After creating a sync policy, you can modify its settings or remove it entirely. This article explains what you can change, how edits affect running syncs, and how to safely delete a policy.
Editing a policy
- Go to Policies in the sidebar
- Click on the policy you want to edit
- Make your changes
- Click Save
What you can edit
| Setting | Can edit? | Impact |
|---|---|---|
| Policy name | Yes | Display only — no impact on sync operations |
| Description | Yes | Display only — no impact on sync operations |
| Sync frequency | Yes | Takes effect on the next sync cycle. Must be within your licence tier. |
| User selection rules | Yes | Re-evaluated on the next sync cycle. New users are added; removed users stop syncing (data retained). |
| Data types | Yes | New data types begin syncing on the next cycle. Removing a data type stops syncing it (data retained). |
Edits don't require disabling
You can edit an enabled policy without disabling it first. Changes take effect on the next sync cycle.
How edits are tracked
Every policy edit generates a "policy updated" audit log event. The event includes a message describing what was changed (e.g. "sync frequency changed", "user rules updated"). This helps with troubleshooting — if sync behaviour changes unexpectedly, you can check the audit log to see if a policy was recently modified.
| Edit type | Audit log event |
|---|---|
| Any field change | "Policy updated" with a message listing the changed fields |
| Enable / Disable | Separate "Policy enabled" or "Policy disabled" event (not "updated") |
Deleting a policy
- Go to Policies in the sidebar
- Click on the policy you want to delete
- Click Delete
- Confirm the deletion when prompted
What happens when you delete a policy
| Area | Impact |
|---|---|
| Sync operations | All sync jobs for this policy are stopped immediately |
| Synced data | Data already synced to Google Workspace is retained. CloudM Continuity does not delete destination data. |
| User accounts | Google Workspace accounts created by Continuity remain active |
| Policy configuration | The policy configuration is permanently removed. This cannot be undone. |
| Audit history | Historical audit log entries for the policy are preserved for reference |
| Affected users | Users who were covered by this policy become unprotected and are no longer synced |
Deletion is permanent
Unlike disabling, deleting a policy removes its configuration entirely. If you're unsure whether you'll need the policy again, disable it instead. You can always delete it later.
Safe deletion checklist
Before deleting a policy, consider the following:
- Disable first. Disable the policy and wait for any in-progress syncs to complete.
- Check user coverage. Ensure users covered by this policy are included in another policy, or confirm that they no longer need to be synced.
- Review audit logs. Check for any recent errors or issues associated with the policy that may need resolution.
- Communicate. If other admins manage the same tenant, let them know before deleting a shared policy.
Frequently asked questions
| Question | Answer |
|---|---|
| Can I undo a deletion? | No. You would need to create a new policy with the same settings. |
| Will deleting a policy delete data in Google? | No. All synced data is retained in Google Workspace. |
| Can I delete an enabled policy? | Yes, but it's recommended to disable first to allow in-progress syncs to complete cleanly. |
| What if I edit the wrong policy? | Changes take effect on the next sync cycle. If you notice an error, edit the policy again immediately to correct it. |