4.5.0 Release Notes

Release Date: 2026-07-30

New Features

Continuous Sync via Atlassian Guard

Large organizations can now switch from Daily sync to Continuous Sync in Settings. Group, role, and user changes are detected from your organization's Atlassian Guard audit log approximately every 5 minutes and applied automatically, keeping data close to real time. A full sync still runs weekly to verify the complete data set and guarantee accuracy.

Near-real-time updates - group, role, and user changes apply automatically, without waiting for the next full sync.
Parallel sync operations - the audit-log sync can run while a full sync is in progress, instead of waiting for it to finish.
Users still syncing are skipped - operations skip users whose data is still being updated rather than acting on unsettled data. This matters most for filters that exclude users, such as "not in group X". Explicitly selected users are never skipped.
Skipped users are reported - an operation that skipped users finishes with a partially failed status and lists them, instead of omitting them silently.
Requires Atlassian Guard - enable Atlassian Guard on your organization to use Continuous Sync. Daily sync remains available otherwise.
Validated at scale - bulk group membership and role changes have been tested at up to 5,000 users.

See Sync and Data Freshness for the full sync model.

See Bulk Operations and Automated Tasks for guidance on reviewing operation results.

User Browser: Last Active column reflects a single app filter

When exactly one app is selected in the Included Apps filter, the User Browser's Last Active column header itself shows that app's name - for example "Last Active (Jira)" - so it's clear at a glance which app the dates belong to. Selecting two or more apps, or clearing the filter, reverts to "Last Active (Organization)".

Bug Fixes

Viewing affected users of a User Operation from Rovo