In addition to the typical Fuse profile fields, such as Username, Email, First Name, and Last Name, Fuse supports custom customer-defined profile fields. HR integration projects should must always start by defining what HR data is available and what data needs to be pushed to Fuse, in order to populate the user profile fields. Only authorized authorised Fuse staff can create custom user profile fields. Updates to customer user custom profile fields are must be requested via through the Fuse Support ticketing systemportal.
User
Profile Field Considerationsprofile field considerations
Customers are reminded that they are the Data Controller data controllerfor their Fuse instance and , which means they are responsible for their user user’s data within Fuse. Please Customers must get approval from your their organisation’s Data Officer or CTO for the HR data being referenced by in the integration.
Whilst Fuse can support numerous custom customer-defined profile fields, in the interest of simplicity, data protection and API overhead these should be , it is strongly recommended that these are kept to a minimum when Integrating integrating with fuseFuse. Only data that is required for Fuse user management, reporting and analytics should be referenced. To Note:
| Note |
|---|
Special characters such as Æ, Ø, Å, Ü, Ö and Ä are not currently supported in usernames. |
Based on numerous customer HRIS integrations we have listed recommended user profile fields below, based on standard business data and organization hierarchyorganisation hierarchies, the following user profile fields are recommended:
Field | Description |
Username | |
First Name | |
Last Name | |
Employee ID | |
Job Title | |
Is Manager | |
Department | |
Function | |
Region | |
City | |
Start Date | |
Start Date UA | |
Additional Custom Field 1 | |
Additional Custom Field 2 | |
Additional Custom Field 3 | |
Additional Custom Field 4 | |
Additional Custom Field 5 | |
Additional Custom Field 6 | |
Landing Page |