Skip to main content
Team members share an account without sharing credentials. Each member signs in with their own credentials (Google, Microsoft, or email) and is given one of five roles. The account Owner is implicit — there’s only one Owner per account, and that’s you.

​
Roles

Uploader is the role for teammates who ship builds and nothing else — they can upload and manage builds, but can’t change project settings. Typical fit: a build engineer, an outsourced dev team, or the teammate who runs releases.

​
What each role can do

Only the Owner can invite, remove, or change a member’s role.

​
Per-project access

Each member has a list of projects they can see. Projects outside that list don’t appear in their dashboard. Use this to share specific work with contractors, agencies, or QA teams without exposing your full portfolio. (Finance members aren’t project-scoped — their access is billing-wide.)

​
Invite a team member

1

Open Settings → Team Members

From the account menu.
2

Click Invite member

Enter their email. They’ll sign up or sign in using the exact email you invited.
3

Pick a role

Admin, Editor, Uploader, Finance, or Viewer.
4

Select projects

Tick the projects this member should have access to. Adjust later anytime.
5

Send

The invite status shows Pending until they sign in.
Invitees must sign in with the exact email you invited, using the same method (Google / Microsoft / email password) they originally registered with. Different addresses or different sign-in methods won’t be matched to the invitation.

​
Edit role or project access

Find the member in the Team list, click Edit, change the role or project list, save. Changes take effect on their next dashboard page load.
Downgrading a member’s role doesn’t revoke their existing API keys, but those keys immediately lose the dropped permissions. Removing a project from a member’s list locks their keys out of that project.

​
Remove a member

Click Remove next to the member’s name. They lose dashboard access immediately and all their API keys stop working. Past actions (build uploads, settings changes) stay attributed to them in audit logs.

​
Best practices

  • Default new members to Viewer; elevate only when needed.
  • Give release engineers and outsourced dev teams Uploader, not Editor — they can ship builds without being able to change settings, domains, or webhooks.
  • Reserve Admin for a trusted second-in-command; it’s everything the Owner can do except manage the team.
  • Keep each member’s project list minimal.
  • For CI/automation, generate an API key from a dedicated Uploader account, not a human teammate’s.

​
Troubleshooting

​
Next

API keys

Each member generates their own keys, scoped to their role and project list.

Billing

Admins and Finance members can manage subscription and payment.