Skip to Content

Workflows

Approval flows that route access requests to reviewers, and the inbox where those requests are decided.

Requiresworkflows

Plan note: Approval workflows are available on the Advanced plan and above (Trial includes up to 3 workflows). The approval inbox itself is always available for any requests that already exist.

Workflows add a review step in front of application access. Instead of access being granted the moment someone asks for it — or the moment an administrator assigns it — a request can be routed to one or more reviewers who approve or reject it. Once approved, the platform performs the assignment automatically.

This area has three parts that work together:

  • Approval flows define when a review is required and who decides, before access is granted. You build rules that match users by directory, group, or identity, and conclude with one of three outcomes: reject outright, approve automatically, or send the request through a sequence of human approvers. See Approval flows.
  • Access certifications periodically re-check access that already exists, on a recurring schedule, and let a reviewer certify or revoke it. See Access certifications.
  • The approval inbox is where both pending requests and due access reviews land. Reviewers see what is routed to them, decide each one (with a reason), and consult the history of past decisions. See Approvals.

How a request flows

  1. A user requests access to an application, or an administrator assigns access to one.
  2. The platform finds the approval flow bound to that application and evaluates its rules against the affected user.
  3. The first matching, active rule decides the outcome:
    • Rejected — the request is denied with no further action.
    • Automatically approved — access is granted immediately, with no human review.
    • Approval process — the request becomes pending and is routed to the first level of approvers.
  4. For an approval process, each level is notified in turn. When an approver at the current level approves, the request advances to the next level; once the final level approves, access is granted.
  5. Every decision is recorded in the audit log.

Where approval applies

An approval flow only takes effect once it is bound to an application, on the application's policy settings, and it governs self-service requests: users request access themselves and the chosen flow decides.

Assignments an administrator makes are not routed through approval. Limit who may assign an application by putting it in a workspace with managed access, and review granted access with an access certification campaign.

See Applications for how to bind a flow to an application.

In this section

PageWhat it covers
Approval flowsBuilding flows: rules, conditions, outcomes, sequential approval levels, draft and publish
Access certificationsRecurring re-review of existing access: campaigns, reviewer rules, certify and revoke
ApprovalsThe shared inbox: reviewing, approving, rejecting, certifying, revoking, and viewing history

Administrators who only need to act on requests routed to them can go straight to Your tasks & approvals.

On this page