<img height="1" width="1" src="https://www.facebook.com/tr?id=755385498933168&amp;ev=PageView &amp;noscript=1">
Skip to content
English
  • There are no suggestions because the search field is empty.

HR Integrations

The platform supports integrations with external HR and employee-management systems, allowing employee information to be synchronized directly with the platform. This helps organizations keep employee records accurate and up to date without relying on manual administration.

HR integrations can be used to add, update and remove users as employees join, change roles or details, and leave the organization. The platform maintains a relationship between the employee record in the source HR system and the corresponding user, allowing subsequent changes to be applied to the correct person.

Supported integration methods

The platform supports two approaches to HR integration:

SCIM 2.0

For HR, identity and provisioning platforms that support the industry-standard SCIM 2.0 protocol. This provides standards-based user provisioning and is suitable for platforms such as Workday and other SCIM-compatible systems.

Custom HR Integration

For organizations, HR providers or internal systems that do not use SCIM, the platform provides a custom integration option. This supports the same core employee lifecycle management while also allowing additional platform-specific information to be supplied.

General capabilities

Depending on the integration method and customer configuration, HR integrations can support:

  • Creating new users when employees join.
  • Updating existing users when employee information changes.
  • Removing users when they leave the organisation.
  • Maintaining a consistent external employee identifier between the HR system and the platform.
  • Updating contact and profile information.
  • Supplying the employee’s company information and, where supported, assigning their primary user group.
  • Associating users with a primary office, facility or other based-at location.
  • Assigning an appropriate subscription level.
  • Storing an employee's home country and, where required, home address.
  • Supporting Remote Worker location information for customers with the relevant feature enabled.

Information that can be synchronized

Required and optional fields vary by integration method. The applicable fields and customer-specific configuration will be confirmed as part of the integration setup, but the platform can generally accept information including:

Information Description
 External employee identifier  A unique and stable identifier from the source HR system. 
 Employee ID  The organization's employee or personnel reference. 
 Username and email  Used to identify and contact the user within the platform. 
 First and last name  The employee's name. 
 Mobile number  A valid contact telephone number. 
 Company  The organization associated with the employee. 
 Home country  The employee's home country, supplied using a recognized country code. 
 Policy/reference number  An optional policy or HR reference. 
 Source update date  The date/time the employee record was last updated by the source system. 
 Primary user group  The employee's primary user group, where supported. 
 Facility / based-at location  The employee's primary office, premise or facility, where supported. 
 Subscription level  The subscription level assigned to the employee, where supported. 
 Home address  The employee's home address, where required and supported. 

Core profile information is supported across the integration capability, while primary group, facility, subscription-level and home-address information is currently available through the Custom HR Integration rather than the standard SCIM interface.

General data rules

A few general rules apply when synchronizing HR data:

  • Each employee should have a stable external identifier so that the platform can reliably associate future updates or deletion requests with the same user.
  • Email addresses, telephone numbers and country information must meet normal validation requirements. International-format mobile numbers are recommended.
  • Group, facility and subscription information must refer to valid records available to the customer and current platform set up. Invalid or out-of-scope assignments are rejected rather than applied to another customer or environment.
  • Where a group or subscription level is not supplied, customer defaults may be used depending on the type of operation and integration configuration.
  • Optional values such as facility, home address and policy/reference number can generally be retained, replaced or cleared through HR updates. The precise behavior is defined during technical integration.

Home addresses and Remote Workers

The Custom HR Integration can store a home address against an employee's profile.

Where the customer also has the Remote Workers feature enabled, the platform can use the supplied address to create or update the employee's associated Remote Worker location on the map.

Address processing is designed so that a temporary inability to determine a map location does not prevent the underlying employee record from being updated. The supplied profile address can still be retained while the location enrichment is reported separately.

Security and customer separation

HR integrations use dedicated machine-to-machine credentials rather than an individual's user login.

Integration credentials are associated with a specific customer and platform space, and permissions control which HR operations the connected system can perform. The integration cannot use supplied data to select another customer or space, and related records such as groups and facilities are validated against the integration's permitted customer environment.

Further information

The exact integration approach, required fields and customer-specific configuration will be agreed as part of the onboarding process.

If you require technical integration documentation, including API specifications, SCIM schemas, authentication requirements, field-level behavior or implementation examples, please contact your Onboarding or Account Manager, who can arrange access to the appropriate technical documentation and integration support.