Groove One Flow Restriction
One Flow Restriction ensures that people (contacts/leads) in a Groove-enabled system can only be active in one flow at a time—if the safety setting is enabled for their organization. This applies across all methods of person import: manual, CSV, auto-import, extension, API, and UI. Contacts already in a flow cannot be added to another unless first removed. The UI disables selection and backend validations enforce the rule regardless of import mechanism.
Use Cases
- Prevent prospects from being enrolled in multiple flows, e.g., Sales Development cadence and Account Executive sequence.
- Avoid customers being contacted by different teams for separate campaigns at once.
- Enhance deliverability and reputation by limiting frequency and overlap.
- Ensures deduplication across automated imports, manual adds, and CSV loads.
- For enterprise scenarios where high-priority flows take precedence.
Admin Setup
A Groove Admin can enable this feature with these steps.
- Enable the safety setting via Manage My Org > Flow Settings > Safety Setting
- Under the Safety Settings section, click the expander (>) to enable settings and add exceptions:

3. If needed, select the available users to exclude from this setting

How it works for users
If you enable this feature as an admin, here's how it'll work for your org's users.
- A user tries to add a person to a flow via any supported method.
- System checks if One Flow Restriction is enabled and if the person is already active in another flow.
If not active elsewhere, then the user can add as normal.
If active elsewhere:
- UI disables add controls, showing a tooltip explanation.
- Backend blocks bypass attempts (API, CSV, extension) and raises an error.
- To move a person, remove them from their current flow before adding to a new one.
- If flow prioritization is enabled, importing a person into a high-priority flow automatically removes them from all other active flows.
- Admin-granted overrides allow exceptions if configured.