In addition to the typical user profile fields in Fuse, such as Username, Email, First Name, and Last Name, Fuse supports customer-defined profile fields. HR integration projects must always start by defining what HR data is available and what data needs to be pushed to Fuse to populate the user profile fields. Only authorised Fuse staff can create custom user profile fields. Updates to customer user profile fields must be requested through the Fuse Support portal.
User profile field considerations
Customers are reminded that they are the data controller for their Fuse instance. instance and are responsible for their user data within Fuse. You must get approval from your organisation’s Data Officer or CTO for the HR data being referenced in the integration.
Whilst Fuse can support numerous customer-defined profile fields, in the interest of simplicity, data protection and API overhead, these should be kept to a minimum when integrating with fuse. Only data that is required for Fuse user management, reporting and analytics should be referenced.
| 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 organisation hierarchy:
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 |
It should be stressed that there is little value in replicating complex organizational structures within Fuse as it just adds unnecessary complexity.