Cloud/Settings/Teams
Teams
Members grouped so access can be granted in bulk: create a team once, add people to it, and every project it touches follows.
Teams is where membership becomes structure. The description: "Group members to manage access at scale." The page's own hint sharpens it: "Group members to grant access to projects in bulk."
Teams
Group members to manage access at scale.
Group members to grant access to projects in bulk.
Platform Engineering
Owns the connector runtime and edge infrastructure.
Billing Ops
Finance integrations and metering.
The mockup is the real surface. Create a team, add members to it, and delete one you do not need.
One card per team
Each team shows its name, an optional description and the people in it as chips. Add member pulls from the organization's members on Members; the same person can sit in several teams. Creating is org:teams:manage: one dialog, a name, an optional "Brief description", and the team exists. Delete team removes the grouping; the people stay members of the organization, only the bundling goes away.
Why grouping matters
Without teams, access is granted person by person, and every project change means touching every person. With teams, the unit of assignment becomes the group: grant the project to Platform Engineering once, and adding someone to the team is the whole onboarding. When someone leaves, removing them from one team revokes everything that came through it.
Why this page exists
Teams are the difference between administering access and babysitting it. They keep the organization's permission model readable: instead of a matrix of who can touch what, you read the teams, and the teams read like the org chart.
What comes next
Roles defines what a role can do; teams define who travels together.