Teams
A team is a named group of people inside an organization. Teams are how ownership works in the Catalog: a team owns the projects it's responsible for, so every project has a clear, living owner instead of a name in a spreadsheet.
Team roles
Membership in a team is GitHub-style, with two roles:
- Maintainer: can manage the team, its membership, and its details.
- Member: belongs to the team and is surfaced as an owner of the team's projects.
Only people who are already members of the organization can be added to a team.
Who can manage a team
- Owners and admins of the organization can create teams, delete them, and manage any team's membership.
- A team's own maintainers can manage that team: edit its details and add, remove, or re-role its members.
A team always keeps at least one maintainer: to remove or step down the last one, promote another member first, or delete the team. Deleting a team leaves the projects it owned in place, simply without an owner, so nothing is lost.
Organization member roles
Team roles are separate from a person's role in the organization itself. Across the whole organization, members carry one of:
- Owner: full access. Transferred, not assigned.
- Admin: manage the organization, its members, and every project.
- Member: create and manage flags, projects, and the catalog.
- Viewer: view projects and the catalog. Read-only.
- Billing: manage billing and invoices. Read-only elsewhere.
See Organizations for how membership and invitations work.