Feature · Crew
Teams
Group employees and people who share memory and pipeline settings.
How it works
Make a team
Open Teams. Select New team and enter a name and a short description. Owners and admins can make and change teams. Other members can read them.
Add members
Open a team and select its members. A team can hold workers and people. A worker belongs to one team at a time; moving it records the change on the worker. A person can be in several teams.
What a team shares
Team memory is visible to the team's workers. A team can have its own pipeline profile, for example its own stage owners and review rules.
Archive a team
Archive a team that you no longer use. Archiving removes its members. You can restore it later; it comes back with no members.
From the help article Teams, checked against the product on .
What you can do
The operations this feature's screens call. Each one is POST /api/<name>, and the badge says who may call it.
MemberlistOrgTeamsThe teams with their workers and people. Archived teams only when includeArchived is true.
Types:
ListOrgTeamsRequestreturns{ teams: TeamDto[] }
AdminarchiveTeamArchives a team and removes every member, or restores it without members.
Types:
ArchiveTeamRequestreturnsTeamDto
AdminupdateTeamUpdates the team.
Types:
UpdateTeamRequestreturnsTeamDto
AdmincreateTeamCreates a team.
Types:
CreateTeamRequestreturnsTeamDto
ViewerlistMembersLists members.
Types:
EmptyRequestreturnsListMembersResponse
ViewerlistWorkersLists workers.
Types:
ListWorkersRequestreturnsListResponse<WorkerSummary>
AdminNo API tokenssetTeamMembersSets the full lists of workers and people in a team. A worker that joins leaves its old team.
Types:
SetTeamMembersRequestreturnsTeamDto
Screens
What it records
The feature writes these events to the audit log, the permanent record of what happened.
- Account security changed
- API token created
- API token revoked
- Member added
- Member role changed
- Org created
- Team changed
- User signed in