Overview
Advanced Visitor Approvals lets you build conditional approval workflows using Policies, a configurable container that defines who approves what, under which circumstances, and in what order. Visual Compliance is a restricted party screening solution that checks whether a visitor's information appears on any lists of restricted parties you've selected.
You can add Visual Compliance as a step to your Policy, strengthening and streamlining your approval process. The outcome of that step (whether the visitor matches a restricted party) can branch the flow and route the visit to a specific approver, such as your trade compliance or security team, before the visitor is cleared.
PREREQUISTES
You'll need to have connected your Visual Compliance account to Envoy before you can add it to a policy. Learn more about how to install Visual Compliance.
Building a Policy with Visual Compliance
Step 1: Create or open your policy
Navigate to Global overview > Visitors > Policies and Create a policy or open a draft of an existing policy.
If you're creating your policy, give the policy a concise Name and Description, then click Create. You'll be taken into the policy builder, which opens with a Workflow trigger node.
Learn more about building a policy.
Step 2: Add the Visual Compliance step
In the policy builder, click Risk Intel, then click Visual Compliance.
Your new step will appear in the canvas. Click on the step to open its settings.
Give your new step a name.
Select which Fields to screen: Visitor name (required), Company (optional), and Address.
Any fields not included in your sign-in flow will be automatically added by the system. You can change the field label that visitors see by entering a new one, or leave the box blank to use the default.
Step 3: Connect your Visual Compliance step to your policy workflow
Decide where you want your Visual Compliance step to run in relation to the rest of the policy. You have the option to screen all visitors by including the screener step at the beginning of the policy, or only screen visitors who meet certain conditions
Connect the step so it runs at the point where you want screening to happen.
The step will produce an outcome (Not flagged / flagged) that you can branch on in the next step.
Step 4: Assign an approver to the Flagged branch
This is where you can assign a specific person or group of people to approve/deny the Visual Compliance match. The Visual Compliance step does not include an approval process; it only runs the screening.
Click the Approval step in the sidebar to add an approval step to the canvas.
Click on the new step to show details. Give the step a name. This label shows in the workflow builder.
Set a Default Approver.
(Optional) Set a Location Override, allowing you to define different approvers depending on the location of the visit.
Step 5: Complete the Flagged path by adding it to your Policy
Click on the Flagged node on your Visual Compliance step.
Connect this path to your recently added approval step.
Connect the node on your approval step to the rest of your workflow.
Once your step is connected, you can continue to build/modify the remainder of your policy. See main article: Building, Publishing, and Using Your Policy for Advanced Approvals
Approving/Denying a Visual Compliance match
When there's an entry or invite that is flagged in visual compliance, the Advanced Approval Process is used in place of the traditional screening workflow.
Match details can be viewed in the Advanced Approval Process workflow window by clicking the 
chart button.
You can also open match details by clicking on either Approve or Deny.
You can add an optional reason when completing an approval or denial.
The History log will update to note the flag, as well as the approval/denial. This update is saved automatically and cannot be edited.
Visual Compliance in a traditional sign-in flow vs. Visual Compliance in a Policy
It's worth understanding what changes when you move screening inside a policy, instead of using a standard sign-in flow:
Routing is explicit. Instead of only notifying a list of alert recipients, a match sends the visit to a named approval step with defined approvers.
Decisions are sequenced. The visit can't proceed past the approval step until the assigned approver acts, so screening becomes a gate rather than a parallel notification.
The audit trail is richer. Approver comments and any Data Collection fields are saved to the invite record and reflected in the History log.
Screening can run at pre-registration. When you require pre-registration, visitors provide their information before the approval process starts, so the Visual Compliance step can screen against complete visitor data and route matches to an approver ahead of arrival, rather than catching them at the kiosk. Depending on the policy, screening and approval can wait for pre-registration to finish or run at the same time. Learn more about Pre-registration for Advanced Approvals.
The workflow is flexible. Because screening is just one step in the builder, you can place it wherever it fits, combine it with conditions and other steps, and add as many branches as you need. Screen only certain visitor paths, chain Visual Compliance with additional approvals or Data Collection, and rearrange steps at any time.