Manage Teams
Create, configure, archive, restore, nest, and manage workspace Teams
Workspace owners, admins, and authorized Team owners manage Teams from Workspace Settings -> Teams. Workspace members can view active Teams they can access and open Team pages from the sidebar.
Create a Team Owner Admin
Open Teams settings
Open Workspace Settings -> Teams.
Enter the Team identity
Type a Team name between 2 and 120 characters. Integrity suggests a short uppercase Identifier for future Team Issue keys until you edit the Identifier directly.
Choose Team access
Choose Public or Private when the workspace capability allows it, then optionally choose a parent Team. The default Team always remains public.
Create the Team
Select New Team. Integrity creates a stable Team slug from the initial name.
Team slugs are immutable. If you rename or move a Team later, the visible name or parent changes but the route stays stable.
Team Identifiers are separate from slugs. Renaming a Team does not regenerate its Identifier, changing an Identifier does not renumber Issues, and duplicate or over-limit values are rejected with field-level feedback.
Manage a Team with a coding agent
After you connect a coding agent, explicitly ask
it to inspect or change a Team using the immutable team:<slug> reference.
The agent reads the current Team configuration, inherited/custom setting
state, exact bounded counts, available actions, and the canonical Team route
through your current workspace access.
Supported administration includes:
- Team creation and routine name, Identifier, description, and icon changes;
- privacy, hierarchy, archive, and restore workflows;
- members, owners, invitations, access requests, and the three supported permission policies;
- Issue statuses, workflow automation, labels and label groups, and estimates;
- Cycles and resources, calendar-feed controls, Triage configuration and rules, and recurring-Issue schedules.
Routine reversible changes apply only after an explicit request. Privacy, hierarchy, access-reducing, destructive, inheritance-resetting, bulk, and calendar-secret actions return a short-lived preview first. Review the exact effects and confirm that prepared action separately; editing the proposed payload creates a different request.
Coding agents cannot permanently delete Teams, select a different structural workspace default Team, change your personal preferred Team, run arbitrary SQL/RPCs, or use Team administration to process individual Triage entries or rewrite generated Issues.
Move a Team under a parent Owner Admin
- Open Workspace Settings -> Teams.
- Select the active Team.
- Open General.
- Choose a parent Team, or choose No parent team to un-nest it.
- Confirm any membership, visibility, or inherited-setting review prompt.
Moving a Team does not change its slug or URL. If the move would violate parent membership or private-Team rules, Integrity blocks the strict move or offers an explicit confirmation path when it can safely add required parent memberships or make public descendants private.
Rename a Team Owner Admin
- Open Workspace Settings -> Teams.
- Select the active Team.
- Edit the Team name.
- Save the change.
Renaming does not change the Team slug or route. A Team's Settings management policy can delegate eligible Team settings to all Team members, but critical governance controls remain protected.
Archive a Team Owner Admin
- Open Workspace Settings -> Teams.
- Select the Team.
- Use the archive action.
- Confirm the archive.
Archived Teams are hidden from the active sidebar list and cannot have members added or removed.
The default Team cannot be archived. It remains the workspace-level landing Team and mirrors workspace membership.
Restore a Team Owner Admin
- Open Workspace Settings -> Teams.
- Switch the Team filter to Archived.
- Select the Team.
- Use the restore action.
The restored Team returns to the active Team list and keeps its original slug.
Access and permissions
Each active Team has an Access and permissions settings page. The page controls three policy categories:
| Policy | Values | Effect |
|---|---|---|
| Settings management | Owners only / All Team members | Who can manage policy-enabled Team settings. |
| Label management | Owners only / All Team members | Who can create, edit, reorder, archive, restore, delete, group, and move Team Issue labels. |
| Member management | Owners only / All Team members | Who can add or remove Team members where owner safeguards allow it. |
Disabled future rows may appear for Team access, membership restriction, Template management, or agent skills. Disabled rows are inventory only until those capabilities ship.
Navigate Team pages
Active Teams you can access appear in the workspace sidebar under Your teams. Select a Team row to open its Team page. Expand a Team to see its fixed Team pages and visible sub-Teams.
Manage Team Issue labels
Team Issue labels live under Team settings -> Issue labels.
Use History from that page to open the Team Audit log filtered to label configuration. The audit contains label/group configuration changes; label assignments on individual Issues remain in Issue Activity.
Use Team labels for vocabulary that should only apply to Issues owned by that Team. The table supports label groups, label colors, descriptions, active/archive filtering, restore, permanent delete for custom labels, and moving custom Team labels to the workspace label scope.
Workspace-wide labels are managed from Workspace Settings -> Issues -> Labels and can be applied to Issues across the workspace.
Team members can apply existing labels to Issues they can edit. Managing the Team label definitions themselves follows the Team's Label management policy.
Manage Team Issue estimates
Team Issue estimate settings live under Team settings -> General -> Estimates.
Team managers can enable or disable estimates, choose Exponential, Fibonacci, Linear, or T-Shirt scales, allow zero estimates, enable extended values, and choose whether unestimated Issues count as one point in grouped effort details. Sub-Teams can inherit estimate settings from parent Teams.
Estimate setting changes write Team Audit. Issue estimate set/change/clear activity remains on the Issue Activity timeline.
Manage Team Issue Cycles
Team Issue Cycle settings live under Team settings -> Cycles.
Team managers can enable Cycles, choose duration, start weekday, cooldown, future Cycle count, automation rules, timezone behavior, and calendar feed availability. Each Team owns an independent schedule; sub-Teams do not inherit parent Cycle settings.
Cycle setting, date, lifecycle, and resource changes write Team Audit. Issue assignment, movement, automation, and rollover remain on the Issue Activity timeline.
Audit and freshness
Team create, rename, archive, restore, parent change, member add, member remove, privacy-cascade, permission-policy, and estimate-setting events write audit evidence. Team-specific events appear in the Team Audit log; Workspace Audit stays focused on workspace-level activity. Team list, Team detail, sidebar, settings, and member surfaces refresh through realtime/cache invalidation.
The Integrity interface and coding agents produce the same receipts, typed Team Audit events, notifications, and private realtime invalidations. Retrying the same successful request key returns the original result without duplicating the product effect.