We’ve deployed an important update to improve how Guardz handles user status changes coming from cloud directories like Google Workspace and Microsoft.
TL;DR:
When a user is suspended in your cloud directory, they’ll now be automatically suspended in Guardz as well—without losing issue history. When reactivated, they’ll return to Active status in Guardz, along with their issues.
What’s new:
Suspended users in Google/MS directories are now marked as Suspended in Guardz (instead of Inactive).
Their issues are now archived, not deleted. You can still view them by filtering for archived issues.
When the user is reactivated in the directory, they automatically become Active again in Guardz, and their issues are restored.
Suspended users no longer count toward your subscription seat count.
Why it matters:
Previously, suspending a compromised user in your cloud directory could cause their Guardz profile to become Inactive and their issues to be deleted—making investigation impossible. This update preserves the data and provides a more reliable, audit-friendly lifecycle.
Note:
If you explicitly mark a user as Inactive in Guardz, they will not be synced with cloud directory changes (including reactivation).