Instance Configuration Sync

Instance configuration used to live in one browser profile. Set up an environment tag on your work laptop and your home profile knew nothing about it. Instance Configuration Sync keeps that setup identical everywhere you are signed in to SN Utils, and lets teams publish a shared baseline that members can adopt or override.

Available on Pro. Community and free installs keep full local instance configuration; only the cross-profile synchronization and team delivery require a licence.

What synchronizes

Configuration is grouped into independent sections, each synchronized on its own:

• Name and environment for the instance
• Instance Tag text, colours, size, opacity, position, clock, and command bindings
• Favicon badge label and colours
• Theme override for that instance
• Header Picker field configuration

Editing one section never overwrites another, so changing a tag colour on one machine and a favicon label on another leaves you with both.

What stays on the device

Some things are deliberately local and never leave the browser profile:

• Visit recency, which drives /env ordering and the Quick Ring
• Enterprise licence state for an instance
• Usage counters and remembered form values
• Caches and previews

Browsing a ServiceNow instance produces no sync traffic at all. Synchronization happens when you edit something, when Manage or the popup opens, and periodically in the background.

Personal overrides on top of team configuration

When a team publishes configuration for an instance, you see it read-only, and anything you set yourself takes precedence field by field. Override only the tag colour and you keep receiving the team's later changes to the tag text, position, and everything else.

Three actions are available on a team-backed instance:

• Reset a single field, returning it to the team's current value
• Revert my changes, removing all your overrides for that instance
• Hide for me, which hides the team's configuration for your account across all your profiles

Delete instance stays reserved for instances that are purely personal. You cannot delete configuration a team owns.

If two teams configure the same hostname, both are kept and you pick which one you prefer. That choice follows you across profiles.

Working offline

Edits apply locally straight away and upload when connectivity returns. A pending change survives a browser restart. Nothing is lost if the network or your session drops mid-edit, and a failed upload never rolls back an edit you already saw take effect.

Deleting an instance

Deleting a personal instance removes it from every profile, including one that was offline at the time and comes back later. It removes the configuration only: licence state, usage counters, and remembered form values on the other machines are left alone.

Backups are separate

Backups remain explicit recovery snapshots, not the way profiles stay in step. Restoring a backup locally does not upload it, and restored entries stay local until you deliberately sync them. Team-owned configuration is never restored from a backup; it always comes from the team.

Turning it off

Instance configuration sync follows the global Cloud Sync setting. With Cloud Sync off, everything keeps working locally, nothing uploads or downloads, and your pending changes are kept until you switch it back on.