Members and Permissions
Who can see and change what, and how roles work.
Roles
Unbind has three roles. Each one includes everything the one before it can do.
| Role | Can do |
|---|---|
| Viewer | Read configuration, logs and metrics. Sees variable names, not their values. |
| Editor | Also deploy, change settings and read variable values. |
| Admin | Also delete things and manage access. |
Editors cannot delete. If a delete is refused, that is why.
Where a role applies
A role is given on something: the whole instance, a team, a project, an environment or a single service. It covers everything underneath. An editor on a project is an editor on all of its environments and services.
People who own the instance have the admin role on every team. See Managing Teams.
Members
Team > Settings > Members lists everyone who can reach the team and the role they have. Team admins manage it: add people, change their role and remove them. Anyone can leave a team they are on.
Some rows cannot be changed here. They are marked with the name of a group, such as superuser, and belong to people who reach the team through that group rather than through a role on the team itself. Instance owners show up this way on every team.
Add someone
Press Add Member, enter an email address and pick a role.
- The address has an account: they are on the team right away. If email is set up, they get a message about it.
- The address has no account yet: Unbind creates an invitation and shows you a link. Share it with them, or let Unbind email it when email is set up. The link works once and expires after 7 days. Opening it asks for a password, creates the account and puts it on the team with the role you picked.
Pending invitations are listed under the members. Revoke one and its link stops working. Inviting the same address again replaces the earlier invitation.
Instance owners can also create accounts without an invitation, from the server with user:create. See Reset Password for how to run the CLI.
Change a role or remove someone
Use the menu on a member's row. Removing someone takes away the role they had on this team and nothing else. Their account, their other teams and their API keys stay as they are.
Groups
Under the hood a role on a team is a group with that one permission, and every team has an admin, editor and viewer group. These groups are managed from the members page and cannot be renamed, deleted or changed through the group endpoints. Instance owners can still make groups of their own for finer grants, such as an editor on one service.
Roles for API keys and apps
You already use this model when you create an API key or approve a connected app. You pick a role and, if you want, the specific teams, projects, environments or services it can reach. A key can never do more than you can.
This is the right way to give a CI pipeline or an AI agent access: an editor key limited to one project, not a key that can reach everything.
GitHub connections
A GitHub connection belongs to the person who made it. Only they see its repositories unless they share it with teams, in which case every member of those teams can pick from it when building in those teams. Team editors can remove a shared connection from their team, and system admins can share it with any team or with all teams, including future ones. See Deploy from GitHub.
Your account
Your account settings, under your avatar, have your email, your password, your API keys, your connected apps and your GitHub Apps. Changing your password does not sign out other sessions and does not revoke API keys.