ShrubberyDocs
API ReferenceSign in
Concept

Team

A named group inside an organisation that scopes membership and Shrubbery visibility.

01 · Definition

Definition

A Team is a group under one organisation. Every Shrubbery belongs to exactly one team (team_id). People hold team_lead or team_member roles on a team; Org Owner is org-wide and is not tied to a single team row.

Avoid: squad, project, workspace (use Team for the product entity).

02 · Role

Role

Teams are the unit of roster and RLS scoping: members see team Shrubberies; the Org Owner sees every team in the org. Capture and send paths that omit team_id fall through to the assigner's default team (typically the org's oldest team) via a database trigger — multi-team pickers on create are not the primary path yet.

Leads and Knights still describe commitment roles on a row; Team membership answers "which group does this commitment and this person belong to?"

03 · Lifecycle

Lifecycle

  • Created — Org Owner creates a team in Organisation Settings; name is unique enough for humans, not a public slug.
  • Populated — members receive team_lead or team_member on that team (invite or role change).
  • Default team — every org gets a default team at signup; new users who create an org become owner + lead there.
  • Deleted — only when empty (no remaining role rows); owner-gated.
04 · Related

Last updated: 24 July 2026