Guide

Access review

Who can reach what in the tenant: members with their roles and project access, and every agent credential with its scopes, last use and end date. Unused, never-used, open-ended and orphaned credentials are flagged; for one person it shows what breaks when they leave. The review itself is recorded.

For: Security & compliance, Admin

Doing a review

  1. Look at Flagged credentials: not used for 90 days, never used, no end date, acting for someone who left (those are already refused), expired but not revoked.
  2. Revoke what is no longer needed on the project's Agents page; OAuth connections are removed by their owner or with the membership.
  3. Check People: tenant roles and the projects each person can read.
  4. Record the review with the outcome. It is kept with the counts of that moment in the history (Access and roles) and appears in the audit trail.

When someone leaves

What breaks if they leave? lists their projects, the service tokens acting for them (CI stops when they go: create a new token under someone who stays first), the personal tokens and connections that go with the membership, their open work, and the permissions only they hold in a project (for example the only approver). The tenant's only owner cannot be removed.

Who can use it

Tenant owners, admins and auditors. Coding agents ask the same with get_access_review (optionally for one person) and record the outcome with record_access_review once the person confirms it.