Skip to main content

Provider Synchronization

Have you ever wondered what happens when someone's mobile ID gets deactivated in your provider's system, or when status changes happen outside of Breeze? Provider synchronization handles all of that for you—automatically keeping everything in sync between Breeze and your mobile ID provider (like STid) so you don't have to worry about it.

Think of it as having a helpful assistant that periodically checks both systems and makes sure they match. When enabled, Breeze quietly runs these checks on a schedule you set, updating statuses, catching changes, and making sure nothing falls through the cracks.

Why this matters​

Imagine this scenario: An employee's mobile ID gets revoked in the STid portal, but Breeze still shows it as active. Without synchronization, operators might try to use or issue Credentials based on outdated information. With provider synchronization enabled, Breeze automatically catches that change and updates the status.

Here's what you get when it's enabled:

  • Always accurate statuses — If someone's mobile ID gets activated, deactivated, or changed in your provider system, Breeze knows about it automatically
  • No manual catch-up — You don't have to remember to check or manually sync when things change elsewhere
  • Peace of mind — Both systems stay in sync without you having to think about it
  • Better visibility — You can see exactly when the last sync happened, so you know your data is fresh

How it works behind the scenes​

When you enable provider synchronization for a template, here's what happens:

  1. Breeze checks on schedule — Based on your sync schedule (you can set how often—daily, hourly, whatever makes sense for your needs), Breeze reaches out to your provider
  2. It compares both systems — Breeze looks at what's in your provider system versus what it has in its own database
  3. It updates automatically — Any differences? Breeze syncs them automatically. Status changed? Updated. Something deleted? Noted.
  4. You can see when it last ran — The template list shows you when each template last synchronized successfully, so you always know your data is current

You set it once, and it just works. No need to monitor it constantly or remember to run manual syncs.

When to turn it on​

You'll want to enable provider synchronization if:

  • You need accurate, up-to-date information — When operators or automated workflows rely on mobile ID statuses, you can't afford stale data
  • Things change frequently outside Breeze — If your provider system is updated by other tools, integrations, or processes, synchronization keeps Breeze in the loop
  • You want to set it and forget it — Once configured, it runs automatically without requiring attention

On the other hand, you might skip it if you're just testing templates, or if you prefer to handle synchronization manually when you know changes have occurred. It's totally optional—enable it when it makes sense for your workflow.

Setting it up​

Configuring provider synchronization is straightforward:

  1. Open any template in the editor
  2. Find the Sync Configuration section
  3. Click "Edit" to open the sync settings
  4. Toggle sync on or off
  5. Set your sync schedule if you want to control how often it runs

That's it. Once enabled, Breeze handles the rest.

For step-by-step instructions, see Editing Templates.

Keeping an eye on it​

You don't need to babysit synchronization, but it's nice to know how things are going:

  • Check the template list — The sync status column shows you at a glance which templates have sync enabled
  • See when it last ran — The "Last Synced" column tells you exactly when each template last synchronized (or shows "Never" if it hasn't synced yet)
  • Review sync logs — If something seems off, check the logs to see what happened during sync operations

Most of the time, you won't need to think about it—it just runs quietly in the background keeping everything aligned.