AWRA OpsHub Search

Who Still Needs This Access

Access is granted one request at a time and almost never taken back the same way. A short review of one role, every quarter, asks the only question that matters about each person holding it — and the answer takes effect the moment it is given.

Security & Compliance Washingtone Aura 7 min read

Every permission in a workspace was granted for a reason that was true on the day. The reasons expire quietly. The question worth asking, a few times a year, is not who has access, which any user list can answer, but who still needs it.

Take a clearing and forwarding firm in Mombasa. In March, with the port backed up, three people from operations were given the payments role so that duty and storage charges could be paid the same day. Two months later the backlog is gone and so is the reason. Nobody revoked anything, because nobody is ever asked to. By September seven people can release a payment, and the finance manager can name four of them.

The year-end review an auditor asks for is one answer to this, and we covered it in everyone who could sign on the thirty-first. This piece is about the smaller habit that makes the year-end review short: one role, once a quarter, decided by someone who knows the work.

One role at a time

An access review in AWRA can cover every active user or everyone holding one role. For a quarterly habit the second is the useful one. Choose the payments role and the review takes everyone who holds it, including anyone holding it temporarily through a time-limited grant. That is the easy one to miss: a temporary grant does not show on the role’s member list in most systems, and it is exactly the kind of access that was meant to be short.

The moment the review starts, each person’s access is written down as it stands that day: their roles, any temporary roles with the date each one ends, every permission they hold and how many, any risky pairs of permissions they combine (the segregation of duties conflicts), and when they last signed in. The review is about that snapshot. If somebody’s roles change while it is open, the line still shows what was reviewed, which is what makes it evidence rather than a screenshot of a moving list.

  • Undecided lines come first, and among them the people with the most risky permission pairs, so the reviewer starts where the exposure is.
  • Last sign-in sits on every line. A person who has not signed in since June is the quickest decision in the review.
  • Two filters narrow the list to the lines still pending or to the people with a risky pair.

A list of who has access is a fact. A list of who still needs it is a decision, and someone has to sign it.

Keep or revoke, and what revoke means

Each line takes one of two decisions. Keep changes nothing; the decision and any note become the record. Revoke needs a note saying why, because that note is what an auditor reads, and it takes effect immediately: the person’s account is deactivated, they are signed out of every browser and device, their API tokens are deleted, and any temporary roles they still hold are ended.

Read that twice before the first review, because it decides how you run one. Revoke ends the account, not the role. It is the right answer for the person who left in July and was never switched off. It is the wrong answer for the operations officer who should keep her job and lose only the payments role. For her the decision is keep, with a note that the role is being removed, and then her roles are changed in user management. The review records the intention, and the role change is recorded in the activity log.

A few guards stop a review being used to do something it should not. Nobody can decide their own line; another reviewer has to. The only remaining active administrator cannot be revoked, so a review cannot lock the organization out of its own workspace. Two reviewers working the same list cannot both decide one line. And once the last line is decided the review completes itself, and its decisions are final.

A date, and someone who is reminded of it

A review can carry a due date. Three days before it, the person who started the review and everyone allowed to run access reviews get a reminder by email and in the bell, saying how many accounts are still undecided. If the date passes with the review still open, the reminder repeats once a week until it is finished. An access review left open is itself an audit finding, so it is chased rather than allowed to go stale.

When it is done, the review downloads as a spreadsheet: who was in scope, what each person could do on the day it started, the decision, the note, who decided it and when. Every start, decision, completion and download is written to the activity log.

Quarter Role to review Why that one
January Payments and payment runs Year-end cover and leave approvals were granted in December
April Stores and stock adjustments Stock-take helpers are usually given more than they need
July Payroll and HR Mid-year changes in staff and responsibilities
October Administrators The smallest group, with the widest access, before year-end

The straight answer

What AWRA OpsHub does today

  • Access reviews scoped to one role or to everyone, including people holding the role through a temporary grant.
  • A snapshot per person of roles, temporary roles with their end dates, permissions, risky pairs and last sign-in, taken when the review starts.
  • Keep or revoke per line, with a note required for revoke, no deciding your own line, and the last active administrator protected.
  • Revoke applied at once: account deactivated, every session and API token ended, live temporary roles ended.
  • A due date with reminders three days before and weekly while overdue, and a spreadsheet export of the finished review.

More we can add to your workspace

  • Reviews that start themselves on a schedule, so the payments role is reviewed every quarter without anyone remembering to begin. Commission it
  • A reviewer named for each line, such as the person’s own manager, rather than anyone who runs access reviews. Commission it
  • A remove-this-role decision beside keep and revoke, applied to the person’s roles when it is chosen. Commission it
  • A dormant-account filter that brings forward everyone who has not signed in for a chosen number of days. Commission it

Where we point you to a specialist

  • We will not let a person decide their own line in a review, whatever their role. Somebody else has to look at it.

Scheduled reviews and a remove-this-role decision are the two extensions organizations ask for first.

More we can add

A review that runs itself

The snapshot, the decisions and the reminders are in place. These additions turn the quarterly review into a routine nobody has to start.

Scheduled reviews

One role, one cadence, a review opened on the first of the quarter with its due date already set.

The manager as reviewer

Each line sent to the person who knows the work, with the access team seeing progress across all of them.

Remove one role

A third decision that takes away the role under review and leaves the rest of the account alone.

The short version

Pick one sensitive role a quarter, start a review of it with a due date, and let someone who knows the work decide every line. Revoke the people who have gone. For the people who should stay but lose the role, keep them with a note and change their roles. Four short reviews a year make the year-end one a formality.

Questions for your next review

Who holds this role through a temporary grant?

Watch for

Grants with no end date in sight.

What it tells you

Temporary access that has quietly become permanent.

Who has not signed in this quarter?

Watch for

Names from teams that have moved on.

What it tells you

Accounts that can be revoked today with no disruption.

Who combines two risky permissions?

Watch for

Someone who can create a supplier and approve a payment run.

What it tells you

A segregation question, not only an access question.

Who decided last quarter’s review?

Watch for

The same person every time.

What it tells you

Their own line is the one nobody has looked at.

See governance and roles in AWRA

Roles and permissions, risky permission pairs, temporary access and the access reviews that check them.

Explore governance and roles

Frequently asked questions

Can an access review cover just one role?

Yes. Choose a role when you start it and the review covers everyone holding that role, including anyone holding it through a temporary grant. You can also review all active users at once.

What happens when a reviewer chooses revoke?

A note is required, and the person’s access ends at once: the account is deactivated, signed out of every browser and device, its API tokens are deleted and any temporary roles are ended. Revoke applies to the whole account, not just the role being reviewed.

How do I remove one role from someone without deactivating them?

Decide keep on their line with a note that the role is being removed, then change their roles in user management. The review records the decision and the activity log records the role change.

Can I review my own access?

No. A line for your own account has to be decided by another reviewer.

Will anyone be reminded if a review is not finished?

If the review has a due date, the person who started it and everyone who runs access reviews are reminded three days before it, and then once a week while it stays open past the date.

Share this article

LinkedIn X WhatsApp

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center