Guides
Teams and roles. Invite people to your org and choose what each of them may do.
Everyone in an org has one of four roles. Each role may do what the one above it in this table may, and more.
| Role | May |
|---|---|
viewer | See the dashboard, hub apps, status, logs, releases and members. Open every org app. |
member | Operate apps: deploy, redeploy, stop, start, restart, roll back, set environment variables, run commands and open a shell, create instances, delete apps, connect GitHub, invite people to an app that has no private instance, list and revoke app invitations. |
admin | Change an app's access, invite members and viewers, change people between member and viewer, remove members and viewers. |
owner | Everything, including inviting and removing admins, inviting people into a private app, and handing the org to someone else. An org has exactly one owner. |
A command your role does not allow fails with the role it needs, such as this needs the member role.
Someone invited to one app is not in this table. They are not a member of your org; see Access and invitations.
Invite people
hub invite teammate@company.com # joins as a member, with that address only
hub invite teammate@company.com --role admin # joins as an admin
hub invite --role viewer # a link for whoever you send it toHub sends no email. The command prints a link to send yourself. An invite with an email works only for someone who signs in with that address; without one, the first person to open the link joins. A link works once and expires after 7 days. Hub does not verify email addresses, so whoever holds a link made for an address can create an account with that address and join. If a link went to the wrong place, revoke it.
The person opens the link, signs in or creates an account, and joins your org. Signing up through an invite needs no invite code and creates no org of their own.
Admins may invite members and viewers. The owner may invite admins too. Nobody becomes owner through a link. The members page on the dashboard lists open invites, and Revoke cancels one.
Manage members
hub members # email, name, role and join date
hub members role ana@acme.com viewer # viewer, member or admin
hub members remove ana@acme.com
hub leave # leave the org yourselfremove and leave ask first; --yes skips the question. After hub leave, the CLI switches to your next org, or logs out when there is none.
Removing someone, a role change and leaving take effect in your apps on the next request: someone removed can no longer open them, and an app reads the new role in X-Hub-Role. Everyone else with one of your org's apps open signs in again on that request too, with no form to fill in.
The owner cannot leave. To hand the org over, use Transfer ownership on the members page of the dashboard; the old owner becomes an admin.