Create Flow Policies
Flow Policies are the business logic layer that connects Flow Events to Flow Definitions. When an event occurs, the policy evaluates whether it matches the configured scope and then triggers the appropriate Flow Definition. This allows different handling based on criteria—for example, running a comprehensive offboarding Flow Definition for full-time employees but a simpler process for contractors. This article demonstrates creating a Flow Policy for employee termination.
Create a Flow Policy
-
Expand Low Code/No Code Workflow and click No Code Flow Event Policies.
-
Click the Add New button.

-
Enter the details for the Flow Policy:
Field Description If This Event Happens Flow Event that triggers this policy (e.g., "Person Leaver" for employee terminations) Run This Flow Flow Definition to execute when the event is detected and scope criteria are met Name Internal name for the policy (e.g., "Terminate Employees") Display Name Name displayed in the EmpowerID UI Description Description of the policy's purpose and when it applies Locale Key (Unique Name) Optional: Locale key for translating the Flow Policy name into other languages. Leave blank if not using multi-language support. Locale Key for Description Optional: Locale key for translating the description. Leave blank if not using multi-language support. -
Click Save.

-
After saving the Flow Policy, define which objects the policy applies to. Without scope configuration, the policy will not match any events. Search for and select the Flow Policy you just created to open its View One page.
-
In the Scope section, click the Add New button.
-
Select the Scope Type that determines how to identify objects for this policy:
Scope Type Use Case By Location Apply policy to people associated with specific organizational locations (e.g., all employees from HR system locations, excluding partners or contractors) By Business Role and Location Apply policy based on both business role assignments and location By Set Apply policy to members of a specific person set By Management Role Apply policy to members of a specific management role -
Select the specific location, role, or set that defines the scope for this policy.
-
Click Save.
The Flow Policy is now active and will execute the associated Flow Definition when the specified Flow Event is detected for objects matching the scope criteria.
Available Flow Events
The following Flow Events are default shipping events included with EmpowerID. Custom Flow Events can be created as needed to extend automation capabilities.
| Flow Event | Description |
|---|---|
| Primary Business Role Location Changed Automatically | Primary Business Role Location Changed based on Directory Data and RBAC Mappings, by the Role and Location Compiler/Processor Jobs |
| Secondary Business Role Location Added Automatically | Secondary Business Role Location Added based on Directory Data and RBAC Mappings, by the Role and Location Compiler/Processor Jobs |
| Primary Business Role Location Reverted TO DEFAULT Automatically | Primary Business Role Location Reverted TO DEFAULT due to lack of Directory Data or RBAC Mappings, by the Role and Location Compiler/Processor Jobs |
| Person Leaver | Person Termination or Planned Leaver |
| Person Mover | Person Mover Lifecycle Event |
| Person Joiner | Person Joiner/Onboard Lifecycle Event |
| Possible Account Takeover | Possible Account Takeover - possibly an account has been compromised |
| Mailbox Discovered | New mailbox detected event |
| Account Inbox Person Provision | Person provisioned from Account Inbox process |
| Person Inbox Joiner | Person Inbox Joiner |
| Person Rehire | Rehire Person |
| Person Reactivation | Cancellation of planned leaver event or Person reactivation after disablement |
| Person Preleaver Notification | Notification about upcoming leaver event |
| Secondary Business Role Location Removed Automatically | Secondary Business Role Location Removed based on Directory Data and RBAC Mappings, by the Role and Location Compiler/Processor Jobs |
Next Steps
With Flow Policies created and scoped, your No Code Flows are complete and will execute automatically when matching events are triggered. Monitor execution through the Flow Event Inbox and Flow Inbox pages.
Related Articles: