Overview
If your organization uses sign-in flow Rules today, you’re already enforcing visitor entry requirements based on information like questionnaire responses. For example, Rules can automatically deny entry, require approval, or notify a team member when a visitor answers a certain way. They’re a great fit for straightforward entry scenarios.
As your approval process evolves, Advanced Visitor Approvals gives you a more powerful way to manage that logic with Policies. Policies are reusable, versioned approval workflows that can be applied across multiple sign-in flows and locations, while supporting capabilities like multi-step approvals, sequential routing, and conditional approval paths.
To help you get started, you can migrate an existing sign-in flow with Rules into a Policy. Your existing approval logic is carried over. Sign-in flows with existing Rules are eligible for migration.
💡Tip: You don’t have to migrate everything at once. Rules continue to work on any sign-in flows that aren’t associated with a Policy, so you can rebuild and test a Policy on one flow before moving additional flows over.💡
Before you begin
A few things to note before migrating from rules to Policies with Advanced Approvals.
Policies are global. You build a Policy at the org level (Global overview > Visitors > Policies) and then associate it with sign-in flows, including global flows with per-location overrides. Rules, by contrast, are configured per sign-in flow.
Recurring invites and self-registration signup links (for group invites) aren't supported yet on flows linked to a Policy. If you rely on those today, keep them on a Rules-based flow for now.
How to migrate your sign-in flow
Navigate to Global overview > Policies.
Click the Create Policy button, then click Create from sign-in flow in the drop-down.
Next, select a Sign-in flow from the drop-down.
You can only migrate sign-in flows that have existing rules.
After selecting an appropriate sign-in flow, the migration will populate Policy name, Policy settings, and Fields. You can add an optional description. After reviewing the migrated information, click Next.
A draft policy will be created in the canvas. You can make changes once the migration is complete. Click Next.
In the Assign approvers step, migrate your Requires approval rule(s) to an Approval Step in the new policy.
Give your new step a name, and set a Default Approver, who will be responsible for completing that step. Click Next to continue.
Once you've completed the steps, you'll be able to Create & publish your step.
Your policy will be created and opened in the Policy builder. From there, you can review the migrated configuration and make additional changes, such as adding sequential approval steps, conditional routing, or other Advanced Visitor Approvals capabilities.
Your migrated policy will automatically be associated with the sign-in flow it is created from.
