About the integration
Which data will be transferred?
Setting up the integration
Additional customization of the integration
Synchronizing custom attributes
Exclude users from the synchronization
Troubleshooting and Frequently Asked Questions
About the integration
Our Personio integration allows you to keep your user base on Leapsome up to date - completely automatically!
Once activated, the integration will automatically:
- create a new Leapsome user account for every new employee that turns 'active' in Personio,
- send a Leapsome invite to that user if the 'auto-invite' option is activated. Alternatively, you can manually invite users by re-sending open invites on your team admin page,
- create 'departments' on Leapsome for every 'department' that you have created in Personio. Members of that department will automatically be assigned to the corresponding team on Leapsome,
- assign direct manager rights on Leapsome based on your supervisor roles in Personio - no need to re-establish your reporting lines,
- update all of the above based on your changes in Personio. Changes may take up to 6 hours to be reflected on Leapsome.
Which data will be transferred?
The integration transfers a variety of employee attributes from Personio to Leapsome. Please make sure to grant access to these attributes when setting up the integration.
Please note that - if the integration is enabled - changes in Personio will override any changes manually made on Leapsome, apart from the team: Teams you manually added in Leapsome will remain active and not be changed by the integration, whereas teams that are synched from Personio would be overwritten if you change a user's team in Personio.
Just a note: If you already created teams manually in Leapsome before switching on the integration, please make sure that the teams you have in Leapsome are spelled exactly like in your HRIS (take into account spaces, commas etc). Otherwise, the integration may add duplicate teams with a slightly different spelling to Leapsome.
The following attributes will be synchronized by default:
| Personio Attribute | Leapsome Attribute | Mapped by default? |
| ID | External ID | yes |
| First Name | Firstname | yes |
| Last Name | Lastname | yes |
| yes | ||
| Status | (used to (de-) activate users) | yes |
| Position | Title | yes |
| Supervisor | Primary Manager | yes |
| Hire date | Start Date | yes |
| Termination Date | End (termination) Date | yes |
| Office | Location | yes |
|
Department |
Department (before July 2024: Team) |
yes |
|
Gender |
Gender |
yes |
You can also sync custom attributes from Personio with Leapsome. Learn more about this in this article. Suitable attributes from Personio, that you may want to include in the synchronization include:
| Personio Attribute | Leapsome Attribute (suggested) | Mapped by default? |
| Level (or similar) | Level | no |
| Team | Team | no |
| Subcompany | Team / Custom Attribute | no |
| Custom Attribute | Custom Attribute, level, or team | no |
Please note, that the information 'Date of Birth' from Personio can currently not be synchronized with the Leapsome-field 'Birthday'. You still have the option to add it as a custom attribute, however, this will not allow you to e.g. segment data by age groups within your Review or Survey Analytics, as for these kinds of calculations Leapsome can only use the data within the field 'Birthday'.
Compensation related properties such as bonus/shares will not be populated. To populate such data (e.g. Bonus, or Shares), please use an Excel bulk user upload.
Salary information can be manually enabled to be synced via the integration settings.
Profile pictures from Personio are also not synchronized, but can be manually updated by the user in their profile.
Setting up the integration
Before you get started
Please make sure that you are an Admin both in Leapsome and Personio, or ask your Personio Admin to help you with this setup.
Generating the necessary credentials in Personio
First, you need to create a Personio Client ID and Personio Client Secret that will allow Leapsome to access your employee data in Personio
- In Personio, go to 'Settings' > 'API credentials'
- Click on the 'Generate new credential' button in the top right corner
- Within the sidebar, enter a name for the credentials (e.g. Leapsome Integration API) in the name field and select the integration from the 'Integration' drop-down menu
- Make sure, that for the Personal data type 'employees', the permission to 'Read' is checked for Leapsome - this should be already pre-selected
- In the 'Readable employee attributes' drop-down menu, make sure that all fields that should be synced by default can be accessed via the API as these are needed to successfully synchronize user data with Leapsome (see table in section 'Which data will be transferred?')
- Finish the credential creation by clicking 'Generate new credential'
Finishing the setup in Leapsome
- After generating your credentials, please navigate to 'Settings' > 'Integrations and imports' > 'HRIS integrations' > 'Personio', click 'Enable the integration', paste your Personio Client ID and Personio Client Secret in the corresponding fields and click 'Update & Synchronize'.
Optional settings
- If you enable the option 'Automatically send Leapsome invites to new employees', each user who is (newly) synced from Personio will automatically receive an invite to join Leapsome. If you disable this option, we will sync the employee data but not send an invite. You can then manually send the invite from the 'Edit employees' tab.
- If you enable the option 'Automatically reactivate Leapsome accounts of employees that are marked as active in the source system', Leapsome will automatically reactive a user once the status in Personio of that user got changed back to 'active‘. This can be helpful for cases, in which colleagues take a sabbatical or parental leave.
And that's it - our platform will now automatically synchronize your user data from Personio.
Additional customization of the integration
Synchronizing custom attributes
Once your initial synchronization has been set up successfully, you have the option to include custom attributes from Personio (e.g. Cost Center, Education, Subcompany, ...) to the synchronization. This article shows you how to set that up.
Exclude users from the synchronization
It is also possible to synchronize only a part of your user base in Personio with Leapsome. This allows you to exclude people from automatically being imported to Leapsome, based on a custom attribute (e.g. certain countries or divisions). Before setting this up, please make sure you have successfully set up the general synchronization, and (if needed) also activated the synchronization of custom attributes and defined a target attribute in Leapsome for each custom attribute you may want to use.
To then exclude specific user groups from the synchronization, follow these steps:
- Go to the Integration Settings in Leapsome and visit the HRIS Tab for Personio
- Open the custom attributes mapping
- Within the list, find the attribute you want to base the exclusion on (e.g. Employment type)
- Enter the value of the attribute that should be used to identify users for exclusion - Please note: This needs to be the exact same value as it can be found in Personio
- Confirm your entry by pressing enter
- Repeat this procedure for as many attributes as you need
Please note, that setting up an exclusion attribute will only cut off the connection between Leapsome and Personio for the affected users. It will not automatically deactivate the accounts of the excluded users. To deactivate these users, you once have to manually deactivate their accounts in Leapsome's 'Employees' section. Due to the exclusion rule you have set up, their profiles will not be re-activated the next time the synchronization runs.
Please note, that any exclusion criteria defined for the attribute 'Status' will be ignored by Leapsome. This is due to the fact, that by default, Leapsome will automatically deactivate users, who have any status other than 'Active' in Personio. Because of that, it is not necessary to define exclusion criteria for statuses like 'On Leave' or 'Inactive'.
Troubleshooting and Frequently Asked Questions
I receive an error message when trying to set up the integration
Within the 'Sync custom attributes' menu in Leapsome, I am missing an attribute.
My defined Custom Attribute from Personio is not showing within my users' profiles.
The integration did not create a user profile for someone.
Can I synchronize the team's profile pictures from Personio with Leapsome?
Can I delete user profiles through the Personio integration?
A user has been deactivated in Personio, but still shows as active in Leapsome.
How frequently is user data updated?
Can I prevent certain (default) attributes from syncing with Leapsome?
After switching on the integration, 'Levels' have been duplicated. Why?
How can I give access to a user on (parental) leave who is deactivated in Personio?
My users' Level information is outdated, although I updated it in Personio.
I receive an error message when trying to set up the integration.
Please make sure that within the API credentials in Personio, within the section 'Readable employee attributes', you checked the fields 'Email' and 'Status'. If those attributes are not marked as readable for Leapsome, the integration will not work.
Afterwards, please make sure to copy the API credentials over to Leapsome correctly. Any characters that may have been added by accident will invalidate your credentials. Once you have checked both, retry the synchronization by clicking 'Update & Synchronize' in Leapsome.
Within the 'Sync custom attributes' menu in Leapsome, I am missing an attribute.
If after clicking on 'Sync custom attributes', your desired attribute is not showing up on the left-hand side, it is likely that Leapsome is not allowed to read that information from Personio. To check this in Personio, please navigate to 'Settings' > 'Integrations' > 'API credentials', and click on the API credentials used for Leapsome. Within the sidebar, check whether your desired attribute is checked as 'readable' within the section 'readable employee attributes'. Adjust this if needed, save your settings and re-try the synchronization in Leapsome by clicking 'Update & Synchronize'. The attribute from Personio should appear on the left-hand side of the 'Sync custom attributes' popup window.
My defined Custom Attribute from Personio is not showing within my users' profiles.
When adding a Custom Attribute from Personio, please make sure to define a target value in Leapsome for it, so that Lepsome knows where to display the data coming from Personio. To set this up, navigate to 'Settings' > 'Integrations' > 'Sync custom attributes'. On the right-hand side, you can select the fields 'Team', 'Level', or any Custom Attribute that you have set up as a target attribute. If you decide on a Custom Attribute, please make sure to create it first in Leapsome via 'Settings' > 'Employees' > 'Attributes and profile sections'. Alternatively, via 'Company' > 'Employees' > 'Actions' > 'Manage Custom Attributes', so that you can choose it from the drop-down menu within the integration settings. Then select the desired target attribute and save your changes. From the next synchronization on, Leapsome will add the selected information to your users' profiles.
The integration did not create a user profile for someone.
Please make sure that the user's status in Personio is set to 'Active'. If they have any other status, Leapsome will not create an account for them. If they are active, please double-check if you have defined any user exclusion criteria under 'Settings' > 'Integrations' > 'Sync custom attributes'. Lastly, Leapsome will not create a new profile for a user, if the email address they use in Personio is already taken by another Leapsome user. Go to 'Company' > 'Employees' > 'Actions' > 'Export', to quickly see if the email address is already taken by any other user profile.
How can I make sure that people who are on leave, or have left the company permanently don't have access to Leapsome?
By default, Leapsome will only activate user accounts for people who have the status 'Active' in Personio. If a user has any other status, their Leapsome account will be deactivated automatically.
We have external contractors within our Personio account. How can we make sure that they don't get access to Leapsome?
You can exclude groups of people, such as contractors, from the synchronization. Just follow the steps within this article's section 'Exclude users from the synchronization'.
Please note that once you have set this up, only the connection to Personio is cut off for these users. If you want to deactivate or delete their existing Leapsome accounts, you have to do this manually once within your 'Employees' settings in Leapome. For all new contractors, that will be added to Personio, no Leapsome account will be created once this exclusion rule is in place.
Can I synchronize the team's profile pictures from Personio with Leapsome?
No, this is not possible. Each user has to update their own profile picture within the 'Personal Settings' in Leapsome.
Can I delete user profiles through the Personio integration?
No. Leapsome will not delete any user profiles automatically. Instead, the integration will deactivate all profiles for users who are not 'Active' in Personio. If you want to delete any profiles, you have to do this manually within the 'Employees' section in Leapsome.
A user has been deactivated in Personio, but still shows as active in Leapsome.
In such case, you most likely have excluded a group of people from the integration, that this user is a part of. Because of that, this user is no longer updated through the integration with Personio. You can double-check your exclusion criteria via 'Settings' > 'Integrations and imports' > 'HRIS integrations' > 'Personio' > 'Sync custom attributes'. To deactivate the user, just navigate to 'Company' > 'Employees' and deactivate the user manually.
How frequently is user data updated?
The integration will update your user data automatically every 6 hours. In addition, you can trigger an additional synchronization by navigating to 'Settings' > 'Integrations and imports' > 'HRIS integrations' > 'Personio' and clicking 'Update & Synchronize'.
Can I prevent certain (default) attributes from syncing with Leapsome?
You can disallow the Leapsome API to read attributes, even if they are default attributes. This is done through 'Settings' > 'Integrations' > 'API credentials' in Personio. If you have existing API credentials that are linked to 'Integration > Leapsome', you will need to create new API credentials, where you would leave this field blank on purpose. Please keep in mind that 'Status' and 'Email' need to be readable, in order for the integration to work.
After switching on the integration, 'Levels' have been duplicated. Why?
The Personio integration does not recognize already existing Levels that have been created manually in your account, even if they are spelled exactly like in Personio. While this does not affect user profiles (There, you will always see the current value received from Personio), you may need to adjust your Competency Framework to make sure your level-specific skill descriptions match
How can I give access to a user on (parental) leave who is deactivated in Personio?
When a user is on parental leave or similar and hence deactivated in Personio, the integration also deactivates them in Leapsome. If you want an employee who is deactivated in Personio because they are on parental leave, sick leave, or similar to have access to Leapsome and their reviews during their absence, you can temporarily exclude this user from the integration so they can be activated in Leapsome.
- Set up an exclusion rule for a specific user to remain active despite being deactivated in Personio: Exclude users from the synchronization.
Alternative: If you have a specific attribute in Personio that labels users who are on parental leave and should remain active in Leapsome, you can also exclude the user based on that attribute - if this is not a standard Leapsome attribute, make sure to synch the custom attribute into Leapsome first. - If the user has a termination date added in their profile in Leapsome, remove the date in 'Employees' > Edit user > 'Info' > 'Employment info' > 'Termination date'
- Re-Activate user in Leapsome
- Remove the exclusion rule once access is no longer needed or the user is back from leave. The status will then again reflect the status and changes from Personio.
Alternative: If you set up the exclusion rule based on a specific attribute, you don't have to remove the exclusion rule in Leapsome once the user is back from their leave and should be synced again. Instead, update the attribute in Personio so that the user is no longer labeled with the attribute used in the rule.
My users' Level information or information from a custom attribute of type 'List of options' is outdated, although I updated it in Personio.
When defining Levels in Personio, each of them has a so-called database value, and translations. Since Personio only shares the database value of the Level in its API, this is the only Level information Leapsome receives. If you now decide to re-name a level in Personio, you will only update the translations, but not the database value. In this scenario, you would need to set up an entirely new level, in order to provide a new database value. You can learn more about this here. The same applies for all custom attributes of the type 'List of Options' in Personio.