The job of this console
Review pending requests, fulfill or reject against Employee and asset masters, and close the row so the trail stays on the approval domain. Export only when audit wants a snapshot.
Admin · Access
Access Requests
Review and fulfill elevated access and asset requests from the universal approval inbox.
Scroll to Flowcharts. Scenario: Fulfill an access or asset request.
Elevated access inbox
Granting doors, not inventing a second HR file
Access and asset requests land here so an administrator can fulfill a laptop, badge, or elevated permission from the same universal approval family as leave and timesheet.
Admin → Access requests
Route
/admin/access-requests
Org flag accessRequestsEnabled
Requester (employee) · HR Admin / Org Admin fulfill
Seat at the table
Anyone may raise a request when the flag is on. Fulfillment is for HR Admin and Org Admin. Managers see team items in My Approvals, not this admin register.
The working rhythm
Filter by status, open a row, fulfill against source records, confirm it closes. Do not create a side spreadsheet of laptops — assets stay on the People assets register.
Moments that bring you here
New joiner hardware. Production-admin for an incident. Contractor access that should expire. After offboarding, leftover grants still open.
ⓘ
Fulfillment writes to source records
Closing a request does not create a parallel asset ledger. Employee and asset masters remain the source; this console only routes the decision.
Flowcharts
1 — Approve an access request
Filter pending items, review justification, then fulfill or deny.
flowchart TD
A[Open Access requests] --> B[Filter pending]
B --> C[Open a request]
C --> D{Justified?}
D -->|Yes| E[Approve / fulfill]
D -->|No| F[Deny with reason]
E --> G[Grant recorded]
F --> G
- 1Open the registerAdmin → Access requests.
- 2Filter pendingStatus chips show what still needs a decision.
- 3ReviewCheck persona, asset, and justification.
- 4DecideApprove to fulfill or deny with a reason.
Overview
Access requests are a domain of the universal approval engine. Fulfillment writes to existing people/asset records — this page is not an independent permission store.
How to use
1. Search before paging
Actor, asset, and headline search is faster than scrolling.
2. Deny with a reason
Empty denials create follow-up noise.
3. Check related policies
Some grants still need Roles & permissions after fulfillment.