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

# BambooHR

> Connect BambooHR to Oleria to bring employees, departments, and manager relationships into your identity and access graph as the authoritative worker record.

Connect BambooHR to Oleria to bring your workforce data into your identity security posture. Oleria reads employees, departments, and manager relationships from BambooHR and uses them as the authoritative worker record that IdP and SaaS access is reconciled against, so a leaver who still holds access somewhere else is visible. This page provides step-by-step guidance for connecting BambooHR to Oleria.

## What Oleria discovers

Once connected, Oleria continuously discovers and maps the following from BambooHR:

* **Employees and people** - the full worker population, including terminated employees. Oleria pulls the complete record on every sync, not just active workers, so leavers who still hold downstream access remain visible.
* **Departments** - your BambooHR department catalog, with stable identifiers that survive a department rename.
* **Manager relationships** - the reporting line for each employee, used to build your organization hierarchy.
* **Department assignments** - which department each employee currently belongs to.

<Note>
  BambooHR is a system of record for the worker, not for application access. It exposes no group, role, access-level, MFA, or SSO API, and no audit log. Because of this, Oleria does not model BambooHR logins as accounts and does not discover groups, roles, or activity from BambooHR - those come from your identity provider and SaaS integrations instead. Departments are also flat: BambooHR does not expose a parent-department relationship, so department hierarchy is not discovered.
</Note>

## Prerequisites

* Administrator permission on the Oleria workspace
* A BambooHR user account that can generate an API key
* Your BambooHR company domain (the subdomain in your BambooHR login URL)

<Note>
  A BambooHR API key inherits the access level of the user who generated it, and BambooHR omits fields the key cannot see rather than returning an error. Generate the key from a dedicated BambooHR user with a Custom Access Level granting full-company read, so the connection does not silently under-report data.
</Note>

## Generate an API key in BambooHR

<Steps>
  <Step title="Open API Keys">
    Sign in to BambooHR and open the account menu in the lower left corner. Select **API Keys**.
  </Step>

  <Step title="Generate a new key">
    Select **Generate a new key**. BambooHR shows the key once, so copy it immediately and store it securely.
  </Step>

  <Step title="Note your company domain">
    Copy your BambooHR company domain - the text before `.bamboohr.com` in your login URL. For example, `acme` in `https://acme.bamboohr.com`.
  </Step>
</Steps>

## Connect BambooHR to Oleria

<Steps>
  <Step title="Open the integration">
    Go to your Oleria workspace, select **Integrations** → select **BambooHR**.
  </Step>

  <Step title="Complete the connection form">
    Fill in the connection form:

    | Field          | Notes                                                                     |
    | :------------- | :------------------------------------------------------------------------ |
    | Company Domain | Required. The subdomain from your BambooHR login URL, for example `acme`. |
    | API Key        | Required. Paste the API key generated in the previous section.            |
  </Step>

  <Step title="Save the integration">
    Select **Authenticate** to validate and save the integration.
  </Step>
</Steps>

## Verify the integration

Confirm the BambooHR instance appears in your Oleria workspace connected integrations. After the first sync completes, you can review the discovered employees, departments, and manager relationships in your Oleria workspace.

<Note>
  When you rotate the BambooHR API key, update it in Oleria by editing the integration. An expired or revoked key will cause the sync to fail.
</Note>

## Contact us

For questions about this integration, contact us at [support@oleria.com](mailto:support@oleria.com).