Roles & permissions
Two separate role systems apply depending on whether a project belongs to an organization.
Project roles
Set per person on a project's Collaborators page. Ordered highest to lowest access — each role includes everything below it.
OwnerEditorCommenterViewer
| Can do | Owner | Editor | Commenter | Viewer |
|---|---|---|---|---|
| View releases, install builds | ✓ | ✓ | ✓ | ✓ |
| Comment and use the board | ✓ | ✓ | ✓ | — |
| Publish and delete releases | ✓ | ✓ | — | — |
| Manage collaborators, webhooks, API tokens | ✓ | — | — | — |
| Transfer ownership, delete the project | ✓ | — | — | — |
Organization roles
An optional grouping layer above projects. Set per person on an org's page.
AdminMember
| Can do | Admin | Member |
|---|---|---|
| See the org, its members and project list | ✓ | ✓ |
| Full owner-level access to every project in the org | ✓ | — |
| Add/remove members, set org branding and defaults | ✓ | — |
| Request the org's closure | ✓ | — |
An org admin gets full (owner-level) access to every project attached to their org automatically — no separate collaborator entry needed. A plain member does not: they only see a project if someone has also added them to it directly as a collaborator. Projects with no organization work exactly as before — nothing here changes personal, non-organizational use.