Teams

Teams are workspace groups for organizing work, navigation, and future Issue ownership. Every workspace has one default Team named from the workspace at creation, and admins can create additional Teams.

What Teams are for

Use Teams when you need a stable workspace grouping for ownership and routing:

• Navigate to Team pages from the workspace sidebar.
• Group people into public or private organizational Teams.
• Nest Teams under parent Teams to mirror the way work is organized.
• Assign visible Teams as owning context for Projects and Initiatives in Spec-Driven Development.
• Save Team-scoped Issue, Project, and Initiative views with a consistent table and detail experience.
• Keep a durable Team slug for URLs and future Team-scoped records.
• Review Team lifecycle and membership changes in the right Logs surface.

Teams can be arranged as parent Teams and sub-Teams. Sub-Team members must also belong to active parent Teams, but parent Team membership does not automatically add someone to child Teams.

Authorized users can administer the same Team settings from Codex or another compatible coding agent. Agent actions use the Team's immutable team:<slug> reference, current server-projected permissions, and the same product services as the Integrity interface. High-impact changes are previewed and require a separate exact confirmation before they apply.

Default Team

Each workspace gets exactly one default Team.

The default Team slug is stable. Renaming the workspace or the Team does not change the Team route.

Team pages

Team pages live at:

/workspace/{workspaceId}/teams/{teamSlug}

Opening the workspace root sends you into a Team-owned work surface. Integrity uses your last explicitly opened Team when it is still available, otherwise the first joined non-default Team, then the default Team.

The Team page includes:

• Overview with the Team icon, name, and description, and a side column with the Team's members, its parent Team, and the sub-Teams you can see. A block with nothing to show says so, for example No parent Team or No sub-teams. Select View all beside the members to open the Members tab.
• Members with the current Team roster.
• Projects for the Projects the Team owns, in the shared Project table.
• Views for Team-scoped Issue, Project, and Initiative saved views.

Only workspace admins see Team member-management actions, and only on active Teams.

Private Teams stay hidden unless you can access them. Sidebars, hierarchy labels, and logs use redacted or omitted references instead of exposing private Team names to unauthorized viewers.

Team Views

Every accessible Team has a Views directory at:

/workspace/{workspaceId}/teams/{teamSlug}/views

Use the Issues, Projects, and Initiatives tabs to create or open views for the current Team. The create form always shows Save to the current Team. Team Views cannot be saved as Personal or Workspace views, and Team scope cannot be removed from the saved lens.

Browsing a public Team does not grant view creation or management. Without Team view authority, the directory remains readable but create actions are absent; opening a copied create URL returns to the directory without mounting an editor.

Selected views use the same table controls and three-card detail drawer as workspace Views. The summary is calculated from visible filtered rows. Only Team Issue views support saved-view subscriptions.

Team Projects

Every accessible Team has a Projects page at:

/workspace/{workspaceId}/teams/{teamSlug}/projects

Open it from Projects under the Team in the sidebar. The page lists every Project you can open that has the Team among its owning Teams, whether as its first Team or as an additional one. A Project owned by two Teams appears on both Teams' pages. Sub-Teams keep their own pages: a Project appears on a parent Team's page only when the parent Team is one of its owning Teams.

The page uses the same table as the workspace Projects page, with its List, Board, and Timeline layouts, filters, and display options. Changing the Team of a Project moves it on or off the page as soon as the change is saved, including for other people who have the page open.

The All Projects tab shows every listed Project. The tabs after it are the Team's Project views, the same views that the Projects tab of Team Views lists. When you can create Team views, Add view and Save as new save the view to the current Team. Your unsaved filter and display changes stay on your device, and personal Project views stay on the workspace Projects page.

New project starts a Project with the current Team already selected. You can still change its Teams before you create it. The More Project actions menu opens the Team's archived and recently deleted Projects when you can view them.

Planning ownership

Projects and Initiatives can carry one or more owning Teams. Team ownership helps people scan who owns planning work, filter/group planning tables, and navigate to visible Team pages.

Team ownership is not permission-bearing. Adding a Team to a Project or Initiative does not give Team members access to that planning object or its evidence. Private Team associations stay display-safe: unauthorized viewers see a generic private Team value instead of names, slugs, colors, hierarchy, members, route links, filter labels, exports, or agent-ready detail.

Related