> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getnovaplan.com/llms.txt
> Use this file to discover all available pages before exploring further.

# HiBob

> Sync your people from HiBob to power headcount actuals and the snapshot.

The HiBob connector syncs your people into Novaplan: roles, departments, sites, start and end
dates, employment status, and comp. This is the source of your headcount actuals and the people
snapshot that every headcount plan builds on.

## Set up the sync

<Steps>
  <Step title="Connect HiBob">
    In Admin -> Integrations, authorize the HiBob connector with your HiBob credentials.
  </Step>

  <Step title="Map people fields">
    Map HiBob's fields onto Novaplan's canonical people fields. Nova can suggest a mapping that
    you review before saving.
  </Step>

  <Step title="Reconcile departments">
    Confirm that HiBob departments map to your canonical departments. Resolution is by ID, so an
    upstream rename does not move people between departments.
  </Step>

  <Step title="Run the first sync">
    Run the sync, then confirm in [Pipelines](/admin/pipelines) that people landed and curated
    cleanly.
  </Step>
</Steps>

## Field mapping

| Canonical field | Typical HiBob source |
| - | - |
| Employee ID | The HiBob person ID (the stable join key) |
| Name | First and last name |
| Job title | Job title |
| Department | Department, reconciled to a canonical department |
| Site | Work site or location |
| Start date | Hire / start date |
| End date | Termination date (when present) |
| Employment status | Active, terminated, on leave |
| Comp | Base salary and comp components |

<Note>
  Department is resolved by ID, never by name. A HiBob department rename keeps each person in the
  right canonical department rather than re-bucketing them.
</Note>

## Common questions

<AccordionGroup>
  <Accordion title="How often does HiBob sync?" icon="arrows-rotate">
    People data is intended to refresh on a regular cadence (typically daily). Check the freshness
    state in [Pipelines](/admin/pipelines) to confirm the last successful sync.
  </Accordion>

  <Accordion title="A new hire is missing from my plan" icon="users">
    Confirm the person exists in HiBob with a start date and an active status, then re-run the
    sync. If the version is locked, the snapshot is frozen and a post-lock addition is handled
    separately.
  </Accordion>
</AccordionGroup>

## Troubleshooting

* **Sync fails to authorize:** the HiBob credential has likely expired or rotated. Re-authorize
  in Admin -> Integrations.
* **Stale people data:** a quiet daily feed is flagged in [Pipelines](/admin/pipelines); re-run
  rather than assuming the data is current.
* **People landing in the wrong department:** the department is mapping by name, not ID. Fix the
  department mapping in [Dimensions](/admin/dimensions).
* **Comp is masked:** salary and comp are sensitive fields. See [Permissions](/admin/permissions).