Skip to content

Build a custom approval workflow

Approval workflows are reusable templates of one to ten stages. Templates and approver groups are on Platform Config → Access & Approvals, tabs Approval workflows and Approver groups. Creating and editing them needs Identity Admin, Tenant Owner or Super Admin; Compliance Officer and CISO can view. For a worked scenario, see the workflow designer tutorial.

1. Create an approver group (optional)

Use a group when any one of several people may approve a stage.

  1. Approver groups → New Group. Enter a Group Name and an optional description, then Create Group.
  2. Click the group to expand it, pick a user in Add member… and click Add. Repeat for each member.

Every member except the person receiving the access is asked to approve; the first decision counts. A group with no eligible members falls back to the application owner. Deleting a group does not update templates that use it.

2. Create the template

  1. Approval workflows → New Template.
  2. Enter a Template Name and an optional Description.
  3. Under Applies to Risk Levels, select the levels (Low, Medium, High, Critical) this template should handle automatically.
  4. Tick Set as default template if it should be the final fallback. Only one template can be the default.
  5. Add stages. The editor opens in Visual; List and Code (a YAML manifest) are the other views. For each stage set a label, an Approver Role and an SLA in hours:
Approver Role Who approves
Manager The requester’s direct manager
App Owner The application owner set in the App Registry
Entitlement Owner The owner set on the entitlement
Compliance Officer A user with that role
Named Individual The person you pick
Approver Group Any member of the group you pick

Identity Admin and Security Analyst are also listed, but currently route to the application owner (or an administrator) rather than to everyone with that role.

  1. Optional in Visual view: Add Condition branches on Risk Level, Entitlement Count, User Type, Department or Sensitivity Level; Add Notification emails the manager, security team or requester, or calls a webhook.
  2. Set the SLA-breach policy: At the deadline choose Auto-reject (fail-closed) (default) or Auto-approve (fail-open) with a risk ceiling, plus a Decision deadline (days) (default 14) and Escalations before reassign (default 3). A breached stage is re-notified daily, then reassigned to the approver’s manager.
  3. Click Create Template.

Each save keeps a version; History lets you Restore an earlier one. The same person cannot approve two stages of one request, and requesters cannot approve their own requests.

3. Attach the template

Templates are chosen per access request in this order. There is no binding by request type.

  1. Entitlement override: App Registry → the application → ⚙ Config → Access & approvals → expand Entitlement-level overrides and pick the template next to the entitlement. It saves immediately.
  2. Application default: in the same section, choose the template under Approval workflow and click Save.
  3. Risk level: a template whose Applies to Risk Levels includes the entitlement’s risk (Medium if it has none). If several match, the default template wins; otherwise avoid overlapping risk levels.
  4. Default template, then any template.

4. Test it

  1. As a test requester, open My Workspace → Request Access → Catalog, add the entitlement to the cart and expand it in the cart (the arrow next to the item, tooltip Show approval chain). The stages and their SLAs are listed before you submit.
  2. Submit. As the stage-1 approver, open Inbox → Multi-stage (only requests with more than one stage appear there; single-stage requests are in Approvals).
  3. Open the request: Approve Stage advances it; Reject needs a reason, then Confirm Rejection. The final stage’s approval approves the whole request.

Not supported today

  • A dry-run or simulate button (use the cart preview).
  • Date or time conditions, and location conditions.
  • Per-stage escalation targets.
  • Min approvals / Min rejections in List view may not take effect for templates saved from the Visual view; treat every stage as single-approver.

Audit trail

WORKFLOW_TEMPLATE_CREATED, WORKFLOW_TEMPLATE_UPDATED, WORKFLOW_TEMPLATE_RESTORED, APPROVER_GROUP_CREATED, APPROVER_GROUP_MEMBER_ADDED, ENTITLEMENT_WORKFLOW_OVERRIDE_UPDATED, APP_UPDATED, APPROVAL_STAGE_APPROVED, APPROVAL_STAGE_REJECTED, SLA_BREACH_ESCALATION. See the audit trail.

© AtmanID · Privacy