...
Field in PeopleHR | Maps to field in Learn Amp |
|---|---|
People HR ID | idfull_name |
First Name (or Known As) | first_name |
Last Name | last_name |
Job Role | job_title |
Employee Image | avatar |
Location | primary_location |
Department | primary_team |
Reports To | override_manager |
Start Date | hire_date |
Leaving Date | leave_date |
Company | Used if integration is set up to only import users with a specific "company" on People HR |
...
Integration Settings
Learn Amp administrators can choose to apply the following settings:
Setting | Description |
|---|---|
full_name | Company (optional) |
Invite new joiners int | id |
| Only import employees with this specific Company selected in PeopleHR. If left blank, the integration will import all employees, regardless of Company |
Invite new joiners into Learn Amp (single select)
| Choose when to send invitations to new users. |
Primary Team in Learn Amp (single-select)
| Choose how PeopleHR creates Primary Teams in Learn Amp. |
Primary Team in Learn Amp (optional)
| Choose how PeopleHR removes and assigns managers to Primary Teams in Learn Amp. |
Assign Override Managers in Learn Amp (optional)
| Choose how Managers are assigned in Learn Amp. If this setting is not selected, a user’s manager will be set to the manager of their primary team. Primary Team managers can be assigned in Learn Amp. |
Other settings (optional)
| Choose how PeopleHR interacts with Learn Amp. |
...
Syncing Additional Information
...
Team Managers: The PeopleHR integration will sync each individual users' manager into Learn Amp if the data is available to do so ('Reports to' field in PeopleHR). This is what is known as an Override Manager in Learn Amp. The Integration does not have the ability sync Team/Department managers in to Learn Amp.
However, Team managers can be configured within Learn Amp to work in conjunction with Override Managers. Your Implementation Coach can provide further details on this.
...
Learn Amp will generate a unique webhook URL that you can use to create a series of subscriptions based on employee update events in PeopleHR. Learn Amp then connects to PeopleHR using an API token which can be generated by an Administrator of your PeopleHR account.
When an event subscription is triggered, PeopleHR will automatically sync any new or updated user information to Learn Amp.
Integration set-up
| Drawio sketch | ||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Integation flow
Integration flow
Learn Amp fetches a user’s information from PeopleHR by looking up the PeopleHR Id for the user. If no matching user is found in Learn Amp, a new user account is created in Learn Amp.
| Drawio sketch | ||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Permissions/Scopes Required
For our Our integration with PeopleHR to work effectively, we ask you grant permissions to the following webhook subscriptionsrelies on two calls to the PeopleHR API in order to fetch user details:
Get All Employee Detail
Get Employee Detail By Id
...
Other Frequently Asked Questions
| Expand | ||
|---|---|---|
| ||
Learn Amp fetches a user’s information from PeopleHR by looking up the PeopleHR Id for the user. If no matching user is found in Learn Amp, a new user account is created in Learn Amp. If a matching user is found, the user’s profile will be updated in Learn Amp. |
| Expand | ||
|---|---|---|
| ||
A new user account will be created with the new PeopleHR ID. To avoid this, the integration can be configured to look up users by email when no matching PeopleHR ID is found in Learn Amp. When this setting is applied, a user account will be updated in Learn Amp and a duplicate account will not be created. |
| Expand | ||
|---|---|---|
| ||
Providing you have all of the webhooks event subscriptions enabled as per the integration set up instructions, PeopleHR should send the updated information over to Learn Amp. This may not happen instantly so allow some time for the change to become visible in Learn Amp. Should the updated Information still not appear in Learn Amp, press the ‘Import all from PeopleHR’ button on the PeopleHR integration page within your Learn Amp account. |
| Expand | ||
|---|---|---|
| ||
You should always create new users or update existing users information in PeopleHR, not In Learn Amp. Newly created or updated user information in PeopleHR will automatically be synced to PeopleHR. |
| Expand | ||||
|---|---|---|---|---|
| Learn Amp does not automatically sync with PeopleHR on a daily basis. After the initial sync where all users are moved into Learn Amp for the first time, PeopleHR will will sync information when an event subscription webhook is triggered. For example, If a new user is created, or a user’s job title changes
| |||
Users are synced at least 24 hours, but will be 'immediately'* synced if:
Note: Webhook notifications from PeopleHR may take several minutes to be sent. So a change to a user in PeopleHR may not register a webhook for some minutes, therefore there is normally a small delay in user detail changes propagating to Learn Amp. |
| Expand | ||
|---|---|---|
| ||
The Integration does not have the ability sync Team/Department managers in to Learn Amp. However, Team managers can be configured within Learn Amp to work in conjunction with Override Managers. Your Implementation Coach can provide further details on this. |
| Expand | ||
|---|---|---|
| ||
A user's primary team will be pulled in via the department's field of the PeopleHR integration. If you want a user to be part of any other team (i.e. a secondary, or tertiary team), then you will need to add users to these teams in Learn Amp. |