Teams

Use Teams to group members for planning, standups, boards, recaps, and shared visibility.

Team model

Within a workspace, teams are the main unit of organization. Teams can have their own standups, planning boards, integrations, and analytics. Even a one-person team can use team-scoped insights, release notes, and standups. A person can belong to multiple teams, and teams can be nested under parent teams for larger organizations.

Creating and joining teams

Any user can create a team. The creator becomes a team admin and can set the team name, icon, linked Slack channel, and initial invites. Invitations can be sent while creating the team or later from team settings.

Each member added to a team must accept the invite before gaining access. If Slack is connected, invitations can arrive through Slack; otherwise email invitations are used. Team members are still workspace members, but workspace membership does not automatically grant team access.

Team roles

Team roles are separate from workspace roles.

Role	Scope
Admin	Configures standups, integrations, team channels, and membership while also participating in team work.
Member	Participates in team work, standups, boards, recaps, release notes, and insights.
Observer	Views team context without contributing standup updates or team work.
Coordinator	Manages team setup without participating in team work.

Team admins and coordinators can invite or remove members, revoke pending invitations, and promote other members to admin.

Create teams around collaboration and visibility, not only the org chart. A team is the group that shares planning, standups, recaps, and progress context.

Membership and access

Team members can see team activity and fellow team members' work subject to privacy settings. Workspace members outside the team do not get team-specific views by default.

Removing a member immediately revokes their access to team features. Their historical work remains attached to the person who did it so summaries, release notes, and analytics keep their context.

Team pages

A team page shows members, pending invites, linked communication channel, configured AI abilities, team-level insights, and recent team work. Use it when you need the operational view for one team instead of the whole workspace.

Team pages connect to planning boards, standups, team insights, and release notes. Historical member work and generated summaries help people catch up, but decisions should stay attached to the underlying initiatives, bugs, todos, comments, and connected app activity.

Use Team Board under the team in the sidebar to see member work across statuses in one grid. Team summaries appear in the team journal, and the Slack bot can answer questions about team work when Slack is connected.

Team settings

Team admins and coordinators can edit the team name, icon, Slack channel, membership, pending invites, and admin roles from team settings. Multiple admins are supported.

Deleting a team is permanent for team-specific setup and history. Individual member work remains attached to the people who did it.