Image
Workflow
Operations

Access provisioning and approval routing

Access requests arrive by chat, get granted by whoever is around, and nobody remembers who approved what. An agent records each request, routes it to the system owner, and passes approved ones to IT. Approving and granting stay with people.

The short answer

Short answer

An agent routes access requests by recording each one with the system, the level of access and the reason, checking it against the requester's role, and sending it to the named owner of that system for approval.

Approved requests go to IT to grant. The agent grants nothing, and a second approver signs off on anything privileged.

Today

Why does nobody know who approved that access?

Someone needs access to the finance tool, so they ask in chat. Whoever has admin rights grants it, because asking the owner would take a day. Six months later the person has moved teams, still has access, and nobody can find the message where it was approved, if it was. Multiply that across every tool a company adds, and the access list stops matching anyone's idea of who should have what.

Who is this for?

An IT lead, systems administrator or operations manager at a company with a growing set of tools and no identity team. It suits businesses that can name an owner for each system and describe, at least roughly, what access each role needs. Granting the access and deciding exceptions stay with people.

What changes when every request has a path?

Part of the requestGranted on requestRouted by an agent
Where it is askedChat, email, in the corridorOne request record, whatever the channel
Who approvesWhoever has admin rightsThe named owner of that system
Fit with the roleNot checkedCompared with the role's usual access, with any difference shown
Privileged accessTreated like any other requestA second approver required
The recordLost in a chat threadWho asked, who approved, who granted, when

How it works, step by step

The agent carries the request from asking to approval. Approval and granting are done by people, in that order.

01

Take the request in any channel you name

Requests made in the IT inbox, the request form or a chat channel you authorize become a request record: who, which system, what level of access, why, and for how long.
02

Check it against the role

It compares the request with the access your role definitions say the requester's role normally has, and shows any difference to the approver. Where no role definition exists, it says so.
03

Route to the system owner

The request goes to the person named as owner of that system. They approve, refuse or ask a question. Silence is not approval, and the agent reminds the owner rather than assuming.
04

Add a second approver for privileged access

Requests for administrator or other privileged access also go to a second approver you name. NIST defines a privileged account as a system account with the authorizations of a privileged user, which is why it gets an extra check.
05

Human gate: owners approve and IT grants

Only after the owner, and the second approver where required, has approved does the request go to IT, who grant the access. The agent approves nothing and grants nothing. In NIST's terms, authorization is access privileges granted to a user, program, or process or the act of granting those privileges, and both halves of that stay with people.
06

Track temporary access

Access granted for a limited time is listed with its end date, and the agent reminds IT and the owner when it should be removed.
07

Prepare the periodic access review

On the schedule you set, it lists who has access to each system, with the approval record for each, so each owner can confirm or remove it.

Never with access

What does the agent never do with access?

Grant or remove access

IT does, after approval.

Approve its own suggestions. It shows the role comparison and leaves the call to the owner.

Treat silence as yes

Unanswered requests are chased, never assumed approved.

Hold admin rights

It needs read access to request records and role definitions, nothing more.

Override an owner. A refused request stays refused unless the owner changes their mind.

Where this fits

Workflow / Automate a Workflow

From request to granted access is a single process, and Tier 1, Automate a Workflow covers it. Your system owners and role definitions are what the readiness checklist will test first. The routing pattern is the same one used in purchase approval workflows that don't stall, and requests that are not about access go through internal request routing and triage. The one-name rule for each approval comes from approval gates. The use case library has more.

How does access routing differ from general IT tickets?

QuestionGeneral IT ticketAccess request
Who decidesIT, usuallyThe owner of the system
What it changesA device or a settingWho can see and change information
What must be keptThe fixThe approval, for later review
When it endsWhen fixedWhen access is removed
Tier 1 / Prove
How It Works

Questions, answered

No. Every request goes to the system owner, read-only included. Routine requests are quick to approve because the role comparison arrives already done.
AI Opportunity Audit · Access requests

Trace every grant back to an approval

Bring the access list for one important system and see how many grants you can trace to an approval.