...
If your company uses Personio, it’s likely that all of your employees will be listed on there. Our integration with Personio allows an automatic sync between platforms – making the setting up and maintenance of user profiles on Learn Amp a seamless experience.
| Info |
|---|
This integration is in Beta and utilises a third party connector, ‘Kombo’, who act as a sub-processor. Read more on them here |
...
Main Features
Syncing users is seamless and efficient, eliminating any need for manual work.
All of your company’s employees that are in Personio are automatically synced into Learn Amp.
In the future, when new users are added into your company’s Personio system, they’ll automatically be added into Learn Amp too.
Standard fields such as an employee’s name, job title, and team are also pulled into Learn Amp.
If an employee’s details (such as job title or team) change in Personio, these changes will be automatically reflected in Learn Amp too.
You can choose when to invite users from your Personio system into Learn Amp, so there’s no rush or need to do so immediately.
When a user is deactivated in Personio, they are deactivated in Learn Amp
...
Kombo.dev or Kombo Technologies GmbH is an ATS HRIS integration partner of Learn Amp. Kombo has integrations with a large number of HRIS providers and act as a single source of contact that allows Learn Amp to access these integrations through their API. This makes it possible for you as a customer to connect your Learn Amp account to the account you have with your ATS HRIS provider.
Kombo is ISO 27001 and SOC 2 certified and stores and processes all data within the EU. Learn Amp has a data processing agreement with Kombo and by proceeding with a particular ATS HRIS integration, you as an Learn Amp customer acknowledge and agree to Kombo Technologies GmbH as a sub-processor under your data processing agreement with Learn Amp.
Does Kombo process our data?
...
How does Kombo work?
| Anchor | ||||
|---|---|---|---|---|
|
...
How secure is Kombo?anchor
Kombo -security
...
As we are in Beta, we will gather more data points than we currently need as we look to add more functionality associated to those scopes.
...
Type
...
Field in Personio
...
Maps to field in Learn Amp
...
Setup
...
Why?
...
Legal entities
...
id
...
Enabled
...
remote_id
...
Enabled
...
name
...
Enabled
...
changed_at
...
Enabled
...
remote_deleted_at
...
Enabled
...
address
...
Optional
...
Employees
...
id
...
Enabled
...
A unique identifier for the user that can be used as a source of truth
...
remote_id
...
Enabled
...
Used as an identifier to sync user data. It may not be unique but is useful contextually
...
employee_number
...
Enabled
...
A unique number assigned to the user that can be used as a unique identifier
...
first_name
...
first_name
...
Enabled
...
Sets a users first name
...
last_name
...
last_name
...
Enabled
...
Sets a users last name
...
nationality
...
Enabled
...
display_full_name
...
Enabled
...
The users full name that can be fetched as a combination of first name and last name
...
job_title
...
job_title
...
Enabled
...
Fetching the users job title which displays on their profile
...
work_email
...
...
Enabled
...
Users work email (e.g. @companyname) that is used to identify them and can be then used to log in
...
start_date
...
hire_date
...
Enabled
...
When the user starts. This can be used to set when they’re invited.
...
termination_date
...
leave_date
...
Enabled
...
When the users end of employment is. This is used to deactivate a user on Learn Amp
...
remote_created_at
...
Enabled
...
A machine readable string which shows the date-time when a user was created
...
changed_at
...
Enabled
...
The date-time when a significant update was applied to a user
...
remote_deleted_at
...
Enabled
...
The date-time when a users was deleted
...
manager_id
...
Enabled
...
This field is used to identify the manager in order to set this on the user
...
employment_type
...
Optional
...
avatar
...
avatar
...
Optional
...
We’re exploring functionality to allow users avatars to be automatically pulled in from the HR system
...
work_location_id
...
primary_location
...
Optional
...
We’re exploring functionality to allow location to be able to add a location and set it on the user, based on the work location
...
legal_entity_id
...
Optional
...
custom_fields
...
Optional
...
Absence types (Optional)
...
id
...
Enabled
...
remote_id
...
Enabled
...
changed_at
...
Enabled
...
remote_deleted at
...
Enabled
...
name
...
Optional
...
unit
...
Optional
...
half days supported
...
Optional
...
exact_times_supported
...
Optional
...
Absences
...
id
...
Enabled
...
remote_id
...
Enabled
...
employee_id
...
Enabled
...
change_at
...
Enabled
...
remote_deleted_at
...
Enabled
...
approver_id
...
Optional
...
start_date
...
Optional
...
end_date
...
Optional
...
start_half_day
...
Optional
...
end_half_day
...
Optional
...
start_time
...
Optional
...
end_time
...
Optional
...
amount
...
Optional
...
unit
...
Optional
...
status
...
Optional
...
employee_note
...
Optional
...
type_id
...
Optional
...
Groups
...
id
...
Enabled
...
name
...
primary_team
...
Enabled
...
remote_id
...
Enabled
...
changed_at
...
Enabled
...
remote_deleted_at
...
Enabled
...
type
...
Enabled
...
Work locations
...
id
...
Enabled
...
remote_id
...
Enabled
...
name
...
Enabled
...
address
...
Enabled
...
type
...
Enabled
...
changed_at
...
Enabled
...
remote_deleted_at
...
Enabled
...
Create and manage employees
...
Enabled
...
Manage absences
...
This will be limited to ‘expected' functionality e.g. Location mapping into a location field.
...
Other Frequently Asked Questions
...