Enhancements
B2C work email validation to check for duplicates
We’ve improved how work emails are validated for records that share contact details with a user profile (e.g., checklist-created records). When updating a work email on a candidate, employee, volunteer, or contractor record, the system now ensures the email is unique, valid, and not blank.
Updates succeed when the email is well-formed and not used by another active user. If the email already exists, is invalid, or left blank, the update is blocked with a clear error message. Leading and trailing spaces are automatically removed.
These checks only occur when the work email field is changed. This update prevents duplicate emails and avoids Azure B2C sync issues.
Changes made to Inactive users should not trigger any data sync to Azure B2C
Updates now prevent inactive users (those with a NotCurrent status such as Terminated, Completed, Suspended) from being created or updated in Azure B2C. If an inactive user does not already exist in Azure B2C, profile changes will no longer trigger any sync or creation requests. This ensures inactive or non-current users are not added unnecessarily to the authentication system and no sync actions occur for these records.
Include additional user details from B2C in the report
We’ve improved the User Details Report to make it easier for system administrators to troubleshoot duplicate accounts and identify users across enableHR and Azure B2C.
You can now search using a single field that accepts either a username or an email address. The report will check both enableHR and Azure B2C records, ensuring a more accurate and complete result.
The report now also includes new Azure B2C fields:
Display Name, Mail, ProxyAddresses, and IdentitySignInName.
These appear in a separate B2C section beneath the existing enableHR results.
We also improved how user status is displayed. The field label is now “User Status”, and we’ve added a new “Record Status” field next to “Linked Record Email.” Record Status reflects the value stored in the database and may be null if no linked record exists.
Searching by email now checks all possible B2C locations where an email might exist (Mail, ProxyAddresses, and Identity identities). Searching by username also works across B2C identities.
If results are found only in enableHR or only in B2C, the report will still show both tables—displaying a clear message when no matching records exist in one system.
Overall, these changes provide clearer visibility of user data across both systems and help administrators diagnose duplication issues more effectively.
foundU’s Custom Position Field to sync with enableHR’s Position Title
We’ve released an enhancement to improve how approved employee position title are synchronised from foundU into enableHR. This update ensures that the correct position title information is displayed in enableHR when the sync runs.
If an approved employee record in foundU includes a Custom Position Title, this value will now sync automatically into the Position Title field in enableHR.
The standard Position field from foundU will no longer update or override the Position Title field in enableHR.
If the Custom Position Title in foundU is empty, enableHR will retain its manually entered Position Title value. No overwrite will occur during sync.
If foundU’s custom title position and position field will have the same value updated, then it will upload blank value in enableHR against the employee record during the sync. Position title field in enableHR can still be manually updated and will retain its value.
foundU’s employee email will now sync by default with enableHR’s email(h)
We’ve released an enhancement to ensure enableHR’s employee email addresses stay accurate, complete, and consistent. This update improves how email(h) and email(w) fields are populated and maintained during the automated iHub sync.
When a new employee is created in enableHR via the foundU → enableHR sync, the email address from foundU will now populate both:
email(h) – Home email
email(w) – Work email
If the email(w) field in enableHR already contains a value, the iHub sync will not overwrite it with the email from foundU.
If email(w) is empty in enableHR, the sync will automatically populate it using the employee’s email from foundU.
If existing record is updated on both systems with different values, the updated value from foundU is populated only in Email(H) field and enableHR Email(W) value is retained.
Field Mapping logic updated between enableHR and foundU
We’ve released enhancements to ensure cleaner, more predictable, and more reliable data syncing between foundU and enableHR.
The new update consists of:
Maintaining similar dataset between the two systems, emergency contact’s Phone field with manually added value in enableHR is updated to null after the sync job runs as foundU does not have this field.
Manually Entered Values Are Protected and Will Not Be Overwritten for the below fields:
Postal Address
Employee ID
Phone Number (Home)