Deprecated connector - For existing implementations only: This specific connector is no longer available for new integrations. If you are currently using this connector, this documentation remains for reference.
For new integrations, please contact your CSP to discuss the recommended alternative connector and its pricing.
Who can use this feature?
|
Personio connector overview
This connector synchronizes your users from Personio to 360Learning. This integration allows you to:
- Choose your connector administrator.
- Map which 360Learning groups your Personio users will be synchronized to.
- Synchronize information from key Personio fields into 360Learning.
- (optional) Select additional Personio fields to synchronize to 360Learning as custom fields.
- (optional) Automatically structure your 360Learning group hierarchy to match your Personio org chart.
Upon activation, the integration will:
- Add synchronized Personio users to 360Learning if they didn’t previously exist.
- Edit existing 360Learning fields with the information from Personio.
💡 The integration will not delete or synchronize users who only exist in 360Learning.
Synchronization schedule
The synchronization starts automatically once a day at 02:00 AM Central European Time (CET/CEST).
Set up the integration
There are a few items you need to complete before you can start setting up the integration in 360Learning.
Step 1: Generate Personio API keys
💡 Personio Article Link: How to Generate and Manage API Credentials for Personnel Data
First, you need to generate your Personio API keys under and enable the following API permissions:
- Employee data: Read only
- Absence data: No access
- Attendance data: No access
- Documents: No access
- Attendance data: No access
- Documents: No access
Step 2: Contact 360Learning
After you have your Personio API keys, email either your 360Learning Client Success Partner or Solution Architect with the following information:
- Integration Name: Personio.
- Personio Domain: Your Personio application URL.
- Personio API Keys: client_id, client_Secret
- 360Learning Group Id: Include only the ids for the groups that you will sync with Personio.
- 360Learning Connector Admin Email: The email of the user who will act as the administrator for your integration. In 360Learning, this user needs to be either a platform administrator or the platform owner.
- (OPTIONAL) Custom Fields: If you want to sync additional fields, include the Personio API field name and how you would like the field name to appear in 360Learning.
- (OPTIONAL) Group Structure: If you want to sync your users into a group hierarchy structure based on Personio fields, include the Personio API field names. Your Support Architect will setup a workshop for you to determine the best hierarchy to reflect your Personio Org Structure.
After that, your Solution Architect will reach out and complete configuration and setup testing with you. Once testing is complete, they will turn the integration on in your live platform.
Step 3: Test the integration
Next, your Solution Architect will send you a URL to test the integration.
The test environment does not automatically synchronize from Personio and 360Learning. When running through your tests, contact your Solution Architect to manually run the synchronization scripts.
Example:
- Production URL:
myacademy.360learning.com - Test URL:
myacademy.360mocc.com:14532
Other things to know about the test environment:
- Any changes made in production will not show up in the test environment.
- Any changes made in the test environment will not show up in production.
- The test environment does not send any emails.
- The test environment is temporary. If you cannot log in to it anymore while still testing your integration, ask your Solution Architect to restart the test environment.
Suggested test scenarios
💡 When running through your tests, remember to contact your Solution Architect to manually run the synchronization scripts.
- All Active Personio users show up as learners in your synced group(s).
- The data from Personio was copied over to the correct 360Learning fields for each user.
- When you modify a user in Personio, the edit shows up correctly in 360Learning after the sync.
- When you create a new user in Personio, they show up in 360Learning after the sync.
- When you terminate a user in Personio, they are deleted in 360Learning after the sync.
Step 4: Activate the integration in production
Once you’ve completed your tests, request that your Solution Architect deploy the integration into your production platform.
When the integration is in production, your platform admins can activate it in the relevant groups:
- If you don’t see hover behavior in the left sidebar, replace the first step with:
- In the left sidebar, click on the relevant group.
- At the top right of the main section, click
Settings.
- In the left sidebar, hover over the group you’re synchronizing data with, then click
Settings.
- In the left menu, click
Integrations.
- In the left panel, select Integrations → Manage integrations.
- Click Personio.
- Verify the API information is correct and click Setup integration.
New users added through the synchronization will get an email notification with an email and password they can use for their initial login. Once they’ve connected, the platform will prompt them to change their password.
More information about the Personio integration
Default synced data
Here are the default fields that the integration syncs from Personio.
💡 The integration only syncs data employees that are marked as active, onboarding, or leave in Personio. It won’t sync data for inactive Personio users.
| Personio API Field Name | Where the field is visible in Personio | 360Learning Field Name |
|---|---|---|
| employee_id | Employee Information → Public Profile | External id |
| first_name | Employee Information → Public Profile | First Name |
| last_name | Employee Information → Public Profile | Last Name |
| Employee Information → Public Profile | ||
| position | Employee Information → Public Profile | Title / Employment |
| supervisor | Employee Information → HR Information | Manager |
By default, users are reconciled (matched and synchronized) primarily via email address. This means the connector uses the user's email to identify and update their profile in 360Learning.
However, you have the option to configure the connector to prioritize the external ID (a unique identifier from your HRIS) for user reconciliation instead. This is recommended if your external IDs are the most reliable and consistent identifiers for your users.
Optional features
Synchronize custom fields
In addition to the default synced fields, the integration can sync any standard or custom Personio field that is reachable through the Personio API. These will show up as custom fields in 360Learning.
To add additional fields to the integration:
- Locate the field’s Personio API: Getting started with the Personio API.
- Choose the 360Learning display name during implementation.
Things to know about how custom fields synchronize:
- Custom fields containing date values (such as hire date or start date) are created as date type fields in 360Learning. All other custom fields are created as string-type fields. Date values from Personio are expected in
yyyy-MM-dd'T'HH:mm:ssZformat. - If you remove the custom field from a user in 360Learning but not in Personio, the integration will add the custom field back to the user in 360Learning in the next sync.
- If you delete a synced custom field from 360Learning but not Personio, the integration will recreate and add the custom field back to users in the next sync.
- If you change the title of a synced custom field in 360Learning, the integration will create and add a new custom field for that field in the next sync. The renamed custom field will still exist in 360Learning, but it will be removed from synced users.
- If you add a non-synced custom field to a synced user in 360Learning, the custom field will stay in place during syncs.
Filter users
You can define filters to limit which users are processed based on values returned in the payload.
Filters are applied only to active users by default. If you need to apply synchronization filters to inactive users as well, contact your CSP to activate this setting.
Synchronize group structure
By default, the integration adds synced users to one group in 360Learning. You can choose to sync them in a group hierarchy structure based on Personio field values.
To set up group hierarchy through synchronization, contact your Solution Architect. They will organize a workshop with you to determine the best hierarchy to reflect your Org Structure.
💡 The integration does not create groups. If the field values of a synced user do not correspond to any existing 360Learning group, the integration will add them to the top-level synced group.
If you choose to activate group structure synchronization, note down the following items:
- The Personio API field names for each hierarchy level. (Example: office and department are Personio API field names.)
- The level in the group hierarchy for each field. (Example: office is level 1 and department is Level 2)
- The possible values for each field. (Example: Paris and New York are possible office values. Support and HR are possible department values.)
What would the example group structure look like in 360Learning?
- Top Level: the synchronized group
- Level 1: office
- Level 2: department