Skip to content

Teams

A team is a grouping of users within your organization. Teams give you a local authority — the team owner — who can curate the team's PRDs without holding org-wide admin rights, and they back ownership and capacity planning across the product.

What a team is

A team belongs to exactly one organization and has:

  • Members — the users in the team.
  • One or more team owners — a team must always retain at least one owner.

PRDs (and documents) can be associated with a team, which is what lets team owners manage them and what feeds team-level capacity into schedule projection.

Creating and managing teams

Creating, renaming, and deleting teams — and adding or removing members — is an org admin action, done from Admin settings. Team owners curate their team's content and ownership; they do not create or delete teams themselves.

ActionWho can do it
Create / rename / delete a teamOrg admin
Add / remove team membersOrg admin
Grant / revoke team ownershipAn existing team owner of that team, or an org admin
View teams, members, and team documentsAny member of the organization

Team ownership

Team ownership is a distinct, grantable authority — separate from the organization roles (owner/admin/member) and from per-resource permissions. A team owner can:

  • Archive and unarchive any PRD belonging to the team (see data management).
  • Grant or revoke team ownership for other members of the team.

Making or revoking a team owner is allowed for an existing team owner of that team or an org admin.

A team keeps at least one owner

You cannot revoke the last remaining team owner. If you want to hand off ownership, grant it to the new owner first, then revoke the old one.

Why teams matter downstream

Teams are not just an org chart — they are load-bearing for two things:

  • PRD and document ownership. Associating a PRD with a team is what gives the team's owners archive/unarchive authority over it, and what routes it into team-scoped views.
  • Capacity planning. A team's capacity (its available people and calendar) is the input the compression meter and schedule projection use to forecast whether a target date is achievable.

Scopingly.io — the Scoping Document Builder.