Skip to content

Manage team and access

Settings → Team & Access is project-scoped. It combines the user directory, reviewer groups, review teams, approval roles, and Terraform approval mapping. Only a project administrator can change users or reviewer groups.

Typical time
10–20 minutes
You need
Project administrator access
Outcome
Reviewed membership and reusable approval routing

Open Settings → Team & Access, select the project, and use the tabs:

  • Users
  • Reviewer Groups
  • Review Teams
  • Approval Roles

Review Total Users, Active Members, Reviewer Groups, and Open Invites. Use the refresh action after another administrator makes a change. Lists use backend pages; use page size, Previous, and Next instead of assuming the first page contains every record.

Team and Access Settings showing the Documentation project selector, access tabs, summary cards, reviewer group, Terraform approval mapping, and pagination controls
Team 1 of 5 · Select a project and access viewShow the project selector, four tabs, summary cards, and backend pagination.

Choose Invite User. ScrinCloud opens the selected project’s setup flow for members.

  1. enter the invited person’s email address;
  2. select the lowest useful project role;
  3. review the selected project;
  4. send the invitation; and
  5. return to Team & Access to confirm the pending row.

Roles are Admin, Editor, Reviewer, and Viewer. Provider access, billing authority, and approval-group membership remain separate permissions.

Team and Access Settings with the Documentation project selected and the Invite User action visible before opening project member setup
Team 2 of 5 · Invite a user to the selected projectShow the project-scoped Invite User action that opens the selected project's setup flow.

Open the row actions for the intended directory entry:

  • Copy email copies the visible address locally.
  • Resend invitation sends a new message for an eligible pending or expired invitation.
  • Revoke access blocks an active non-owner member after confirmation.
  • Delete member removes an active member’s project access record.
  • Delete invitation invalidates an invitation record.

The project owner cannot be revoked through this row action. Review the name, email, role, status, and project before confirming a destructive action.

Team and Access user directory with synthetic example-domain users and the non-owner member actions menu showing Copy email, Revoke access, and Delete member
Team 3 of 5 · Use the correct member lifecycle actionShow a synthetic row menu for a non-owner directory entry before any destructive confirmation.

Choose Create Group and complete the three drawer steps:

  1. Group details: enter a name and description, then choose Reviewer Group, Review Team, or Approval Role and add a clear function.
  2. Members & access: select at least two active project members, choose one or more permissions, select the environment scope, and set at least two required approvals.
  3. Review: confirm members, permissions, scope, and minimum approvals, then choose Create Group.

Available permissions include Terraform plan review, Terraform apply approval, policy-exception review, production approval access, and emergency-override review.

Create Group drawer on Members and access with synthetic documentation users, review permissions, an environment scope selector, and a minimum approvals selector
Team 4 of 5 · Create a reusable approval groupShow the Details, Members & access, and Review steps with synthetic members and permissions.

Open Reviewer Groups, Review Teams, or Approval Roles and choose Edit on the intended row. Update the same details, members, permissions, scope, or minimum approvals, then choose Save Group.

Review Terraform Approval Mapping to confirm groups with review or apply permissions are visible for routing. Creating a group does not approve a Terraform plan and does not let a member self-approve.

Edit Group drawer for a synthetic documentation approval group over the Team and Access reviewer groups and Terraform Approval Mapping tables
Team 5 of 5 · Edit a group and review approval mappingShow a synthetic group Edit action and Terraform Approval Mapping table.

Reload the selected project and confirm the directory status or group membership, permission, environment scope, and minimum approvals. Review the appropriate audit record for a high-impact change. UI state alone is not proof that the backend mutation or notification delivery succeeded.

Create a project or ask a project administrator to grant you administrator access.

Select a project. The group also needs a name, description, at least two active members, at least one permission, and a minimum approval count no greater than its selected members.

Resend applies to eligible non-active invitations. Revoke applies to active non-owner members. Use the row’s current status to choose the correct action.