This version improves efficiency and reliability across the platform to help streamline day-to-day administration, boost system responsiveness, and improve visibility for multi-recipient requests.

Universal Update: User Management History

What's changing?

We implemented a User Management History view that shows admins a timeline of changes made to a selected user. Administrators will be able to see what changed, who made the change, and when it happened. This includes user creation, status updates, user settings changes, and access assignment changes such as roles, groups, privileges, and policies.

User Management History will only show updates to user records moving forward. The system will not retroactively log changes made before the User Management History functionality is available. 

How will it work?

Administrators with View User and Edit User permissions will see a new History icon on user records. Clicking this icon will load their User Management History in a pop-up. Events are sorted in chronological order and include the date and time, event title, change details, and the user or system process responsible for the change. If multiple values are changed at the same time, an event will be collapsed by default and can be expanded to view the full list of changes. If no tracked history exists for the selected user, the modal will not display any events.

User Management History will include the following events:  

• User creation through login, request submission, HR Feed, Seed Data, or Bulk Import
• Status changes, such as active/inactive or blocked/unblocked
• Preferred language updates
• Automated Approver Collaborator updates
• Collaborator end-date updates
• Role, group, direct privilege, and policy assignments or removals

Administrators can also generate a printable copy of the User Management History for audit review, compliance sharing, or internal recordkeeping. See User Management History for details on the events displayed in User Management History and instructions on printing this information.

Why are we making this change?

This change gives administrators better visibility into user and access-related changes. It supports compliance reviews, audit preparation, and troubleshooting by providing a clear timeline of user lifecycle, settings, and access updates in one place.

It also brings User Management closer to the existing history pattern used elsewhere in the system, making it easier for administrators to review change activity in a familiar format. 

Who is affected?

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. 

Universal Update: Performance Enhancements for Background Processing 

What's changing?

As part of our ongoing Background Processing and Platform Performance initiatives, we have implemented a series of backend performance enhancements focused on improving request creation and submission workflows across the system.

These improvements include:

• Optimization of high-traffic and low-performing backend endpoints.
• Database query tuning and performance improvements.
• Reduced processing times for request creation and submission operations.
• Improved handling of concurrent user activity.
• Increased system stability during periods of high demand.

These enhancements are designed to improve the overall responsiveness of the application and provide a more reliable user experience.

How will it work?

Our engineering team has analyzed key request creation and submission workflows and identified opportunities to reduce processing overhead and improve system efficiency. As a result:

• Request creation processes will execute more efficiently, reducing wait times for users.
• Request submission workflows will benefit from optimized backend processing and database interactions.
• System resources will be utilized more effectively during peak usage periods.
• Users should experience fewer delays, timeouts, and intermittent failures when creating or submitting requests.
• The platform will be better equipped to handle large volumes of simultaneous activity, including campaign-based request creation and other high-volume workflows.

These changes occur behind the scenes and do not require any user action.

Why are we making this change?

As customer usage continues to grow, maintaining a fast and reliable user experience remains a key priority. These performance enhancements were implemented to:

• Improve application responsiveness.
• Reduce request processing latency.
• Increase system reliability and stability.
• Minimize request creation and submission failures.
• Support future scalability and continued platform growth.

By optimizing backend services and database performance, we are providing a smoother and more consistent experience for all users.

Who is affected?

This affects users who create or submit requests, especially during periods of high system activity or bulk processing. 

Approvals & Disclosures: Requests with “Update Pending” Recipients Remain Visible in Action Items

What's changing & how will it work?

Requests with multiple recipients will now remain visible in the appropriate Action Items table when one or more recipients are in “Update Pending” status, and other recipients still require action. For approvers, the request will continue to appear in Action Items when they are assigned to an activity or recipient that is still “Awaiting Approval”.  

As part of this enhancement, we also updated the reminder notification logic. Approvers will now receive reminders only for their assigned activities or recipients that are in the "Awaiting Approval" status. Activities or recipients in the "Update Pending" status will no longer prevent reminder notifications from being sent to the rest of Approvers. Approvers will only receive reminders for activity or recipients that are “Awaiting Approval” and assigned to them, not for those in "Update Pending“ status.

For submitters, the request will appear in Action Items when they have a pending action, such as resubmitting updates or canceling recipients. The request will remain visible to the relevant user until all required approver and submitter actions are completed. 

This updated reminder and action item logic only applies to requests created and actioned after v4.10 is deployed.

Why are we making this change?

Previously, if any recipient on a multi-recipient request was in “Update Pending” status, the request would be excluded from the approver’s Action Items and reminder queue, even when other recipients were still awaiting approval. This made it difficult for approvers to locate and act on requests without relying on email links.

This change improves request visibility and helps ensure that approvers and submitters can consistently find the requests that require their attention. It also aligns reminders with the specific actions that are still pending, reducing confusion and helping users complete approvals and updates more efficiently.

Who is affected?

This change affects approvers and submitters working with multi-recipient requests in Approvals & Disclosures.