...
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 toReports To | override_manager |
Start Date | hire_datehire |
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:
...
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 | ||
|---|---|---|
| ||
Users are synced at least 24 hours, but will be 'immediately'* synced if...:
Note: Immediate means that the action will be immediately sent to the queue, sometimes at time of peak traffic, there may be minor delaysWebhook 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. |
...