Transfers
Users sometimes change department, location, or manager. This data may come from an SoR or be entered manually in Bravura Security Fabric . Transfers may require authorization and typically require changes to profile and account attributes, as well as management of change requests that a user was associated with before they were transferred. Bravura Security Fabric can be configured to automatically manage these requirements.
Automation
im_corp_automated_transfer
Purpose:
This scenario implements an automated transfer process for existing users based on changes to the location, department or manager attributes detected on a monitored system of record (SoR).
Configuration:
This scenario relies on configuration data located in the following external data store (extdb) tables:
hid_global_configuration: Adds TRANSFER_* settings under the AUTOMATION namespace, to define parameters such as the target ID for the SoR or the pre-defined request to be used for automated transfer requests.
im_policy_authorization: Adds an authorization rule to allow
idtrack(automation) requests to be auto-approved.hid_policy_attrval_*: Adds rules for handling profile attributes such as the EMPLOYEE_TYPE and OU, which may have to be updated as part of the transfer.
Manual requests
im_corp_manual_transfer
Purpose:
This scenario allows members of the HR team or managers to request the transfer of existing users to another location, department or manager.
Configuration:
This scenario relies on configuration data located in the following external data store (extdb) tables:
im_policy_authorization: Adds authorization rules for transfer requests so that they require approval from members of the HR team, or auto-approve these types of requests if the requester is a member of the HR team.
hid_policy_attrval_*: Adds rules for handling profile attributes such as the EMPLOYEE_TYPE and OU, which may have to be updated as part of the transfer.