Access to an application.
Invite developers and colleagues to one application without sharing your password: the Viewer, Developer and Administrator roles, what each can do, and how to change or end access.
Access to applications is given to each application separately. Invite a developer or a colleague to the application they work on — they sign in with their own login and get only that application, with the role you choose. A person can have different roles in different applications.
Access covers the application with everything that belongs to it: its services, databases, replicas, buckets, previews and terminal. Nothing else in your account is opened to them.
Inviting a person
Open the application → the Access permissions tab → Invite a person. Enter their email address, choose a role and click Invite.
The person receives an email link and signs in — or creates an account — with that email address. The link works for 7 days. Until it is accepted, the menu next to the person has Send the invitation again and Cancel invitation.
The Access permissions tab is available to the account owner and the application's Administrators.
Roles
| Role | In short |
|---|---|
| Viewer | sees the status, deploys, logs, monitoring and usage; changes nothing |
| Developer | deploys and rolls back, variables, terminal, data, domains, previews and maintenance; no resources, payments or access |
| Administrator | everything in the application: resources, services and databases, payment, the spending limit, deleting and who has access |
The account owner can always do everything in every application.
What each role can do
| Action | Viewer | Developer | Administrator |
|---|---|---|---|
| See the application, its deploys and their logs, runtime logs, monitoring, usage and spending this month | ✓ | ✓ | ✓ |
| See domains, previews, instances, the list of backups and buckets | ✓ | ✓ | ✓ |
| Deploy, redeploy, roll back, restart; change build settings, services' commands and schedules, processes | — | ✓ | ✓ |
| See and change variables and connection details | — | ✓ | ✓ |
| Use the terminal and the console, Explain this error | — | ✓ | ✓ |
| The Data tab: look at data, change it, import and export | — | ✓ | ✓ |
| Add and remove domains, redirects, maintenance mode, deploy hooks, preview password, notifications | — | ✓ | ✓ |
| Make a backup now | — | ✓ | ✓ |
| Launch the application and pay for it, change its resources, plan and the project it is shown in | — | — | ✓ |
| Switch the branch the application is deployed from | — | — | ✓ |
| Add services, databases, instances, replicas and buckets; make a replica independent | — | — | ✓ |
| Restore a backup, open a database to outside access | — | — | ✓ |
| Set the application's spending limit | — | — | ✓ |
| Delete the application, a service, a database or a bucket | — | — | ✓ |
| Manage who has access to the application | — | — | ✓ |
A terminal in a preview opens for Developers and Administrators, as in the application itself.
The repository an application is deployed from is connected through the account owner's GitHub, so choosing another repository — for the application or for a new service — is done by the account owner.
Working in the owner's account
Once the invitation is accepted, the owner's account appears in your user menu (the avatar at the top right) under Accounts. Choose it to switch. If you have access only to some of its applications, you see only those applications — no payments, other services or team of that account. My account in the same menu takes you back to your own.
The account team
An Administrator of the whole account on the Team page is an Administrator of every application in it — they appear on each application's Access permissions tab as «via account Administrator». Other team roles do not give access to applications by themselves — access to each application is given on its own Access permissions tab.
Members of the team whose role lets them manage services (Administrator, Technical) can create new applications in the account. The person who creates an application gets access to it right away: an account Administrator as its Administrator, a Technical member as its Developer. Launching and paying for it is done by the account owner or an Administrator of the application.
Removing someone from the account team ends their access to the account's applications too.
API tokens and the command line
Personal API tokens belong to the person who creates them, in Account settings → API tokens. In someone else's account a token acts with that person's role in the application, and the token's own scope applies on top: for example, a Viewer's token cannot deploy even with Full access. See Developer tools.
Changing a role or ending access
On the Access permissions tab, choose another role next to the person — it applies at once, and they get an email about it. End access in the menu next to them ends their access to the application at once, including through their API tokens. The application itself is not changed.