Teams

People → Teams is where you manage native teams. Members inherit the session-visibility grants assigned to their teams.

What native teams are

A native team is a named group of members that you create and manage directly in the console, for the sole purpose of scoping session visibility.

Team names must be unique, case-insensitive: you can’t create “Platform” if “platform” already exists.

Create and manage teams

The New Team card at the top of the page has a Team name field and a Create button.

Each existing team appears as a card showing its name and a member-count chip (X member / X members). Three actions sit on the card, each behind a tooltip:

Manage members — expands the members panel (see below).
Rename — swaps the name for an editable field with Save and Cancel.
Delete team — opens a confirmation dialog:

Delete Team Permanently delete team ‘{name}’? This cannot be undone.

Confirming (Delete) removes the team; Cancel backs out. Deletion is permanent — there’s no undo.

Managing members

Clicking Manage members on a team card opens a Members panel below it.

Current members are listed one per row, each with a remove control. If the team has no members yet, the panel shows No members yet.

To add someone, use the Add member autocomplete — it searches by name or email — then click Add. Only active org members can be added; the search won’t surface someone who’s been removed from the organization or whose invitation is still pending.

A member can belong to multiple teams at once — adding them to a second team doesn’t remove them from the first.

Removing someone from the organization entirely (People → Members) cascades: they’re removed from every native team first, then from the organization. You don’t need to manually clean up team membership before removing a member. See Members & invitations.

How teams control visibility

Native teams exist to scope session sharing. When a member shares a session, the share popover’s Teams & people row lists native teams alongside individuals — picking a team grants every current member of that team access to that session, without changing its default visibility.

Because grants resolve against live team membership, adding or removing someone from a team immediately changes what they can see through that team’s existing grants — there’s nothing to re-share. See Visibility & sharing for the full visibility model, including how team grants combine with the private / org_public / public defaults.

Members & invitations — organization membership, roles, and the cascade removal behavior.
Visibility & sharing — how team grants control session visibility.
Administration — the console overview.