Rehire users
Bravura Identity has components that set default rules and thresholds for comparing identity attributes in requests to onboard new users with attributes of existing users, in order to compute a likelihood that the proposed new hire is, in fact, a returning user with an existing profile. Threshold values set by this component determine whether a given score merits a warning to the requester or should block an onboarding request, due to the high certainty that it is a returnee.
Use case
Organizations need to differentiate between new employees and employees that are being rehired. Employees that are being rehired should go through a different process that could enable their previous resources or, in certain circumstances some employees maybe flagged to not rehire.
Solution
Bravura Identity is configured to retain identity information for all users, even after deactivation. This means that user profiles are not deleted, but instead, deactivated. Identity attributes normally include name, date of birth and identifiers such as a driver’s license number or social security number. Moreover, when a user is deactivated, three termination-related attributes are populated: termination date, reason for deactivation and whether rehiring this user is allowed.
When processing onboarding requests, regardless of whether they originate in a system of record (such as HR) or a request form, Bravura Identity applies rules to score how closely the new identity matches any identities already known to the system. These rules work by matching different sets of attributes – for example, first name plus last name plus date of birth. How closely the new user matches an existing profile is used to compute a confidence score. If the confidence score is above one threshold, a warning is generated that the new hire may not actually be new. If the confidence score is above another, higher threshold, then the request is blocked, because there is sufficient certainty that the new user is, in fact, a returning old user.
When an onboarding request using a request form, closely matches an existing profile , the following actions can occur:
Users of Bravura Identity are either instructed to terminate the process, as the old user was flagged as do-not-rehire
Users are instructed to reactivate the old user profile.
When an onboarding request closely matches an existing profile from a Source of Records, the following actions can occur:
The request is blocked with rehire not permitted.
The request is permitted and a subsequent request is submitted for someone to review the potential conflict.
In no case should a new user profile be created for a returning old user.