Skip to content

Access request approval: one reviewer for restriction, two plus Legal for revocation

How approving an access request works: one reviewer signs off on restricting or suspending access, two reviewers plus Legal sign off on revoking it.

Updated · 6 min read

In short

  • Restricting or suspending someone's account or access needs one reviewer to sign off; revoking it needs two reviewers plus Legal - the measure decides the path, not who happens to be free.
  • The reviewer sees the exact subject, the stated grounds and the facts behind the request, not a paraphrase typed into a DM.
  • Once decided, the request produces a signed grant and a record anyone can produce later, including while it is still pending.
  • DueReason records the decision and issues the signed grant; it does not remove access itself - executing the change stays on the requester's own tooling.

Access gets restricted, suspended or revoked ad hoc in most organizations today - a message to an admin, a ticket with no second signature, a line in a spreadsheet. DueReason's access-or-account-action template turns that into a workflow with the right number of reviewers for what is actually being asked.

The two paths: restriction or suspension vs. revocation

Every access request names a measure: restrict, suspend or revoke. The two lighter measures - restricting or suspending - route to a single reviewer from the account-reviewers group, with a written reason recorded as evidence. Revoking access routes differently: two reviewers from that group, then a separate approval from Legal, each with a written reason. The workflow is chosen by the measure on the request, not by who files it or which admin happens to be online.

A restriction or suspension is usually reversible - a password reset, a re-enabled account, a shortened hold. A revocation is not: once access is gone and the grounds are recorded, undoing it means filing a new request from zero. Two reviewers catch a revocation that one person got wrong on their own, and a separate Legal step exists for the cases - a termination, a contract dispute, a policy breach - where the grounds matter enough that a non-admin signs off too, independent of the two account reviewers.

What the reviewer actually sees

The request carries a subject (who or what account is affected), the measure, an optional duration in days for a time-bound restriction, the stated grounds and the supporting facts - up to 20,000 characters, enough for an incident writeup, not just a one-line reason. A reviewer answering is shown this exact payload, not a summary someone typed into a chat message, and the request itself cannot be approved by the person who filed it.

The record once it is decided

A decided access request produces a signed grant bound to that exact payload, and the request can produce a record - JSON or CSV - at any point, including while it is still pending. If anything in the payload changed after a reviewer saw it, the grant no longer matches and is refused rather than silently applied to something slightly different from what was approved.

What this does not do

DueReason has no built-in connector to an identity provider or HR system, and it does not deprovision anything itself. It records the decision, who made it and on what grounds, and issues the signed grant once the required reviewers have answered. Acting on that grant - disabling the account, revoking the API key, pulling the badge - is still done with the requester's own tooling; the workflow is the paper trail and the gate before that action, not the action itself.

Questions

Can the person whose access is being restricted or revoked approve their own request?
No. DueReason never lets the person who filed a request be one of the people who approves it, regardless of which group they belong to - this applies to every request, not only access actions.
Does restricting or suspending access ever need Legal to sign off?
Not by default. Only a revoke measure routes to Legal after the two reviewers; restricting or suspending access needs a single reviewer with a written reason.
Does DueReason actually disable the account or revoke the access?
No. It records the request, routes it to the right reviewers for the measure, and issues a signed grant once approved. There is no connector that removes access on its own - whoever acts on the grant still does that in the system where the account lives.

Put a second approver on every access request

Create an account, install the access-or-account-action template, and route restrictions, suspensions and revocations to the reviewers who should see them - with a record you can still produce later.

Create your account

Sources

This guide explains the regulation as we read it; it is not legal advice. Check the official text and your national law, which may add obligations.

Start with DueReason

Create a free account, try it live, or talk to us about your workflow.

Get product updates