Skip to content

Build a custom approval workflow with the Workflow Designer

What you’ll do

You’re Sarah Chen. Your CISO just established that Salesforce System Administrator access requires both the requestor’s manager AND the application owner to approve, in serial — and when the requester is a contractor or vendor rather than an employee, security must additionally sign off. Today this happens via Slack-back-and-forth, gets lost, and produces zero audit trail. After this tutorial, the workflow runs itself.

This walks the canonical custom-approval-workflow scenario. Time investment: ~25 min for the first workflow design + perpetual zero-touch for every subsequent request that matches.

Prerequisites

  • identity_admin role
  • The target entitlement exists in the application (e.g., Salesforce — System Administrator per Onboard your first app), with an entitlement owner set
  • A clear policy from your CISO/legal on what approvers + routing are required
  • Optional: an approver group for the security team (Platform Config → Access & Approvals → Approver groups)

Step 1 — Create the workflow template

Navigate to Platform Config → Access & Approvals → Approval workflows (the Approval Workflow Templates page) and click New Template. Pick a clear name + describe the policy in plain English:

  • Name: salesforce-admin-approval
  • Description: “Multi-stage approval for Salesforce System Administrator. Manager → entitlement owner → security (non-employees only). 5-day SLA per stage.”
  • Risk Levels: leave these unchecked. Checked levels make this template the automatic route for every request at that risk level; this template should apply only where you bind it (Step 3).

You don’t need a -v1 suffix: every save records a version in the template’s Version history (Step 7).

Step 2 — Define the stages

Templates are serial stages of approvers. Each stage has a Stage Label, an Approver Role, an SLA (hrs), and a quorum (Min approvals / Min rejections, both default 1). Add three stages:

Stage 1: Manager approval (SLA 120 hours)

  • Approver Role: Manager — the requester’s direct manager. If the requester would be approving their own request, AtmanID escalates up the management hierarchy.
  • Min approvals: 1

Stage 2: Entitlement owner approval (SLA 120 hours)

  • Approver Role: Entitlement Owner — the named owner of the entitlement being requested (the Salesforce admin owner you assigned in Onboard your first app). Use App Owner instead if you want the application owner.
  • Min approvals: 1

Stage 3: Security signoff (SLA 72 hours; CONDITIONAL — non-employees only)

  • Approver Role: Approver Group → your security team group (any member can approve), or Security Analyst (any user with that role)
  • Min approvals: 1

Then make Stage 3 conditional. Add a condition — field user_type, operator neq, value employee — and, in Visual view, connect the condition’s Yes branch to Stage 3 and its No branch to the end of the workflow. Branch connections are only configured in Visual view.

The condition is the load-bearing detail. AtmanID evaluates it when the request is submitted, against the requester’s identity type; for employees, Stage 3 is skipped and the workflow completes after Stage 2 approval. Conditions can test risk_level, entitlement_count, user_type, department, location and sensitivity_level — there is no date-based condition.

Finally, set the SLA-breach policy: what happens At the deadline (Auto-reject (fail-closed) — the right choice for admin access — or Auto-approve), the Decision deadline (days) (default 14) and the Escalations before reassign (default 3). Overdue stages escalate first; after that many escalations the stage is reassigned; at the decision deadline the request is auto-rejected.

Save. AtmanID audits WORKFLOW_TEMPLATE_CREATED.

Step 3 — Bind the workflow to the entitlement

Navigate to Identity & Access → Applications → Salesforce Production → ⚙ Config → Approval Workflow. Leave the app default as it is, open Entitlement-level overrides, and pick salesforce-admin-approval for System Administrator.

Save. AtmanID audits ENTITLEMENT_WORKFLOW_OVERRIDE_UPDATED with the entitlement and the workflow_template_id. An entitlement has at most one override.

From now on, every access request for Salesforce — System Administrator runs through this workflow. Other Salesforce entitlements keep their normal routing, most specific first: the app’s default workflow, then a template whose Risk Levels include the request’s risk, then the tenant’s default template, then a single implicit approval stage.

Step 4 — Preview the approval chain

There is no simulate mode for templates. Instead, preview the chain the way a requester sees it: in My Workspace → Request Access → Catalog, add Salesforce — System Administrator to your cart. Before anything is submitted, the cart shows which template will apply, its stages, the approvers and the SLAs — no request or audit record is created.

Check:

  • The template shown is salesforce-admin-approval (if not, re-check the override in Step 3)
  • Stage 1 (manager) → Stage 2 (entitlement owner), with your SLAs
  • The preview evaluates conditions as an employee, so Stage 3 does not appear. To see Stage 3 fire, submit a [Test] request as a contractor test user and cancel it afterwards.

If the path doesn’t match your CISO’s intent, fix the template now. Catching design issues here saves hours of back-and-forth on real requests.

Step 5 — Watch a real request flow through

A user submits an access request for Salesforce System Administrator. The workflow instantiates:

Request submitted
→ Audit row: ACCESS_REQUEST_SUBMITTED
Stage 1: Manager review
→ Notification to the requester's manager
→ Approved (or rejected — the request is rejected, requester notified)
→ Audit row: ACCESS_REQUEST_STAGE_APPROVED
Stage 2: Entitlement owner review
→ Notification to the entitlement owner
→ Approved
→ Audit row: ACCESS_REQUEST_STAGE_APPROVED
Stage 3: Security signoff (skipped for employees)
Workflow completes:
→ Audit row: ACCESS_REQUEST_APPROVED
→ Provisioning runs (connector, or a provisioning ticket for a disconnected app)

Every record is tied to the access request it belongs to, so an auditor can reconstruct the whole chain from that one request.

Step 6 — Approver delegation (for vacations)

The Salesforce admin owner is going on vacation for two weeks. Without delegation, every Stage 2 approval would block her inbox while she’s away.

She delegates from My Profile: in the delegations panel she enters the Delegate’s Email (e.g., her direct report), a Starts date and a Valid Until date, and an optional reason. AtmanID audits APPROVAL_DELEGATED.

While the delegation is active, her delegate can decide the approvals routed to her; a decision made that way is audited APPROVAL_DECIDED_AS_DELEGATE, so the record shows both the original approver and the person who decided. The delegation ends at its Valid Until date, or earlier if she revokes it (APPROVAL_DELEGATION_REVOKED).

Step 7 — Iterate on the policy

Six months in, the CISO updates the policy: Stage 3 (security signoff) should fire NOT just for non-employees but also for anyone outside the US.

Edit the template: add a second condition (location neq US) and, in Visual view, connect the first condition’s No branch to it, its Yes branch to Stage 3 and its No branch to the end — so either condition can route to Stage 3. Save. AtmanID audits WORKFLOW_TEMPLATE_UPDATED and records the previous definition in Version history, from which you can view or restore any earlier version (WORKFLOW_TEMPLATE_RESTORED).

The binding from Step 3 doesn’t change — the entitlement still points at salesforce-admin-approval, and new requests use the updated definition. “What was the policy when this access was granted in 2026 Q1?” is answered from the version history.

This is the version-history pattern. Every saved version is kept; template and binding changes are themselves audited.

What just happened

You converted “approval policy lives in Slack” into:

  • Codified policy — the workflow template IS the policy, with every saved version kept
  • Zero-touch execution — every request for the entitlement runs the workflow automatically
  • Full audit trail — every stage decision, escalation and delegation audited with actor + timestamp
  • CISO-grade evidence — auditors asking “show me how Salesforce admin access was approved in Q2 2026” get the answer from the audit trail, per request

This is the shape of every workflow you’ll build — same flow whether it’s Workday admin, Snowflake DBA, GitHub admin. Time investment is once-per-policy, not per-request.

Common pitfalls

  • Assuming self-approval is impossible everywhere. The Manager role escalates up the hierarchy when the requester is their own approver. Role-pool stages (e.g., Security Analyst) don’t — keep requesters out of the groups that approve their own requests.
  • No SLA-breach policy. Stages without a sensible SLA and deadline sit open. Set 72–120 hours per stage and fail-closed at the deadline for privileged access.
  • Checking Risk Levels by accident. A checked risk level routes every request at that risk to this template, not just the entitlement you bound.
  • Not binding workflow to the entitlement. Template exists but isn’t applied = real requests use the default routing + your custom one is just decoration. Bind explicitly.
  • No preview before real requests. Catches design issues before they become operator pain. Always check the cart preview.

Going further

  • For the API path to manage templates as code, see Reference → API Reference /api/v1/workflow-templates (GET lists, POST applies a manifest in JSON or YAML, idempotent on metadata.name; needs read:workflows / write:workflows). The template page’s Code panel shows the manifest for any template.
  • For the GitOps approach to managing workflows as code (the atmanid/workflow-sync GitHub Action), see the v1.9.0 changelog entry
  • For the architectural model behind workflow execution, see Architecture → RBAC architecture
  • For the audit-trail forensic patterns auditors use to verify workflow execution, see Iris for compliance officers

© AtmanID · Privacy