Teams, roles & permissions
Every app belongs to an organization. Solo, you're the only member; as a team, you invite people and assign roles that decide who can build versus who can ship and manage. Apps are shared across the org — not owned by one person.
Roles
| Role | Can do |
|---|---|
| Owner | Full control. Everything an admin can do, plus delete or transfer apps and manage the plan, seats, and billing. |
| Admin | Manage apps and the team: create apps, attach/detach resources, manage env & domains, schedule cron, merge pull requests, and invite or remove members. |
| Member | Build: edit files, save versions, create branches, open pull requests, and deploy previews. Can't merge to main or change org-level settings. |
| Guest | Limited collaborator. Sees no apps by default — an admin grants access to specific apps (great for a contractor on a single app). Guests are free and don't use a paid seat. |
main and changing settings require admin (or owner).Inviting teammates
Admins and owners invite people by email from the dashboard. An invite carries a role (member, admin, or guest); the invitee accepts via the link and joins the organization. You can change a pending invite's role before it's accepted, and remove members later.
When someone is removed from the org, their personal preview deployments and playground databases for the org's apps are torn down automatically.
Per-app access (Team plans)
On Team plans you can set access per app, not just per organization:
- App admin — grant a member admin rights on a single app (merge its PRs, manage its settings) without making them an admin of the whole organization.
- Guests — invite someone who sees no apps until you grant them specific ones. Guests are free, but the number you can add is capped at twice your billable seats, and their deploys draw from the team's shared pool.
How this maps to merging
The role split is what makes the branch & pull-request workflow safe: a member's work reaches production only when an admin reviews and merges the PR. main stays protected no matter how many people are building.
Billing & seats
- Solo and Pro plans are single-seat — for one builder.
- The Team plan is billed per seat, with a few seats included in the base (more on Team Premium than Team Basic); beyond that, each extra member is an added seat. Guests don't use a seat. Adjust seats and see pricing on the pricing page.
- Team plans also unlock per-app access — app admins and guests, above.