Workspace Roles and Permissions: A Practical Guide
Once more than one person touches the same API collection, “who can do what” stops being optional. Someone needs to edit requests and shared environments; someone else just needs to read them without accidentally breaking a teammate’s work. Role-based access control (RBAC) solves this by attaching a fixed set of permissions — individually named capabilities like “create a request” or “read a shared environment’s secrets” — to a role, then assigning that role to each person instead of managing their access one permission at a time.
The Permission Catalog
Every action a workspace member can take maps to one named permission. Roles are just bundles of these:
| Group | Permission | What it allows |
|---|---|---|
| Workspace | workspace.read | View the workspace and everything inside it |
| Workspace | workspace.settings.manage | Rename the workspace, change its settings |
| Workspace | members.manage | Change a member’s role, or remove them |
| Workspace | roles.manage | Create, edit, or delete custom roles |
| Collections | collections.read | View collections |
| Collections | collections.create | Create new collections |
| Collections | collections.update | Rename or reorganize a collection |
| Collections | collections.delete | Delete a collection |
| Folders | folders.read | View folders |
| Folders | folders.create | Create new folders |
| Folders | folders.update | Rename, move, or reorganize a folder |
| Requests | requests.read | View requests |
| Requests | requests.create | Create new requests |
| Requests | requests.update | Edit or move a request |
| Environments | environment.workspace.read | View shared (workspace) environments |
| Environments | environment.workspace.create | Create a shared environment |
| Environments | environment.workspace.update | Edit a shared environment |
| Environments | environment.workspace.delete | Delete a shared environment |
| Environments | environment.workspace.readSecrets | See the decrypted value of secret variables in shared environments |
| Environments | environment.personal.manageOwn | Create and manage your own personal (non-shared) environments |
Two permissions are deliberately scarce: roles.manage is the one thing
every default role except Owner lacks — it’s what actually customizes who
can touch role definitions themselves. And environment.workspace.readSecrets
is the one that decides whether a member sees real credential values or
just that a secret variable exists.
The Default Roles
HTTP Titan ships seven product-defined roles. Which ones you can assign depends on your workspace’s plan — see the next section — but the roles themselves are fixed: nobody can edit what a default role grants, which is what keeps “Owner” meaning the same thing in every workspace.
| Role | Summary |
|---|---|
| Owner | Full access: workspace settings, members, custom roles, and every content/environment permission, including secrets. |
| Editor | Everything Owner has except workspace settings, member management, and role management. Can fully create, edit, and organize collections, folders, requests, and shared environments. |
| Viewer | Read-only on collections, folders, and requests — but can still see decrypted secrets in shared environments and manage their own personal environment. |
| Maintainer | Editor’s full content/environment access, plus workspace settings and member management — everything Owner has except creating or editing custom roles. |
| Developer | Full create/edit on collections, folders, and requests, but shared environments are read-only (no create/update/delete) — still sees secrets and manages a personal environment. |
| QA | Read-only on collections, but can create and edit folders and requests to build test cases. Shared environments are read-only; secrets and a personal environment are still available. |
| Guest | Read-only everywhere — collections, folders, requests, and shared environments — with no access to secret values and no personal environment. The most restrictive role in the catalog. |
A subtlety worth calling out: Guest is more restrictive than Viewer, even
though Viewer is one of the three “base” roles and Guest is one of the
four “extended” ones. Viewer still gets environment.workspace.readSecrets
and environment.personal.manageOwn; Guest gets neither. Match the role
to what the person actually needs, not just to how senior they are.
How Roles Map to a Plan
Not every plan gets every role, and only the highest tier can define new ones:
- Free — Owner, Editor, and Viewer only. These three are available on every plan precisely because they’re the roles existing teams are already used to.
- Team — all seven default roles, including Maintainer, Developer, QA, and Guest. No custom roles yet — the permission sets above are fixed.
- Enterprise — everything in Team, plus the ability to create, rename, and edit fully custom roles with their own permission sets, including duplicating a default role as a starting point.
If a workspace is downgraded after custom roles were already assigned, those assignments are preserved — existing members keep working — but the role’s permission set is frozen until the workspace is back on a plan that supports editing it.
Managing Roles in HTTP Titan
Workspace Settings → Members & access has a dedicated Roles section: default roles are listed read-only (with a plan-tier lock shown on the ones your current plan doesn’t unlock yet), and — on Enterprise — a “New role” button opens a permission checklist grouped the same way as the table above. Assigning a role to a member or a pending invitation uses the same list, so the gating is consistent everywhere a role gets picked.