Overview
Once you've built the basics of a policy, you can extend it with more sophisticated step types to handle parallel reviews, location-specific approvers, and additional risk screeners.
This article covers three advanced building blocks: Concurrent approval steps for notifying multiple teams simultaneously, Location Overrides for assigning different approvers per office while maintaining a single policy, and Risk Intel steps for adding screeners, such as Visit Frequency, to the workflow. These can be combined with the Condition and Approval steps covered in Creating a Policy.
PREREQUISITES
You'll need to have already built the Policy fields, Conditions, and Approval steps before adding in any advanced policy steps.
Concurrent approvals
Concurrent approval lets you notify multiple review parties simultaneously. This is useful when several teams, such as security, trade compliance, and operations, all need to sign off on a visit without waiting on each other.
How concurrent approval works
All approvers within a Concurrent step are notified simultaneously. Each reviews and responds independently. The workflow only advances once every required approver has approved. If any single approver rejects the invite, it is rejected immediately, regardless of whether others have responded.
Adding a concurrent step
In the policy builder, drag the Concurrent block from the left panel onto the canvas.
Inside the Concurrent block, add the Approval steps you want to run in parallel, for example, Trade Compliance, Security, and Operations approvals.
Assign an approver to each step.
Connect the Concurrent block's input and output nodes to the rest of your workflow.
Click Save or Publish when ready.
Tips for using Concurrent approvals
All approvers in a Concurrent step must approve for the workflow to continue. There is no "majority" or "quorum" option.
If one approver rejects, the invite is rejected immediately.
You can add as many approval steps inside a Concurrent block as your workflow requires.
Concurrent steps can be combined with Conditions and sequential steps in the same policy.
Location Overrides
Location Overrides let you apply a single policy across all your office locations while assigning different approvers at each site. Instead of building a separate policy for each location, you configure a single policy with a default approver and set location-specific overrides where needed.
How location overrides work
Each Approval step has a Default Approver, the person who handles reviews at any location without a specific override. When an override is set for a location, only that override approver is notified for invites from that site. The default approver is not included for those locations.
Setting up location overrides
In the policy editor, select an Approval step on the canvas.
In the step panel, enter a Default Approver.
Under Location Overrides, click Set by location.
In the Location Overrides modal, search for a location and assign one or more approvers.
Repeat for any other locations that need a dedicated reviewer.
Click Apply.
Tips for using Location overrides
Locations without an override automatically use the default approver. You don't need to configure every location.
The location list is searchable and scales to large deployments.
Each location supports multiple approvers.
To enforce the same policy across all locations, associate it with a global sign-in flow.
Risk Intel Step
Risk intel steps are additional screeners you can add to your policy, such as blocklist and visit frequency.
Within the Policy builder, click Risk Intel to add a new step to the workflow builder.
Select your risk intel. Currently available: Visit Frequency.
Visit Frequency: set Threshold Days (how many days to look back) and Threshold Count (number of visits within that period).
After configuring the Risk step, you can add it to your workflow.
Once you've completed configuring your advanced policy fields, you're ready to assemble your Policy!