Skip to Content
Team & roles

What each platform role can do

Every login on your account has one role: Admin, Developer or User. Here is exactly what each one is allowed to do, so you can pick the right role when you invite someone to your team.

Admin

Full control of the account: plan, team, servers, deployments and staging.

Can

  • Change the plan
  • Invite and remove team members
  • Generate a server's sale order
  • Create staging environments
  • Deploy and redeploy
  • Buy a new server through checkout
  • Change and run servers and deployments
  • See the account's servers and deployments
Developer

Builds and ships: servers, deployments, staging and checkout — no plan or team changes.

Can

  • Generate a server's sale order
  • Create staging environments
  • Deploy and redeploy
  • Buy a new server through checkout
  • Change and run servers and deployments
  • See the account's servers and deployments

Cannot

  • Change the plan
  • Invite and remove team members
User

Sees everything on the account’s servers — changes nothing on them, the plan or the team.

Can

  • See the account's servers and deployments

Cannot

  • Change the plan
  • Invite and remove team members
  • Generate a server's sale order
  • Create staging environments
  • Deploy and redeploy
  • Buy a new server through checkout
  • Change and run servers and deployments

Side by side

The same permissions, compared across all three roles.

Action Admin Developer User
Change the plan Schedule a move to a different pricing tier from the Plan card in Settings.
Invite and remove team members Add platform users by email with a role, change an existing member’s role in place, or remove them from the account.
Generate a server's sale order Create the subscription order for a server with the Generate Sale Order action.
Create staging environments Start a new staging copy of a production server, within your plan’s staging limit.
Deploy and redeploy Deploy a server, rebuild a deployment, or redeploy it at a chosen commit.
Buy a new server through checkout Configure and pay for another server on the website. Whoever signs up for a new account is its Admin, so a first purchase is always allowed.
Change and run servers and deployments Start and stop, change resources, archive, restore or delete, reset or change admin credentials, create and restore backups, edit custom addons, and Connect As a user of the deployment.
See the account's servers and deployments Open every server of the account, whoever created it, with its builds, logs, backups and monitoring.

Good to know

Checked when you act

A button can still be visible to a role that isn’t allowed to use it. The action itself is refused with a “Your role (…) doesn’t have access to this action” message.

Shared across the team

Every login on the account sees all of the account’s servers, whoever created them. The role decides what each person may change; nobody outside the account sees them.

Always one admin

An account must always keep at least one active Admin, and the account owner can’t be removed. Promote someone else to Admin first.

Every login uses a seat

Your plan’s platform-user limit counts every active login on the account — Admins, Developers and Users alike, owner included.