Skip to main content

​
Introduction

Qobra connects seamlessly to 60+ HRIS, including Workday, Lucca, Factorial, ADP, Sage and many more. You can access the whole list here. The integration is used to:
  • synchronize users, management hierarchy, user groups, user attributes
  • auto-provision users
Management hierarchy sync is only available when your HRIS provides each employee’s manager. Some HRIS tools, such as Loket, don’t expose this information. For these tools, the org chart sync option is greyed out in the HRIS configuration, and Qobra doesn’t import the management hierarchy. Hover over the option to see why it is unavailable.

​
Sub-processing and security

To connect to all these HRIS systems, we rely on Kombo, a german subprocessor. Kombo has been carefully audited on feature and security standards. They follow the best security standards, and are ISO27001, SOC 2 type 2, and GDPR compliant. You’ll find more information here.

​
Access

For each HRIS, you will be able to:
  • choose the information scopes you give Qobra access to.
  • connect your HRIS to Qobra via the most secured way available. For most systems, this will be Oauth 2.0, but it can sometimes be via an api key or a service user as shown below.
HRIS integration scope
HRIS integration setup
For the full walkthrough — setting up the connection, running a sync, and what each synchronized field maps to — see the Help Center article: HRIS integration.

​
Sync an existing user attribute from your HRIS

If you created a user attribute manually in Qobra and the same data now lives in your HRIS, you can convert it into an HRIS-synced attribute instead of creating a new one. Plans, views, and reports that use the attribute keep working after the conversion. To convert an attribute:
  1. Open Qobra settings > User attributes.
  2. On the local attribute you want to convert, select Sync from HRIS.
  3. Choose the HRIS field that will feed the attribute. Only HRIS fields that aren’t already imported are available.
  4. Select Sync.
Qobra marks the attribute as synced and immediately starts a users import from your HRIS. For each user, existing manual values are handled as follows: Qobra refuses the conversion when:
  • the attribute is already synced from an integration.
  • the HRIS integration is paused or being deleted.
  • the HRIS integration doesn’t sync user attributes.
  • the HRIS field type is incompatible with the attribute type.
  • the attribute is unique and the HRIS field isn’t unique.
  • the HRIS field key is already used by another user attribute.
The conversion replaces the attribute’s API key with the HRIS field key (for example, job_title). If you read or write this attribute through the Public API, such as with GET /v1/users or PUT /v1/users/bulk, update your integration to use the new key.