Teams and users

Membership lives in one place: the Users & Teams section of Settings. It is where you set somebody’s role, group people into teams, and remove them when they leave. Inviting them is the one part that happens elsewhere.

Open Settings, then Users & Teams in the section list. The older /settings/users and /settings/teams addresses still work, but they drop you at the top of Settings rather than on this section, so use the section list.

Invite a teammate

DeltaVault does not send invitations. The Invite via Clerk button above the user list opens Clerk, the identity service that holds your organization’s accounts, in a new tab, and you invite people there.

Once somebody accepts and signs in, they appear in the user list here, and this is where you give them the role you want them to have. A new member arrives as an editor unless their Clerk role says otherwise, so check the role of anyone whose access should be narrower.

The three roles

Every member holds exactly one role, shown in the Role column and spelled in lowercase:

viewer reads. They cannot change metadata.
editor reads and changes metadata. This is the working role for a data engineer.
admin does everything an editor does, and additionally manages settings, membership, roles, and teams.

Change a role by picking a new one from the Role column. Only an administrator can: for anyone else the control is disabled and reads Only administrators can change roles.

A role you set here governs DeltaVault and nothing else. It does not travel back to Clerk, so the role in Clerk’s own organization screen can differ from the one shown here. The role in this list is the one DeltaVault enforces.

What else the user list shows

Name, Email, Role, and Joined are visible to everyone who can open the section. Administrators also see Home persona and Allowed personas, which set which persona a member starts in and which ones they may switch to.

Remove takes somebody out of the organization. It asks you to confirm first and names the person. Removing is not permanent in the sense that matters: you can invite them again through Clerk.

Teams

A team is a name and a list of members, and you use it to group people for team scoped permissions. The Teams list shows each team’s Name and its Members count, and starts at No teams yet.

Select New team, give it a Team name, and select Create. It is created empty, with no members.
Select the team’s name to open it.
On the team page, pick somebody under Add member and select Add. The picker offers only people who are not already on the team, and says All users are already members of this team. when everyone is.
Remove on a member’s row takes them off the team. They keep their organization membership and every other team.

Each team’s row menu offers Rename and Delete. Deleting a team removes its team scoped memberships and permissions; its members keep their organization access.

What a member sees that an administrator does not

The difference is larger than a few disabled buttons, and it is worth knowing before somebody reports that a page is missing.

A member who is not an administrator sees only the Conventions section in Settings. Every other section, Users & Teams included, is absent from the section list. Opening a link straight to a section they cannot see does not produce an error: Settings simply shows them Conventions.

Administrators who lose the role mid session hit the second layer: the role control, Remove, New team, Rename, and Delete all disable themselves and read Requires admin role. Behind both layers the server refuses the change outright, so a member cannot reach these actions by any route.

One asymmetry to know: a member who follows a direct link to a team page can read that team and its members. Every action on the page is refused.

Nothing in this section is affected by which branch you are on. Roles, membership, and teams are organization wide, and they are editable on main.

Troubleshooting

Somebody accepted an invitation and is not in the list. They appear once they have signed in to DeltaVault at least once, not when they accept in Clerk.
The Role control is disabled. You are not an administrator in this organization. The tooltip names the reason.
Users & Teams is not in my Settings list. You are not an administrator. Ask one to make the change, or to give you the role.