Run an access review that produces removal decisions
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A manager cannot make a useful access decision from a name and an “Approve” button. Give them the permission being reviewed, the business task it enables, how the person receives it, and the evidence supporting continued need. Ask them to choose retain, reduce, remove, or investigate—then keep the review open until approved changes are verified.
The working unit should be a person or service identity paired with a specific entitlement, not a person paired with an entire workspace. Someone may still need customer-record access while no longer needing exports, membership administration, or access to another team’s records.
This workflow covers recurring reviews of existing access. It does not redesign your roles or assess employee performance. Its central artifact is a workbook that connects evidence, a decision, an authorised change, and a completion check.
1. Set a boundary that makes completeness testable
Write down which workspace, identities, permission types, and snapshot date the review covers. Include privileged roles, team or group memberships, guests, and service identities where those exist. Name what is excluded and who owns the excluded review. “All access” is not a useful scope if nobody knows whether it includes connected tools or shared credentials.
Assign distinct responsibilities:
- Review coordinator: assembles the inventory, routes questions, and tracks outstanding work.
- Business reviewer: explains which tasks require continued access.
- Resource owner: confirms whether the requested scope is appropriate for the resource.
- Authorised implementer: makes approved changes.
- Verifier: checks the resulting access, preferably someone other than the implementer for sensitive changes.
One person may hold several responsibilities in a small team, but record which responsibility they are exercising. Avoid letting a person silently approve their own privileged access; route that decision to another accountable owner.
Record changes made during the review. Otherwise, a correct opening inventory can become an inaccurate completion record.
2. Build evidence around entitlements, not just names
For every review row, collect the identity, account type, current entitlement, resource scope, grant path, business owner, and evidence date. Grant paths matter: access may come directly, through a group, or through a broader role. Removing one path may leave another intact.
Add the current business task and any useful activity evidence available to authorised reviewers. Keep activity evidence narrow: whether a relevant function was used may help assess access need; a detailed account of someone’s working habits is outside this review’s purpose.
Recent use is not sufficient justification, and no recent use is not sufficient reason to remove. A person may use an unnecessary export permission routinely. Another may legitimately hold an infrequently used emergency responsibility. Ask what task requires the access and what would fail without it.
If reports are unavailable, document a manual inventory method. Record which membership screens, group lists, resource-sharing views, or administrator records were inspected, by whom, and when. Have a second person reconcile that list against another available source. Identify blind spots explicitly; do not label a partial inventory complete.
Check your workspace and current plan for available reporting, permission granularity, and change mechanisms. This process does not assume a particular product exposes every field or supports every suggested reduction.
3. Give reviewers four decisions with concrete tests
Ask the reviewer to answer: “Which current task requires this permission, on which resources, and could a narrower permission support it?” Use the following decision rules.
- Retain: the task and scope are justified. Record the reason, evidence, and any expiry or next-review trigger.
- Reduce: the task remains, but the current permission is broader than necessary. Specify both what stays and what must go.
- Remove: there is no current authorised need for the entitlement. Identify the grant paths to revoke.
- Investigate: evidence is missing, conflicting, or insufficient to choose safely. Name the question, owner, and decision deadline.
“Still works here” is not a business justification. Neither is “might need it.” A useful answer identifies a responsibility, such as handling assigned support cases, and connects it to the minimum needed scope.
The OWASP authorization guidance recommends least privilege. For this review, apply that principle by examining individual entitlements rather than renewing every permission bundled into an account. That guidance is not evidence that any particular workspace implements a specific control.
Make “investigate” a real work queue, not a softer version of retain. A missed deadline should trigger escalation to a named owner, not silent approval or an unplanned automated removal.
4. Use a filled workbook, not an empty checklist
Fictional worked example: Every person, workspace, date, identifier, evidence reference, and outcome below is hypothetical. The entries illustrate a recommended workflow, not an actual audit or product capability.
The hypothetical review covers the Harbor Support workspace as of 4 May 2026. Its scope includes human accounts, guests, and a service identity. The connected finance workspace is excluded and has a separate owner. Imani is coordinator, team leads provide business decisions, Rowan owns the workspace, Jules implements changes, and Casey verifies them.
Use separate workbook tabs for inventory and decisions, unresolved questions, and execution evidence. Link them with stable row IDs. Store supporting evidence in a restricted location; reference it rather than copying customer records or credentials into the workbook.
Tab A: Inventory and decisions
- AR-01 — Maya Chen, support agent. Current access: read and update assigned support records through the Support Agents group. Evidence: membership snapshot INV-01 and team lead confirmation BUS-01, dated 5 May. Business justification: owns the current escalation queue. Reviewer: Lena, support lead. Decision: retain. Reason: scope matches assigned work. Unresolved question: none. Next trigger: queue reassignment or the next scheduled review.
- AR-02 — Tomas Reed, team lead. Current access: workspace administration through a direct role; assigned-record access through Support Agents. Evidence: INV-01 and an administrator-role inspection INV-02. Business justification: still handles cases, but no longer administers membership. Reviewer: Rowan. Decision: reduce. Target: remove the direct administrator role; retain Support Agents membership. Unresolved question: confirm that no scheduled administrative task still depends on Tomas. Target date: 7 May.
- AR-03 — Priya Shah, former project contractor. Current access: read-only access to the Migration Archive through Migration Guests. Evidence: group snapshot INV-03 and project owner confirmation BUS-03 that the assignment ended. Business justification: none remaining. Reviewer: Devon, project owner. Decision: remove. Target: revoke archive access and guest membership after checking for other grants. Unresolved question: none. Target date: 6 May.
- AR-04 — svc-report-export, service identity. Current access: read and export across support records through Reporting Services. Evidence: INV-04; available activity record shows a recent export but does not identify the consuming workflow. Business justification: unconfirmed weekly reporting dependency. Reviewer: Rowan. Decision: investigate. Question: which workflow uses it, who owns that workflow, and does it require workspace-wide scope? Owner: Niko, reporting lead. Decision due: 8 May. No removal authorised yet.
- AR-05 — Elena Cruz, operations analyst. Current access: read and export through Analysts, plus a direct export grant. Evidence: INV-05 and reporting-owner confirmation BUS-05. Business justification: prepares a summary from approved reports; raw-record export is no longer required. Reviewer: Niko. Decision: reduce. Target: retain approved read access while removing export through both grant paths. Unresolved question: can the available permission model separate read from export? Target date: 8 May.
- AR-06 — Omar Vale, temporary incident coordinator. Current access: membership administration through a temporary direct grant. Evidence: INV-02 and incident-owner confirmation BUS-06. Business justification: incident coordination has ended. Reviewer: Rowan. Decision: remove. Target: revoke membership administration, preserving ordinary case access. Unresolved question: none. Target date: 6 May.
Tab B: Questions and bounded exceptions
- AR-02: Rowan confirmed on 6 May that Jules now owns membership changes. Question resolved; reduction authorised.
- AR-04: Niko must identify the workflow and accountable owner. Rowan authorises temporary continuation through 8 May while the dependency is checked. Record the exposure: workspace-wide export remains possible. Escalate to Rowan if unresolved; do not close the row.
- AR-05: Jules’s hypothetical permission inspection confirmed a narrower read-only option is available. Niko approved that target on 7 May. Both the group-derived and direct export grants must be addressed.
If the narrower option had not existed, AR-05 would remain unresolved until the owner chose a supported alternative or documented a time-bound exception. Do not record an unimplementable reduction as completed.
5. Separate approval from execution and verification
A decision is an instruction, not proof of a changed permission. Use distinct states: awaiting decision, approved, scheduled, applied, verified, blocked, and reopened. Keep the decision field separate from the execution state so that “remove” never reads as “already removed.”
Before implementation, compare the approved target with current access again. A group or role may have changed since the snapshot. For shared grants, check who else would be affected; removing a permission from a group can change access for people outside the reviewed row.
Tab C: Hypothetical execution and verification ledger
- AR-02 — verified. Approval: Rowan, 6 May. Applied: Jules removed Tomas’s direct administrator role on 7 May. Evidence CHG-02 records the role change. Casey inspected the resulting role and group assignments in VER-02: administration absent, Support Agents membership retained.
- AR-03 — verified. Approval: Devon, 5 May. Applied: Jules removed Priya from Migration Guests on 6 May. Casey checked archive sharing and other applicable memberships in VER-03; no remaining archive grant was found in the reviewed scope. An authorised access check confirmed the archive was unavailable. Evidence references: CHG-03 and VER-03.
- AR-05 — verified after rework. Approval: Niko, 7 May. Jules initially removed the direct export grant, but Casey found export remained through Analysts. State changed to reopened. Jules then assigned the supported read-only scope and removed the broader membership. VER-05 records export unavailable and required read access preserved on 8 May.
- AR-06 — verified. Approval: Rowan, 5 May. Jules revoked the temporary administrative grant on 6 May. Casey’s resulting-access inspection in VER-06 confirmed that membership administration was absent and ordinary case access remained.
- AR-04 — open. No change applied. No completion evidence claimed. Investigation and temporary-continuation deadline remain visible.
Use authorised testing methods; do not ask users to share passwords. Where effective-access views or safe access checks are unavailable, record the verification method and its limits rather than asserting complete revocation.
6. Recover from uncertainty without rubber-stamping it
Missing owner: route the entitlement to the workspace owner for a decision. For service identities, identify dependencies before disabling access; unexplained activity is a reason to investigate, not proof that broad access is justified.
Reviewer disagreement: record the competing task requirements and ask the resource owner to resolve scope. Preserve the disagreement instead of replacing it with a vague approval.
Broken work after a change: validate the reported dependency. If restoration is authorised, record exactly what was restored, why, and when it will be reviewed again. Reopen the original row; do not erase the earlier removal evidence or quietly restore a broader role.
Removal did not take effect: inspect alternate grants, inherited membership, and any documented session or credential handling relevant to that system. Apply further changes only with authorisation. A successful change request alone does not establish that the identity lost access.
7. Close against evidence, then measure the next review
Report decision counts separately from verified changes. A high approval count says little about whether access is appropriate, and a high removal count is not a target worth gaming.
In the hypothetical workbook, there are six entitlement rows: one retain, two reduce, two remove, and one investigate. Four change decisions have verified completion; one investigation remains open. Elena’s reopened row also exposes a useful failure mode: checking only direct grants would have missed effective export access.
For your review, track inventory gaps, decisions without specific justifications, approved changes awaiting verification, overdue investigations, and changes reopened after failed checks. Describe the review boundary alongside those measures so a partial inventory does not look like complete coverage.
Next action: choose one bounded workspace and populate the workbook before requesting approvals. Every row should have an identified grant path, a business reviewer, a concrete decision or owned question, and an execution state. Close each approved removal only when the evidence shows the intended access is gone within the reviewed scope.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications