Opensense offers the ability to sync user data from external directories like Microsoft Azure, Google Directory or other sources to ensure consistent, automated signature management. However, there may be times when you need to manually override or preserve changes made directly within Opensense. This is where breaking the sync comes in.
Why Break the Sync?
When your directory is synced with Opensense, any changes made in the Users section will be overwritten during the next scheduled sync—unless you take action. To retain manual edits, you must lock the field and select break the sync. This ensures that specific user fields remain unchanged, even if the source directory contains different data.
How to Break the Sync
To preserve changes made within Opensense:
Navigate to the Users section in the Opensense portal.
Locate the user whose data you want to edit.
Click into their profile and identify the field you wish to modify.
Lock the field by clicking the lock icon next to it.
Once locked, select the two arrows to break the sync to prevent future syncs from updating that specific field.
đŸ”’ Note: Breaking sync is applied on a per-field basis. Other fields will continue syncing unless explicitly broken.
Outlook Add-in Behavior
If your users are using the Outlook Add-in, they can edit certain fields within the Signature Settings tab, depending on whether those fields are locked or unlocked:
Editable (unlocked) fields: Users can input custom values. When they do, the sync is automatically broken for that specific field to preserve their changes.
Locked fields: These are visible in the add-in but cannot be edited by the user. Data in these fields continues to sync from the directory unless the sync is manually broken.
This allows for a flexible workflow where users can take control of specific aspects of their signature (e.g., preferred pronouns or title variations) without losing the benefits of automated syncing for everything else.
Opensense Support
For further assistance, contact Opensense Support:
Email: help@opensense.com
Knowledge Base: help.opensense.com