Roles and Permissions
SelfDocHub has three user roles and a separate token mechanism for publishing. This page lists who can do what.
Roles#
| Role | Purpose |
|---|---|
reader |
Reads documentation, uses Try-It, saves requests, exports documents. |
editor |
Everything a reader does, plus edits documentation content of the services the editor can access. |
admin |
Manages the installation: users, services, teams, integrations and license. Sees every service. |
All access requires a signed-in user. There is no anonymous read path. Publishing specifications uses a per-service upload token instead of a user session. See Publishing a Specification.
Team scoping#
reader and editor users only see and reach the services covered by the teams they belong to. A user who is in no team sees no services. This applies to the left menu and to the service's API routes, not only to what is listed. admin users are exempt: they always see and manage every service. See Teams.
Permission matrix#
| Action | reader | editor | admin |
|---|---|---|---|
| Browse services, endpoints, versions and Change Log | yes | yes | yes |
| Search | yes | yes | yes |
| Use Try-It, save requests, share links, save interactions | yes | yes | yes |
| Favorites, personal working version (pin) | yes | yes | yes |
| Create environments; edit or delete one's own | yes | yes | yes |
| Edit or delete any environment | – | – | yes |
| Use the Export Wizard and export cover pages | yes | yes | yes |
| Read text pages and their history | yes | yes | yes |
| Edit overlays (service, tag, endpoint, parameter) | – | yes | yes |
| Create and edit text pages, labels and the service structure | – | yes | yes |
| Import a version, delete a version | – | yes | yes |
| Review and delete orphaned overlays | – | yes | yes |
| Promote a merged snapshot | – | yes | yes |
| Make another version current for everyone (switch) | – | – | yes |
| Edit a version's display number, reparse a version | – | – | yes |
| Create, edit and delete services; rotate a service token | – | – | yes |
| Manage service groups | – | – | yes |
| Manage users and teams | – | – | yes |
| Manage SSO providers | – | – | yes |
| Manage notifications | – | – | yes |
| Manage MCP tokens, mark environments and endpoints for MCP | – | – | yes |
| Upload a license | – | – | yes |
| Force a rebuild of merged documents | – | – | yes |
Note: Features that depend on the license (SSO, notifications, MCP, export, Try-It through MCP) additionally need the matching feature in your license. See License and Tiers.
Environments and ownership#
Anyone who can read a service can create an environment for it. Editing or deleting needs the creator or an administrator. A person who cannot manage a row sees a read-only View action instead. Only an administrator can open an environment to the MCP server, and only a public one. See Environments.
Per-user data#
Saved requests, saved interactions, favorites, pins and exports belong to the user who created them. Another user's export answers 404.