Docs
Open Babbit

Guides

Invite your team and set roles

A project has three roles: owner, builder and viewer. This guide covers invites, roles, the permissions an owner can change, and what happens when someone leaves.

Before you begin

You need to be an owner of the project to invite people and change permissions. Builders can see the Team screen but can't change it.

Roles

RoleCan
OwnerEverything: propose, approve, promote to production, manage secrets, the team and agent settings. Owners hold every permission, always.
BuilderPropose changes and approve them, revert, and connect outside agents. By default, builders can't approve their own drift, promote to production or manage secrets.
ViewerRead everything and comment. A viewer's comment is an input: it counts when a change answers it.

The full list of permissions and their defaults is in Roles and permissions.

Invite someone

  1. Open your profile menu and choose Team.
  2. Click Invite.
  3. Enter the person's email address.
  4. Choose a role.
  5. Choose how long the invite lasts: 1, 7 or 30 days.
  6. Click Create link. Babbit copies the link.
  7. Send the link to the person yourself.

An invite is for one person. The link works only when that person opens it, signed in to GitHub with a verified email address that matches. If anyone else opens the link, or it has expired or been used, nobody joins, and the page says why in one line.

Invites appear under the team grid with their role and days left.

Change someone's role

  1. On Team, click the person's role.
  2. Choose the new role.

The change takes effect at once. The row's audit line records who changed it and when.

Change what a role may do

The lower half of Team lists what each role may do. The first rows, such as propose, approve and manage the team, are fixed for each role. The rest are settings an owner can change:

  1. Find the permission's row, such as Promote to prod.
  2. Click the light under Builder to turn the permission on or off for builders.

Owners keep every row, and viewers change nothing. Every permission is checked where the action happens, not only on the screen. When someone without a permission tries, a message tells them to ask an owner.

Remove someone

Removing someone is a change to the team, not a delete.

  1. On Team, open the person's role menu.
  2. Choose to remove them.
  3. Confirm.

The person stays on the list as left, so their past approvals still name them. They lose every role at once: an approval, a token or a gate answer from them is refused from then on. Babbit lists the secrets they entered so you can rotate them.