Teams
Create teams in your workspace to organize how people deliver work.
Create teams in your workspace to organize how people deliver work.
Workspace plans can cap how many teams you create and how deep they nest.
Overview
A workspace is composed of one or several teams. Teams typically represent groups of people who work together frequently. Issues belong to a team. Projects can span more than one.
By default, when you create a workspace Pulse provisions a team named after the workspace (or General if that name cannot be used). The owner is enrolled as its manager. It's up to you how to split up teams, and people can belong to one or many.
Consider grouping teams by:
- Teammates who work together frequently
- Areas of work such as marketing, mobile app, or platform
- Keeping everyone on one team (the simplest approach for a small workspace)
If you are unsure how to structure your teams, start with one or two. It is easy to add more later.
Your teams
Teams you belong to appear in Your teams. Sub-teams you can reach through a parent nest underneath — you do not have to be a member of every child to see work that parent opens.
Click a team name to expand:
- Home — team landing page, pinned resources, and team documents
- Triage — requests waiting for this team's response (
GthenT) - Issues — issues on this team (
GthenE) - Cycles — current, upcoming, and past cycles (
GthenC), with Current (GthenV) and Upcoming (GthenW) nested underneath - Projects — projects linked to this team (
GthenP) - Views — saved views filtered to the team
- Releases — team ship-batches (
GthenL)
Team Loops is a tab on Home, not a sidebar row.
Triage, Cycles, and Releases only appear when that capability is on for the team.
Team documents
Every team has a home page for team-level resources. Pin documents and links, browse the Documents tab, and jump to common team pages from the Go to rail.
Open Home by clicking the team name in Your teams. From Add resources, create a New document, pin Existing documents, or add a New link….
See Team pages.
Team settings
Configure each team under Settings → Your teams → <team>. From Home, use Go to → Team settings. On Settings → Administration → Teams, open a row's menu and choose Settings.
Team managers and workspace admins can change settings. Available pages:
| Settings page | Configure |
|---|---|
| General | Name, identifier, icon, description, estimates, and Workspace-wide availability |
| Members | Who belongs to the team and their team role |
| Team labels | Team-level labels and groups |
| Templates | Team-level issue, project, and request templates |
| Issue SLAs | Ordered SLA rules for issues on this team |
| Request SLAs | Response and resolution rules for this team's requests |
| Cycles | Enable cycles, duration, timezone, and whether a child follows its parent |
| Issue statuses | The workspace issue workflow |
| Triage Intelligence | AI suggestions for requests routed to this team |
| Source control workflow | Move issues from GitHub and GitLab activity |
| Pulse Agent | Agent provider, guidance, and repository access |
Working with other teams
View other teams
You can open issues, projects, and documents on teams you are allowed to see.
Access control
Workspace members can work across teams they can reach. You do not have to join every team you create issues for.
Turn on Workspace-wide availability (Service provider) to Show this team to all workspace members in team pickers, even people who are not members.
Sub-teams you can reach through a parent stay nested in Your teams.
Create or join teams
Workspace managers and platform admins can create teams.
To create a team:
- Go to
Settings → Administration → Teamsand click Create team - Open the command menu with
Cmd/CtrlKand choose Create a team… - In the settings sidebar, choose Create a team (
/settings/new-team)
Team limits
Your workspace plan can cap how many teams exist and how deep a parent/child tree may go. If create is blocked, ask a workspace admin.
Team creation settings
When you create a team, you can set a parent team and Workspace-wide availability. Identifier, estimates, and members are set after create.
Team creation is limited to workspace managers and platform admins. The person who creates the team is enrolled as its manager.
Tips on structuring teams
Keep these tips in mind when deciding how to structure teams:
- Issues are tied to teams. Think about how you prefer to manage backlog, cycles, and archive-style history.
- Issue statuses are workspace-wide (
Backlog,Todo,In Progress,QA,Release,Done). Every team uses the same workflow. - Cycles are team-specific. A child with no cycle policy of its own follows its parent; use Set own cadence to diverge.
- Projects can belong to one team or several. An issue still belongs to a single team.
- Labels and templates are easy to keep per team. Saved views can include more than one team.
Manage teams
Join / leave / invite teams
Team managers add existing workspace members from Settings → Your teams → <team> → Members (Add members). Change a member's team role from the row menu.
Workspace admins invite people to the workspace from Settings → Administration → Members.
Application identities such as Pulse Agent can hold a team membership for automation.
Sub-teams
See Sub-teams.
Archive a team
Archive sunsets a team without a hard delete. Use it when the team should leave active use and its history should stay.
To archive a team, open Settings → Your teams → <team> and choose Archive… in Danger zone. On Settings → Administration → Teams, the row menu also has Delete…. Both remove the team from active use.
Please note that you cannot undo Archive… from the product.
What happens when a team is archived:
- The team leaves Your teams and team pickers
- Child teams move up to the archived team's parent, or become roots
- Issue identifiers the team used stay reserved so another team cannot take them
FAQ
Last updated on