Roles and permissions
Every project member has exactly one role. Roles are project-scoped — being an admin on the team doesn't automatically make you an admin on every project the team owns.
The four roles
| Role | What they can do |
|---|---|
| Owner | Everything. Only one per project. Can transfer ownership or delete the project. |
| Admin | Everything except transfer ownership. Can invite, change roles, delete the project, manage integrations. |
| Developer | Edit flows, comment, see all members. Cannot invite or change settings. |
| Viewer | Read-only. Can open flows, read comments, see members. Cannot edit anything. |
Who can assign which role
- The owner is fixed at creation. To change it, use Transfer ownership (see Delete or transfer).
- Admins can grant any role except owner.
- Developers and viewers can't change anyone's role.
Common patterns
- Solo project — you're the owner, nobody else. Keep it that way until someone else needs in.
- Pair / small team — owner + a couple of developers. Promote one to admin only when invitations become a chore.
- Cross-team review — invite reviewers as viewers so they can read the flow and leave comments without risking accidental edits.
What happens when someone leaves
A user who leaves the project (or is removed by an admin) loses access immediately — including any flows, comments, and integration data scoped to this project. They can be re-invited later.