Table of Contents
Set up integration- Multiple connections
- Unimicro
- Set up integration
- Supported features
- Supported fields - Employee fields
- Supported fields - Position fields
General questions
- FAQ: Unimicro and Huma position integration
- How does the integration between Huma and Unimicro work?
- What happens when I update a field in Huma?
- If I update a field in Unimicro, why don’t I see the change in Huma?
- Why isn’t an employment relationship created when I add it in Huma?
- How do I make sure employment relationship updates are reflected in Unimicro?
- Why doesn’t the employee ID update in Unimicro when I change it in Huma?
Multiple connections
If you need to configure multiple integration instances, follow the setup guidance provided here.
Does your Unimicro account have several “Underenheter” and you need separate connections for each? Then you must configure one integration instance per “Underenhet.”
Unimicro
Are you using DNB Regnskap, Sparebank1 Regnskap, Eika Regnskap, or Azets? Great news: Huma now integrates seamlessly with these systems.
In the examples below, we've used "Unimicro" as a reference, but the process is identical for the other systems listed above.
This means that you do not need to log in to Unimicro if you are using DNB Regnskap, Sparebank1 Regnskap, Eika Regnskap, or Azets, simply use your respective system from those listed above.
Set up the integration
-
To configure an integration in Huma, you must have a "System role with full access permissions for Organization".
-
If you are unsure which roles are required on the Unimicro side to complete the integration setup, please contact Unimicro support for guidance.
Get started quickly by following these steps:
- In Huma: Open Unimicro by searching for it in the top search field or under "Integrations" in the main menu.
- Be familiar with the supported features and the supported profile fields
-
Click the "Set up" button
- Add Enviroment and Organization number
-
Accept Huma’s Terms and Conditions and add the Organization number to the organization you want to connect to.
- Click Save
- Locate the org.nr by navigating to Unimicro > Companies > Org.nr
- You will be sent to Unimicro and asked to authorize the connection to your Unimicro account
- Once a connection is successfully established, updates on users in Huma for the supported fields will be sent to Unimicro
Synchronize users between Unimicro and Huma
When synchronizing users manually, Huma will compare the users in Unimicro with users in your Huma organization. Decide what to do with non-matching and missing values, as well as with users that don’t exist in both systems.
⚠️ You need to resynchronize to add new users. They will not be added automatically
Keep profiles automatically updated from Huma to Unimicro in real-time
Changes made in the supported profile fields will be automatically updated in Unimicro.
⚠️ Note that changes made in Unimicro will not be automatically updated in Huma. To do that, you’ll need to manually synchronize once again.
Note
If an error occurs during synchronization, you can see detailed information in the “Error log” on the Unimicro- integration page in Huma.
Supported fields - Employee fields that are synchronized.
Changes made to supported fields in Huma (listed below) are automatically updated in Unimicro in real time. Changes made in Unimicro, however, must be synchronized manually in Huma.
| Huma field | Unimicro field |
|---|---|
| Email address |
Huma requires this field’s value to be unique. |
| Employment ID* (REQUIRED) |
employee.employeeNumber The integration can’t update this field’s value in Unimicro with the value in Huma. Unimicro requires this field’s value to be unique. Huma requires this field’s value to be unique. |
| Given name |
employee.businessRelation.name
|
| Family name |
employee.businessRelation.name
|
| Phone number |
employee.businessRelation.phones[].number Unimicro requires this field’s value to be unique. Huma requires this field’s value to be unique. |
| Date of birth |
birthdate
|
| Identifications |
employee.socialSecurityNumber employee.internationalID employee.internasjonalIDType employee.internasjonalIDCountry
|
| Address |
employee.addresses[].address
|
| Gender |
employee.sex Unimicro currently only supports synchronizing male and female as genders. If the gender is unspecified in Unimicro, it will remain unchanged in Huma. If the gender is custom in Huma, it will be unspecified in Unimicro. |
Supported fields - Position fields that are synchronized.
📄 Learn more about how employee data synchronization works in integrations in general.
⚠️ Note that activating the integration does not transfer historical position data to Unimicro. Only positions that are created or updated in Huma after the integration is activated will be synchronized.
Position data is synchronized only from Huma to Unimicro, not from Unimicro to Huma.
| Huma fields | Unimicro field |
| Contract type |
employee.employments[].employmentType The integration can’t set this field’s value in Unimicro with the value in Huma. Updates and deletions are supported. |
| Employment percentage |
employee.employments[].workPercent The integration can’t set this field’s value in Unimicro with the value in Huma. Updates and deletions are supported. |
| Contract start date |
employee.employments[].startDate The integration can’t set this field’s value in Unimicro with the value in Huma. Updates and deletions are supported. |
| Job title |
employee.employments[].jobName The integration can’t set this field’s value in Unimicro with the value in Huma. Updates and deletions are supported. |
FAQ: Huma to Unimicro position integration
Create positions in Huma
You cannot create a position in Huma and have it synced to Unimicro so that it is created there. You must first create the position in Unimicro, and then create it in Huma. For the sync to work, the positions must match on the following fields:
- Contract type, Employment percentage, Contract start date and Job title.
Does the integration update position data?
Yes. When supported position fields are changed in Huma, the update is automatically sent to Unimicro.
This applies, for example, when a position is created or when fields such as contract dates, percentage of full-time equivalent, or contract type are changed.
In which direction is data synchronized?
Position data is synchronized in one direction only:
Huma → Unimicro
Changes made directly in Unimicro will not be sent back to Huma.
How are positions matched between Huma and Unimicro?
Positions are matched based on the contract start date.
If an existing position in Unimicro has the same start date as the position being updated in Huma, Huma will update that position in Unimicro with the new values.
If the start date differs, the existing position will not be updated.
When is position data sent to Unimicro?
Position data is sent to Unimicro when:
-
A new position is created in Huma
-
An existing position is updated in Huma
-
The change occurs after the integration has been activated
Can historical positions be transferred?
To register historical position data in Unimicro, this must either be done manually or by updating the position in Huma after the integration has been activated.
The integration does not transfer historical position data that existed before the integration was activated.
Why is not all position information from Huma sent to Unimicro?
Not all position fields are synchronized between Huma and Unimicro because the information stored in the two systems is structured differently. Some fields exist only in one of the systems, or they may have different structures or meanings.
In some cases, this is also due to technical limitations in the Unimicro API or in how data is handled in Huma. Because of these differences, it is not always possible to achieve a complete 1-to-1 transfer of all position fields between the systems.
Why isn’t the position removed in Unimicro when I delete it in Huma?
Unfortunately, this function is not supported, so positions must be deleted manually in Unimicro.
General Questions
How does the integration between Huma and Unimicro work?
The integration lets you sync users between Huma and Unimicro. Once connected, updates to users in Huma automatically transfer to Unimicro for supported fields. You can also run a manual sync to compare users and handle any differences.
What happens when I update a field in Huma?
If a supported field is changed in Huma, the update automatically transfers to Unimicro in real-time.
If I update a field in Unimicro, why don’t I see the change in Huma?
Changes made in Unimicro do not automatically update in Huma. To bring updates from Unimicro to Huma, you need to run a manual sync.
Why isn’t an employment relationship created when I add it in Huma?
The integration does not automatically create employment relationships in Unimicro. You need to add them manually in Unimicro.
How do I make sure employment relationship updates are reflected in Unimicro?
-
If the employee already has a default employment relationship in Unimicro, changes in Huma’s supported fields will update automatically.
-
If there’s no employment relationship, you must first create one manually in Unimicro.
-
Then, run a manual sync once to link the data. After that, future updates from Huma will transfer automatically.
Why doesn’t the employee ID update in Unimicro when I change it in Huma?
The employee ID cannot be changed via the integration because it is a unique identifier in Unimicro. If you change it in Huma, you’ll need to update it manually in Unimicro to keep everything correct.