Review access approval requests
To review access approval requests, start with a signed-in account and a documented reason for the security or governance task. In Admin, filter pending requests, open request, verify requested scope, and approve minimum access. Use the least access needed, verify the subject and scope, and keep secrets and personal data out of notes and support evidence.
Before you start
- A signed-in account and a documented reason for the security or governance task
- Verify actor, scope, time, and requested access before making or approving a change
Steps
- Open /approvals and filter to pending requests for the intended Business Account and branch.
- Open one request and verify requester, requested capability, branch scope, reason, and recorded time.
- Approve only the minimum justified scope, or reject with a clear reason; submit the decision once.
- Refresh and confirm the final decision state before handling another request.
Expected result
The request shows one final approved or rejected decision with the reviewed requester, capability, branch scope, reason, and time. Submitting once does not grant broader access than the approved request.
Permissions
- Approvals requires rbac.write; the approved scope cannot exceed the request or the operator’s own authorization.
Troubleshooting
A pending request cannot be found or opened.
Confirm Business Account, branch, pending filter, requester, and request time. Do not create or approve a substitute request; preserve the safe request reference for Support.
Approve or reject has no final state.
Refresh the same request before submitting another decision. Stop if status changed or scope is unclear; report the request reference, reviewed capability and branch, intended decision, and time.
Related articles
Enroll the signed-in user’s trusted authenticator without exposing the QR secret or one-time code.Manage personal privacy data
Request the signed-in person’s data export or account deletion once and track the returned status.Review audit and communication history
Filter and preserve scoped audit or communication evidence without treating the history as editable data.
Open in TajerGo
Sign in with the appropriate role and confirm your Business Account and branch before continuing.
Read as Markdown · Guidance for support agents
Last reviewed 2026-09-06 · Send documentation feedback