Teams

Teams are the primary boundary for day-to-day delivery in Pulse. Issues, cycles, releases, labels, and most templates belong to a team even when initiatives and projects span wider scope.

What a team is for

Use teams to:

• Separate ownership (Engineering, Design, Support, …)
• Give each group its own workflow, estimates, and cycles
• Scope permissions — members see and edit work for teams they can access
• Nest sub-teams under a parent while keeping each sub-team's settings independent

A workspace has many teams; each person may belong to one or several.

Where teams appear

Your teams (sidebar)

Direct memberships appear as roots in Your teams. Sub-teams you can reach through a parent nest underneath — you do not have to be a member of every sub-team to see work your parent team owns.

Click a team name to expand:

• Home — team landing page, pinned links, team documents
• Triage — requests waiting for this team's response
• Issues, Cycles, Projects, Views, Releases — filtered to that team

Workspace administration

Workspace admins manage the team list under Settings → Administration → Teams: create teams, set parent relationships, icons, and identifiers.

Team home

Every team has a Home page (/teams/<team-id>). Use it to:

• Pin documents, views, and links the team opens daily
• Publish team-level resources separate from any one project
• Give new members a curated starting point

Open Home by clicking the team header or choosing Home under the team in the sidebar.

Team settings

Team managers and workspace admins configure delivery under Settings → Your teams → <team>.

Common settings include:

Sub-teams do not inherit estimate scales or cycle settings from a parent — each team configures its own.

Permissions

Pulse checks permissions per resource and team:

• Read access to a team's issues may come from team membership or broader org roles.
• Manage actions (accepting requests, editing team settings) require team manager or workspace admin roles.
• The sidebar only shows teams and links you are allowed to open.

If you expect a team in the sidebar but do not see it, ask a workspace admin to confirm membership and permissions.

Hierarchy

Teams may have a parent team. In the sidebar:

• Teams you belong to always appear at the top level of Your teams
• Sub-teams nest under the nearest ancestor you can see, even if you are not a member of intermediate teams

This mirrors how work is organized without hiding child teams behind collapsed parents you do not belong to.

Related work at workspace scope

Some objects appear in both places:

• Projects — workspace-wide list plus per-team filtered list
• Requests — workspace intake plus team Triage
• Initiatives — usually workspace-scoped, linking to projects on multiple teams

Choose team scope when editing execution details; use workspace lists when coordinating across teams.

Next steps