Using Multiple Sync Policies

CloudM Continuity supports running multiple sync policies at the same time. Each policy has its own configuration, sync frequency and user selection, and all of them can be active together. This article explains how policies are prioritised, what happens when a user is matched by more than one policy, and how licensing works across policies.

Running multiple policies

You can create as many policies as you need. Each policy can be independently activated, paused or deactivated, and pausing one policy has no effect on the others. There is no limit on the number of policies — your licence controls the number of users, not the number of policies.

Common reasons to use multiple policies:

• Different sync frequencies for different groups (for example, hourly for executives, daily for everyone else)
• Different destination domains or username suffixes for different parts of the organisation
• Separating departments, regions or subsidiaries into their own policies

Policy priority

The Policies page displays your policies as an ordered list. A policy's position in the list sets its priority — the policy at the top has the highest priority. To change priority, drag and drop policies into the order you want.

• New policies are added at the lowest priority by default
• Priority changes are saved immediately, but take effect on the next sync cycle — syncs already in progress are not interrupted

When a user is in more than one policy

Because each policy selects its own users, the same user can be matched by several policies. When that happens, the highest-priority active policy applies to that user.

Scenario	Which policy applies
User is in Policy A (priority 1, active) and Policy B (priority 2, active)	Policy A
Policy A is paused	Policy B takes over for overlapping users on the next sync cycle
Policy A is reactivated	Policy A reclaims overlapping users on the next sync cycle

Only active policies take part in this resolution — paused and deactivated policies are always skipped.

Users keep their original Google Workspace account

A user's Google Workspace account is created the first time a policy provisions them, using that policy's destination domain and username suffix. That account is permanent for the user:

• If a different policy later becomes the user's applied policy — through reordering, pausing, or changes to user selection — the user continues to sync to the account that was originally created, even if the new policy has a different destination domain or suffix
• The new policy's other settings, such as sync frequency, apply from the next sync cycle
• Changing a policy's settings after users have been provisioned does not re-provision them either — the destination account never changes once created
• No second Google Workspace account is created, and the user's synced history stays in one place

Seeing which policy applies

With several policies active, the Sync Status page shows the applied policy for each user. Opening a user's details shows the applied policy with a link to it, and indicates when the user is also matched by other policies. Filtering by policy on the Sync Status page reflects the applied policy.

Licensing across policies

User limits apply to unique users across all policies. A user who appears in three policies counts once against your licence, and adding a user to a second policy does not increase your licensed user count. If your total unique users exceed the licence limit, syncing continues and an overage warning is shown, consistent with existing licensing behaviour.

Next steps

• Creating a sync policy — Step-by-step guide
• Defining user selection rules — How to target specific users
• Enabling and disabling a sync policy — Policy lifecycle