Skip to content

Request access, and approve or deny a request

Requesting access is open to everyone. Approving needs the approve requests permission (Manager, Identity Admin, Tenant Owner, Compliance Officer, CISO, Super Admin) and being an assigned approver on the request’s current stage. Administrators with full access to approvals (for example Identity Admins and Super Admins) can also act on requests not assigned to them. Nobody can approve their own request.

Request access (requester)

  1. Open the My Workspace hub β†’ Request Access β†’ Catalog tab (the Enterprise Application Catalog). Only applications an administrator has published, and made requestable for your role, are listed.
  2. Find the application and select Request Access (card view) or Request (list view).
  3. In the panel:
    • Request For β€” Myself, or Someone Else (Managers, Identity Admins, Tenant Owners and Super Admins only).
    • Select Entitlement β€” the role or permission you need. Peer data shows how common it is for people like you.
    • Justification β€” why you need it. Your organisation can make this mandatory and set a minimum length.
    • Access Duration β€” Permanent, Time-Limited, JIT (Hours) or Specific Date. If your organisation caps grants, longer durations are shortened on submission.
  4. Select Submit Now, then Confirm & Submit. Or select Add to Cart to request up to 20 items in one checkout.

Checks that run before the request is created:

Check What you see
SoD conflict with a block rule SoD Conflict β€” Request Blocked; the request cannot be submitted
SoD conflict with a warn rule SoD Conflict Detected; you can submit and the request is flagged
App has a minimum trust score you do not meet Trust Score Too Low; the request is refused

The request then routes through the app’s approval workflow (or the platform default) and stage-one approvers are notified.

Approve or deny (approver)

  1. Open My Workspace β†’ Inbox β†’ Approvals tab (My Pending Approvals).
  2. Select a row to open Request Details: requester, Requested Access (application and entitlement), Business Justification, Risk Check, Approval Workflow stages and Access Expiry.
  3. Optionally set Set / Override Expiry β€” leave blank to keep the requester’s expiry.
  4. Select Approve β†’ Confirm Approve, or Deny β†’ add a Reason (optional, up to 500 characters, shown to the requester) β†’ Confirm Deny. Bulk Approve and Bulk Deny act on the selected rows.

A multi-stage request stays Pending until every stage approves; any denial ends it as Rejected. Your past decisions are under the History tab (Decision History).

After approval

AtmanID does not grant access in the target system on its own. Approved requests wait in the Provisioner Queue (Identity & Access hub β†’ Provisioning Queues β†’ Provisioning tab, Identity Admins and Super Admins):

  • Execute β€” for apps with a connector, creates the account if needed and assigns the entitlements in the target system. The request becomes Provisioned only if every item succeeds; otherwise it stays in the queue to retry.
  • Mark Provisioned β€” after someone has granted the access by hand.

AtmanID does not open a Jira or ServiceNow ticket for an approved request. If your service desk needs to know, add a New Webhook Subscription for the ACCESS_APPROVED event (Platform Config hub β†’ Integrations & API β†’ Developer portal tab) and create the ticket from that event.

Track a request

Requesters use My Workspace β†’ Request Access β†’ My requests tab. Filter by All, Pending, Approved, Rejected or Cancelled; open a row to see each approval stage and the denial reason, if any. An approved request for an app without a connector reads Approved (In Progress) until it is provisioned. A Pending request can be withdrawn with Cancel this request β†’ Confirm Cancel.

Audit trail

Submission writes ACCESS_REQUEST_SUBMITTED (plus ACCESS_REQUEST_SOD_WARNING or ACCESS_REQUEST_SOD_BLOCKED when a conflict is found); each stage decision writes APPROVAL_STAGE_APPROVED or APPROVAL_STAGE_REJECTED; inbox decisions write ACCESS_REQUEST_APPROVED or ACCESS_REQUEST_REJECTED; executing from the queue writes PROVISION_EXECUTED.

Β© AtmanID Β· Privacy