Roles
Understand workspace roles, Team roles, direct Issue shares, and policy-controlled Team permissions.
Integrity uses layered permissions. Workspace roles decide who can administer the workspace, Team roles decide who can work inside a Team, and scoped grants such as direct Issue shares or restricted source access stay limited to the object they were granted for.
Workspace roles
| Role | What it means |
|---|---|
| Owner | Highest workspace control. Owners can manage members and sensitive workspace controls, and at least one owner must remain in every workspace. |
| Admin | Routine workspace administration. Admins can manage workspace settings and members, but owner-only safeguards still apply to owner assignment and final-owner protection. |
| Member | Standard collaborator. Members can use normal workspace collaboration surfaces, subject to Team, Module, source, and object-level access rules. |
Owners and admins can invite workspace members. Only owners can invite or promote other owners.
Workspace role names are separate from source/folder Manager, Editor, and Viewer roles. External guest sharing is Viewer-only; people who need to edit should be workspace members with the appropriate source or folder access.
Team roles
| Role | What it means |
|---|---|
| Team owner | Manages the Team by default and can use owner-only Team controls. |
| Team member | Can do normal work for Issues owned by Teams they can access. |
Team membership does not grant access to Modules, artefacts, baselines, reviews, Spec-Driven Development, or restricted source content by itself.
Team permission policies
Each Team has an Access and permissions settings page. Three policy categories can be set to Owners only or All Team members:
| Policy | Controls |
|---|---|
| Settings management | Team settings that opt into the Team settings policy. |
| Label management | Team Issue labels and label groups. |
| Member management | Adding or removing Team members where owner safeguards allow it. |
Future rows such as Team access, membership restriction, Template management, and agent skills may appear disabled when they are not part of the current plan.
Issue access
Team members can create Issues and edit normal Issue work fields in Teams they can access: title, description, status, priority, assignee, labels, primary Feature, and icon color.
Issue editors can assign an Issue only to a Phase from its current Feature. Feature Phase creation, rename, date, reorder, description, and deletion require the named Feature Phase capability; Feature visibility or an Issue link does not grant that authority.
Direct Issue shares grant access only to the shared Issue. In this release, direct-share recipients can read the shared Issue but do not gain Team context or Team Issue mutation rights.