> For the complete documentation index, see [llms.txt](https://help.swarmia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.swarmia.com/settings/integrations/hr-systems/hibob.md). # HiBob Connect Swarmia directly to HiBob with OAuth to sync time off and match employees. Swarmia connects directly to HiBob over OAuth to sync time off and match employees to Swarmia authors. ## Why use the direct integration * **No third-party data processor.** Swarmia reads from HiBob directly, so your HR data doesn't pass through an intermediate vendor. * **Same data, same effect on your metrics.** Approved time off feeds into developer effort metrics, FTE counts, investment balance, capitalization, and the work log. ## Requirements * **An admin in both Swarmia and HiBob.** The connection starts in Swarmia and ends with the consent step in HiBob, so the same person has to be a Swarmia admin and a HiBob administrator. If your HiBob admin isn't a Swarmia admin yet, [invite them as one](/settings/organization/managing-users-and-roles.md) for the setup. Removing them afterwards doesn't affect the connection. * **Work email on every employee.** Swarmia matches HiBob employees to Swarmia authors by their *work email*. Employees without a work email won't sync, and their time off won't show up in Swarmia. ## Connect HiBob 1. Go to **Settings** → [**HR system**](https://app.swarmia.com/settings/hr-system). 2. In the HiBob row, click **Connect**. You'll be redirected to HiBob to authorize the connection. 3. Approve the requested access. Swarmia asks for two read-only scopes: `timeoff:read` to read time off requests, and `timeoff.sensitive:read` to read how each time off policy is classified. 4. After approval, you're redirected back to Swarmia. The status flips to **Connected** and the initial sync starts in the background. The initial backfill usually completes within a few minutes. ## What Swarmia syncs ### Time off * All time off created or changed in HiBob over the last **2 years**, refreshed every **24 hours**. There's no cutoff on future dates, so a request booked for next year syncs as soon as it's created. * Only **approved** time off counts. Canceled and deleted requests are kept so the day stops counting as time off, but they never appear in metrics or the work log. * **Part-day absences count as a full day.** A half day or a few hours off is stored as a whole day. * **Open-ended time off doesn't sync** until an end date is set in HiBob. It syncs on the next daily refresh after you add one. * **Only the work type is stored.** HiBob classifies every time off policy as paid time off, unpaid time off, or working time. That classification is the only policy detail Swarmia stores — vacation, sick leave, parental leave, and anything else are all treated the same. Swarmia reads policy names to match them to requests, but doesn't store them. It never reads balances, accrual rules, approvers, or the reason someone gave for a request. {% hint style="info" %} **Time off under a private policy syncs too.** Swarmia sees absences booked under a policy marked private in HiBob, so those days count as time off rather than working days. They're stored like any other time off — dates and work type, never the policy name or the reason. {% endhint %} ### Employee data * **Work email and name only.** Swarmia uses them to match each HiBob employee to a Swarmia author. Both come from the time off records themselves — Swarmia doesn't have access to your employee directory. Swarmia doesn't read addresses, compensation, job details, or any other employee fields. ## Where the data shows up * **Developer effort metrics** — approved time off reduces a person's available days, so effort scores reflect when people are actually working. * **FTE counts** — feed into [investment balance](/features/focus/balance-engineering-investments.md) and [software capitalization](/features/capitalize-software-development-costs.md) reports. * **Work log** — time off appears when work log is grouped by author. See [Developer effort (FTEs)](/definitions/developer-effort-ftes.md) for how time off factors into the calculation. ## Check the connection status The [HR system settings](https://app.swarmia.com/settings/hr-system) page shows the current status of the integration: * **Connected** — the integration is healthy and syncing. * **Needs reconnecting** — the connection works, but it was made before Swarmia asked for the policy classification scope. Reconnect to grant it. * **Disabled** — the integration has been turned off, or HiBob revoked Swarmia's access. If HiBob rejects a token refresh, Swarmia retries automatically before flagging the connection for reconnection. ## Disconnect or reconnect Disconnecting happens in HiBob. Go to **Marketplace** → **Manage apps** and remove Swarmia. Syncing stops, and the time off Swarmia already has stays as it is. To reconnect, remove Swarmia in HiBob first, then click **Reconnect** in Swarmia. HiBob won't authorize an app that's still installed, so starting from Swarmia while the app is in place ends on a HiBob error page instead of the consent screen. {% hint style="info" %} **Connections made before the policy classification scope need reconnecting.** HiBob can't widen the access of an app that's already installed, so remove Swarmia in HiBob and connect again. The time off Swarmia already has stays as it is. {% endhint %} ## Related * [HR systems overview](/settings/integrations/hr-systems.md) * [Upload time off data via CSV](/settings/integrations/hr-systems/upload-time-off-data-via-csv.md) — alternative when a direct integration isn't an option. * [Time off API](/settings/integrations/swarmia-apis/time-off-api.md) — push time off into Swarmia programmatically. * [Developer effort (FTEs)](/definitions/developer-effort-ftes.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.swarmia.com/settings/integrations/hr-systems/hibob.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.