What's New?

• Known As Name Display in Access Evo — Administrators can now configure whether employees' Known As name or First Name is displayed within the Access Evo workspace, with intelligent fallback behaviour

• Security Improvements — Ongoing security vulnerability remediation and dependency updates

• Bug Fixes — Resolved issues to improve system stability and performance

Known As Name Display in Access Evo

Administrators can now control which name is displayed for employees within the Access Evo workspace — either their legal First Name or their Known As name — using a new organisation-level setting in SelectHR.

What's changed?

A new Name to display in Access Evo option has been added to the Access Evo Settings page within SelectHR. Administrators can choose whether employees' legal First Name or their Known As name is displayed across the Access Evo workspace. The change takes effect automatically as part of the nightly sync, with no per-employee configuration required.

The two available options are:

• First Name: The employee's legal first name is sent to Access Evo. This is the default behaviour and matches how the system has always worked.

• Known As Name: The employee's Known As name is sent to Access Evo where one has been entered. If no Known As name is recorded, the system automatically falls back to the employee's First Name — ensuring no employee is left without a display name.

⚠️ Important: Changing this setting will update all employee display names in Access Evo on the next nightly sync. This may affect how staff appear in posts, notifications, and integrated products. Please consider this carefully before making a change.

Benefits

• Flexible identity management — Organisations can choose the name that best reflects how employees are known across their workplace tools

• Inclusive and personalised experience — Employees who use a preferred or known-as name see that reflected consistently in Access Evo

• Intelligent fallback — No configuration is required per employee; the system automatically uses First Name if no Known As name is recorded

• Simple administration — A single organisation-level control with clear in-app guidance explaining the impact before any change is made

• Consistency across systems — Display names stay aligned between SelectHR and Access Evo through the existing nightly sync

What was the challenge?

Previously, Access Evo always displayed an employee's legal First Name regardless of whether a Known As name had been recorded in SelectHR. For organisations where employees commonly go by a preferred name, this created a disconnect between how people are known internally and how they appeared in Access Evo. There was no mechanism for administrators to change this behavior without bespoke development.

How to configure this setting

Follow the steps below to update the name display setting for your organisation.

Step 1: In the SelectHR HR (2.0) menu, navigate to Configuration and expand the Configuration sub-menu. Scroll down and select Access Evo Settings.

Title: SelectHR Configuration menu showing Access Evo Settings - Description: SelectHR Configuration menu showing Access Evo Settings

Fig. 1 — Access Evo Settings in the SelectHR Configuration menu

Step 2: The Access Evo Settings page opens, showing the Integration Settings panel. Locate the Name to display in Access Evo field. Select either First Name or Known As Name using the radio buttons.

Title: Access Evo Settings page showing Name to display option - Description: Access Evo Settings page showing Name to display option

Fig. 2 — The Name to display in Access Evo setting within Access Evo Settings / Configuration Options

Step 3: Click the information icon next to the field to view the inline tooltip. This explains exactly how each option behaves — including the fallback logic — before you commit to a change.

Title: Tooltip explaining First Name and Known As Name options - Description: Tooltip explaining First Name and Known As Name options

Fig. 3 — Inline tooltip describing the behaviour of each name display option

Once you have selected your preferred option, click Save. The setting will take effect from the next nightly sync.

Security Improvements

The following security updates have been applied in this release as part of our ongoing programme of security maintenance and vulnerability management.

ID	Title	Resolution	Action Required
2217042 2217185 2255518	Security & Dependency Updates	Security vulnerability remediation and dependency updates have been applied to the platform as part of our ongoing security maintenance programme. These include updates to core libraries and resolution of identified vulnerabilities to keep the platform secure and up to date.	No action required.

Bug Fixes

This release includes the following bug fixes to improve system stability and performance.

ID	Title	Resolution	Action Required
1862282	Fields and Tables within SelectHR Being Audited Where Not Required	Removed unnecessary audit tracking from several system parameter fields and internal tables within SelectHR. Fields such as LastAbsenceAllHolidayAdditionsUpdate, LastAbsenceAllStatisticsUpdate, LastBradFordFactorUpdate, PensionLastProcessed, and FamilyLeaveLastProcessed are no longer audited. Audit tracking has also been removed from internal tables including the members error log, workflow instance stage users, system alerts, item version, security sessions, and source type fields. These fields and tables record internal system processing timestamps and operational data that do not require change tracking — auditing them created unnecessary database overhead and noise in audit reports without providing meaningful compliance or operational value. ClearPath customers will see reduced audit log volume and improved database performance, with audit reports containing only meaningful data changes.	No action required.
2262492	Handle EventResult.ViewDocument in RunButtonCommand Sidebar Path	Fixed an issue in the sidebar where attempting to view a document via a RunButtonCommand action could result in an unhandled error. The EventResult.ViewDocument case is now correctly handled, ensuring documents open as expected.	No action required.