Roles and permissions
Updated on October 27, 2026
Roles and Permissions
Four graduated roles control what each member can do in a shared project.
The roles
| Role | In one sentence |
|---|---|
| Owner | The project creator: full rights, including deleting it |
| Admin | All rights except deleting the project |
| Developer | Deploys and configures services, without managing the team |
| Viewer | Read-only: canvas, logs, metrics |
Detailed matrix
| Action | Owner | Admin | Developer | Viewer |
|---|---|---|---|---|
| View the project, logs, metrics | ✓ | ✓ | ✓ | ✓ |
| Create services / deploy a template | ✓ | ✓ | ✓ | No |
| Deploy, restart, variables, domains | ✓ | ✓ | ✓ | No |
| Manage redirections | ✓ | ✓ | ✓ | No |
| Organize the canvas (cards, links, folders) | ✓ | ✓ | ✓ | No |
| Delete a service | ✓ | ✓ | No | No |
| Rename / describe the project | ✓ | ✓ | No | No |
| Invite, remove, change roles | ✓ | ✓ | No | No |
| Delete the project | ✓ | No | No | No |
Choosing the right role
- Viewer for a client or manager who tracks progress without touching anything.
- Developer for the team coding day to day: they can deploy anything, but they cannot manage the team or delete a service.
- Admin for your trusted partner: they manage everything except deleting the project.
A role change takes effect immediately, with no need to reconnect.
Permissions also apply to the API and the CLI: an API key acts with its owner's roles, never more.