Universal Updates: New Events Tracked in User Management History

What's changing & how will it work?

User Management History will now capture updates to users through HR file integrations so administrators can see all changes to employee users.

As part of this update, User Management History will now include the following events completed via HR feed:

• Employee creation
• Status changes, such as active/inactive
• Updates to employee  
• Role, group, direct privilege, and policy assignments or removals

Administrators with View User and Edit User permissions can open the employee’s User Management History modal to see these events and identify that the change originated from the HR feed or applicable bulk import process.

Why are we making this change?

This enhancement provides greater visibility and traceability for employee changes performed through automated HR processes. Administrators can more easily understand when and how an employee record was created or modified without having to rely on external HR integration records.

It also creates a more complete audit trail by bringing automated HR-driven changes into the same User Management History used to review other user administration activity.

Who is affected?

Tenants that create or maintain employee records, roles, privileges, or group assignments through HR file integrations or applicable bulk imports will see these events in User Management History.  

This change affects administrators who manage users and access in Admin > Access Management > User Management. Users without the required View User or Edit User privileges will not see the History icon.  

Compliance Monitoring: Root Cause Analysis

What's changing?

Compliance Monitoring is introducing a new Root Cause field that allows users to document the underlying reason for an identified issue when closing a review. Root Cause assignments will also be available in Insights, reporting exports, and Review History, providing greater visibility into recurring issues and their causes.

How will it work?

Users will see a new Root Cause dropdown above the Comments field when closing a review as Issue: Referred, Issue: No Remediation, or Issue: Remediation. They can select one Root Cause from their organization's available values or create a new value directly from the dropdown. The field is optional, so users can complete the review without selecting a Root Cause. This functionality is also supported for Collective Reviews. Root Cause information will be available in the following areas:

• Transaction Metrics Dashboard: a new Root Cause tile is available in the Transaction Metrics dashboard to summarize reviews by Root Cause. Root Cause will also appear in individual review details.
• Review Exports: a new Root Cause column will be included in the review_transactions.csv export. The column will remain blank for reviews without an assigned Root Cause.
• Review History: Root Cause assignments, changes, and removals will be recorded in the audit trail, including the previous and new values, the user who made the change, and the date and time.

Existing review closure workflows and other review actions will remain unchanged.

Why are we making this change?

Previously, Compliance Monitoring allowed users to identify and resolve issues but did not provide a structured way to capture why those issues occurred. Introducing Root Cause classifications will help organizations consistently document underlying causes, identify recurring patterns, and analyze trends across reviews. These insights can support more targeted remediation strategies and proactive measures to prevent similar issues in the future.

Who is affected?

This enhancement will benefit Compliance Monitoring users who manage issue-related reviews, analyze review outcomes in Insights, or use exported review data for reporting.

Users with access to Review History will also gain greater visibility into Root Cause assignments and changes. Root Cause values will remain specific to each organization, and existing permissions will continue to apply.