Audit a person’s access and a resource’s audience

Use both the member view and Inventory to verify who can do what.

An access review needs two perspectives: what this person can use, and who can use this resource. Team provides a member record for the first and Inventory rosters for the second.

Review one person

1. Open Team and select the member in the correct organization.
2. Confirm the organization role. Owners and Admins have broad access; Viewers remain read-only.
3. Review Spaces and Operations access.
4. Review Space memberships and the Space-access mode. Treat summary counts as an overview, not a complete effective-access report.
5. Inspect project overrides and Space blocks, including exceptions retained beneath a blocked Space.
6. Review shared overviews separately.
7. Review primary department and explicit creation exceptions.
8. Review Operations scopes and any sensitive or destructive powers relevant to the person’s work.

Review one resource

Open Team → Inventory, select the Space or project, and open its access roster. Read the effective access level for each person. The source labels help explain the result; a label or stored grant alone is not the final answer.

Check a Space and a sensitive project separately. A direct project grant can explain project access even when the Space roster does not show access. A primary department explains creation authority and is not evidence that the Space has been shared.

Make a focused correction

If the person lacks one project, review its sharing. If they lack a creation destination, change creation governance. If they cannot perform one operational action, review the role and relevant scope. Avoid assigning Admin simply to make a confusing combination disappear.

When withdrawing access, look for alternate sources. Removing one project override can reveal inherited access. Unblocking a Space can reactivate retained project overrides. Changing a primary department does not remove old Space memberships or direct project shares.

Verify and record the outcome

Refresh the resource roster after the change. Ask the affected Member to try the intended action and an action that should remain unavailable. Record the person, resource, reason, effective result, and review date in your company’s chosen review record.

Repeat this review when someone changes responsibilities, when a project is moved or published, and when the company introduces sensitive departmental work. A routine review is especially useful for temporary cross-department collaborations.

When a review includes an organization-role change, inspect the resulting scopes again: the role-change flow writes defaults for the new role. If a former member returns, review their effective resource access and any stored exceptions before treating the new invitation as a clean permission reset.