Organizations and roles
An organization holds your projects, your members and your billing. Each member has a role, and you can fine-tune what that member can see and change.
Roles
| Role | Starts with |
|---|---|
| Owner | Everything |
| Admin | Everything |
| Member | Edit access to every product, but cannot publish, delete projects, manage members or manage billing |
| Viewer | Read-only access to every product |
A role is a starting point. You can adjust a member's permissions afterwards.
Permissions
Each member has a level of None, View or Edit for each area.
| Area | What it opens |
|---|---|
| API Studio | Specs, endpoints, pages and docs releases |
| SDK Studio | SDK settings, builds and package publishing |
| Docs navigation and components | The docs sidebar and custom components |
| API playground | The try-it console and running MCP tools |
| Monitoring | API traffic, alerts and the status page |
| Project settings | Domain, branding, webhooks and white label |
Five more switches sit beside those levels:
| Permission | Allows |
|---|---|
| Create projects | Starting new projects |
| Delete projects | Removing projects. This is separate from Project settings access |
| Publish | Publishing docs versions and triggering SDK releases |
| Manage members | Inviting and removing members and changing their permissions |
| Manage billing | Changing plans and SDK language subscriptions |
A member who manages others can only give permissions they have themselves.
Project access
A member can reach all projects in the organization, or only specific projects you choose. An agency or a contractor who works on one API usually wants the second.
Inviting people
Invite someone from Settings, under your organization, and pick their role. A pending invite can be revoked until it is accepted, and an unused invite expires. From the CLI, use octri orgs invites.
Switching organizations
You can belong to several organizations. Switch with the project switcher in the dashboard, or with octri orgs switch.