--- title: "HiBob integration: Setting up" slug: "hibob-integration-setting-up" updated: 2026-10-22T15:30:03Z published: 2026-10-22T15:30:03Z canonical: "help.cintra.co.uk/hibob-integration-setting-up" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.cintra.co.uk/llms.txt > Use this file to discover all available pages before exploring further. # HiBob integration: Setting up Cintra sets up the HiBob integration with your HiBob admin. Your HiBob admin creates a few things in HiBob and sends the details to Cintra, then Cintra creates the integration. Once it's in place, your payroll user runs the first sync. Before you start, make sure your payrolls, work patterns, headings, pension scheme parts and cost codes have the same names in HiBob and payroll. See [HiBob integration: Overview](/payroll/docs/hibob-integration-overview). ## Setup at a glance | Step | Who does it? | | --- | --- | | Create a service user | HiBob admin | | Create a permission group and assign the service user to it | HiBob admin | | Create the custom fields | HiBob admin | | Create the company sick pay report | HiBob admin | | Send the details to Cintra | HiBob admin | | Create the integration and map your data | Cintra | | Run the first sync and check the results | Payroll user | ## Creating a service user The integration uses a HiBob service user to read your data. 1. In HiBob, go to **System Settings** > **Integration tools** > **Service users**. 2. Click **Create service user**. 3. Enter a display name and, if you want, a description, then click **Create**. 4. Copy the **Service user ID** and token, and keep them somewhere safe. HiBob only shows the token once, so make sure you save it before you move on. For more information, see HiBob's help article [Manage service users](https://help.hibob.com/hc/en-us/articles/27875098648465-Manage-service-users). ## Creating a permission group 1. In HiBob, navigate to **Permission groups within Account**. (System Settings>Account>Permission groups). ![](https://cdn.document360.io/fc2cda72-4645-4b36-96bf-60439ec11f11/Images/Documentation/image-OJCJ8SR5.png) 1. Create a server user permission group just for the integration, and give it the permissions listed in the tables below. ![](https://cdn.document360.io/fc2cda72-4645-4b36-96bf-60439ec11f11/Images/Documentation/image-OYVO8N1Q.png) 1. Assign the service user to the permission group. 2. Make sure the service user can read the **Cintra payroll name** custom field in the **Payroll** section. 3. In **Access data for**, remove the **Lifecycle status = Employed** condition, otherwise, leavers won't sync. ![](https://cdn.document360.io/fc2cda72-4645-4b36-96bf-60439ec11f11/Images/Documentation/image-6BB3JP9O.png) ### Features tab permissions | Data category | Permission required | | --- | --- | | Advanced analytics > Lifecycle | View the aggregate of everyone's Lifecycle data | | People > ATS Pending Hires | View Pending Hires for ATS integrations | | People > Club View | View the company's clubs view | | People > Directory | View the company's people directory | | Settings > Working Patterns | Manage working patterns | | Time off > Settings | See company's time off settings | | Features > Reports | View reports according to people's data access rights | ### People's data tab permissions | Data category | Permission required | | --- | --- | | People > About | View selected employees' About section histories View selected employees' About sections | | People > Address | View selected employees' Address section histories View selected employees' Address sections | | People > Basic info | View selected employees' Basic info section histories View selected employees' Basic info sections | | People > Employment | View selected employees' Employment section histories View selected employees' Employment sections | | People > Financial | View selected employees' Financial section histories View selected employees' Financial sections | | People > Home | View selected employees' Home section histories View selected employees' Home sections | | People > Identification | Edit selected employees' Identification sections View selected employees' Identification section histories View selected employees' Identification sections | | People > Lifecycle | View selected employees' Lifecycle section histories View selected employees' Lifecycle sections | | People > Payroll | View selected employees' Payroll section histories View selected employees' Payroll sections | | People > Personal | Edit selected employees' Personal sections View selected employees' Personal section histories View selected employees' Personal sections | | People > Personal contact details | View selected employees' Personal contact details section histories View selected employees' Personal contact details sections | | People > UK tax settings | View selected employees' UK tax settings section histories View selected employees' UK tax settings sections | | People > User data | View selected employees' User data section histories View selected employees' User data sections | | People > Work | View selected employees' Work section histories View selected employees' Work sections | | People > Work contact details | View selected employees' Work contact details section histories View selected employees' Work contact details sections | | People > Pensions | View selected employees' Pensions section histories View selected employees' Pensions sections | | Time off > Balance | Adjust selected people's time off balances and bank their overtime Bank overtime on behalf of their employees See selected people's time off and sick leave balances | | Time off > Requests | View all fields, approve or decline requests that are pending approval of others | | Time off > See who's out today | See who's out based on their personal working pattern and time off calendar See who's out today See who's out because of a private policy or policies with a custom name | ## Creating the custom fields HiBob doesn't hold some payroll data as standard, so you need to create custom fields for it. These include the Cintra payroll name, sort code and pension details, plus some optional fields depending on how you pay your employees. See [HiBob integration: Required fields in HiBob](/payroll/docs/hibob-integration-required-fields-in-hibob). ## Creating the company sick pay report The integration uses a HiBob report to find out which sick pay policy each employee is on. 1. In HiBob, go to **Analytics** > **Reports** > **Time Off** > **Policy Assignments Summary**. 2. Duplicate the report, so you have a copy just for the integration. If the report isn't there, create a custom report using the time off policy assignment fields. 3. Make sure the report includes at least the employee ID or name, policy type, policy name, assignment effective date and assignment status. 4. Filter the report to show only the sick leave policy type. 5. Set the date range to **Last 365 days**. 6. Make a note of the report ID. You'll find it in the report's URL, for example `31324507`. ![](https://cdn.document360.io/fc2cda72-4645-4b36-96bf-60439ec11f11/Images/Documentation/image-XRWP6P7C.png) Every employee must have a sick leave policy assigned in HiBob. If an employee doesn't have one, none of their absences come into payroll. If your company doesn't have a company sick pay policy, assign a statutory sick pay policy instead. ## Sending the details to Cintra Send Cintra: - The service user ID and token - The company sick pay report ID - A list of the absence types (policy types) you use in HiBob You should send these details either via the support ticket or though Cintra People [messaging](/payroll/docs/messaging). ## What Cintra does Cintra then: - Enters the API credentials and creates the integration - Applies your company sick pay report ID - Maps your absence types and any custom fields, such as roll number, cost parts, units and rate Cintra lets you know when the integration is ready for the first sync. ## Running the first sync Once the integration is ready, your payroll user runs the first sync and checks the results. 1. Go to **Payroll** > **CintraHR log** and click **Sync now**. 2. For each employee, check that these have synced correctly: - Name - Address - National Insurance number - Salary - Work pattern - Bank details 3. Fix any errors in HiBob or payroll, depending on the error, then run the sync again. > [!NOTE] > **Note**: Any changes made in Payroll will NOT be updated in Hibob. Only make payroll changes if it relates to a configuration and NOT an employee record. For example: > > - You can update work pattern name in Payroll. > - You should NOT change an employee's bank account details in Payroll. While you're testing, work through a small group of employees at a time. This makes it easier to trace each error back to a specific change. To see everything the sync has changed in the current period, use the payroll's period changes view. See [Viewing period changes](/payroll/docs/period-changes-dashboard). For help with errors, see [HiBob integration: Using the CintraHR log](/payroll/docs/hibob-integration-using-the-cintrahr-log).