In addition to the typical profile fields such as Username, Email, First Name, Last Name, Fuse supports customer-defined profile fields. HR integration projects should 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 authorized Fuse staff can create custom user profile fields. Updates to customer user profile fields are requested via the Fuse Support ticketing system.
User Profile Field Considerations
Customers are reminded that they are the Data Controller for their instance and are responsible for their user data within Fuse. Please get approval from your Data Officer or CTO for the HR data being referenced by 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 kept to a minimum when Integrating with fuse. Only data that is required for Fuse user management, reporting and analytics should be referenced.
To Note: Special characters such as Æ, Ø, Å, Ü, Ö and Ä are not currently supported in usernames.
Can we confirm if APIs support UTF-8? I think the do but we need this confirmed
Based on numerous customer HRIS integrations we have listed recommended user profile fields below, based on standard business data and organization 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 |