Every org member has exactly one role. Roles are checked at every authenticated endpoint that touches org-scoped state.Documentation Index
Fetch the complete documentation index at: https://docs.slipway.sh/llms.txt
Use this file to discover all available pages before exploring further.
Roles
| Role | Read repos, deployments, logs | Read variable values | Trigger deploys | Manage secrets, variables, registries, domains | Manage members, billing |
|---|---|---|---|---|---|
| Viewer | yes | yes | no | no | no |
| Developer | yes | yes | yes | yes | no |
| Admin | yes | yes | yes | yes | yes (except delete org) |
| Owner | yes | yes | yes | yes | yes |
member is a legacy alias for developer and ranks identically.
What each role can do
- Viewer is read-only. They can see repos, browse deployments, watch logs, and read variable values, but can’t trigger a deploy or change configuration. Use this for stakeholders who want visibility without the ability to break things.
- Developer is the typical engineer role. They can deploy, manage secrets and variables, and configure repo-level settings (preview auth, PR comments).
- Admin adds org-wide configuration: members, invites, registries, custom domains, billing.
- Owner adds the ability to delete the org. There can be more than one owner.