Base tiers
The person who creates a project becomes its Owner. This is unrelated to account registration order; Orbit has no global first-user administrator role.
Owner guarantees
The Owner role always has every permission and cannot be edited. The Owner cannot be removed from the project or changed to another tier. To make someone else the Owner, use Transfer ownership.Editable system roles
Admin, Member, and Viewer are system roles. From Settings → Workspace → Roles & management, you can add permissions to them, but you cannot delete the roles or remove the abilities guaranteed by their base tiers. Clearing a permission in the editor does not override a tier guarantee. Use a lower base tier with custom roles when you need tightly scoped access.Custom roles add access
Create a custom role when the base tiers are too broad. Give it a name and slug, then enable the permissions it should grant. Permissions cover projects, members, roles, settings, integrations, automation, labels, issue types, issues, and comments. Custom roles are additive:- A member keeps every ability from their base tier.
- Permissions from all assigned custom roles are combined.
- A custom role can grant an ability, but it cannot deny one already supplied by the base tier or another role.
- A person can hold several custom roles at once.
Own and any comment permissions
Comment moderation is split into separate abilities:- Create comments controls whether someone can add a comment.
- Edit own comments and Delete own comments apply only to comments the person wrote.
- Edit any comment and Delete any comment allow moderation of other people’s comments.
Manage roles
Open Settings → Workspace → Roles & management, then choose a project. Depending on your permissions, you can:- inspect the project roles and search the permission catalog;
- create and rename custom roles;
- enable one permission or an entire section at once;
- edit the permissions of Admin, Member, Viewer, and custom roles;
- delete custom roles.