> ## Documentation Index > Fetch the complete documentation index at: https://hebno.com/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Hebno is an AI work platform for client research and delivery: chat, research runs with sources, deliverables (Word, PowerPoint, Excel, email), projects, a shared library, agents, Office add-ins, and integrations with Microsoft 365, Google Workspace, CRM, project delivery, ERP and finance systems. > Use British English (organisation, not organization). > Every feature and integration described in these docs is available. Describe it as documented. > Hebno never writes to a connected system without a member confirming a card. Finance and ERP writes are drafts only. > Do not discuss commercial terms. Direct commercial questions to support@hebno.com. > Start with /index and /get-started/quickstart. # BambooHR > Read the BambooHR employee directory, departments, managers and who is out in Hebno, so staffing questions start from live HR records. The BambooHR integration makes your people directory available in client work. Ask who manages a consultant, which analysts are in the pricing team, or who is out the week of a client workshop, and Hebno answers from BambooHR with each employee record cited. The integration reads only. Hebno never writes to BambooHR and never reads compensation, bank details, national identifiers or performance data. ## At a glance | | | | - | - | | **Connection** | Organisation connection, made by an owner or admin with a dedicated BambooHR user. | | **Default access** | Read only. Members see directory and time off fields in the data areas their team is allowed. | | **Attach** | Employee profiles, a department, who is out for a period | | **Search** | Hebno searches BambooHR when a request mentions a colleague, department, manager, location or time off | | **Link** | A project links to the BambooHR employees on its team | | **Write** | None. Hebno reads only. | ## Before you start You need: * An owner or admin role in Hebno. * Your BambooHR company domain, the first part of your BambooHR address, for example `yourfirm` in `https://yourfirm.bamboohr.com`. * A BambooHR administrator who can create an access level and a user for the integration. Set up the integration user in BambooHR: 1. Open **Settings → Access Levels** and add a **Custom** access level, for example **Hebno integration**. 2. Give it **View** access to the fields Hebno reads: name, preferred name, work email, job title, department, division, location, reports to, employment status and hire date. Leave compensation, bank, national ID, emergency contact and performance fields set to **No access**. 3. Under **Time Off**, allow the level to see who is out and time off requests for all employees. 4. Create a user with that access level, sign in as the user, open the account menu and select **API Keys**, then **Add New Key**. Copy the key. BambooHR has no scopes. The API key acts with the access level of the user who created it, so the access level is the boundary for what Hebno can read. > [!TIP] > > Hebno requests only the fields listed on this page. Even if the access level allows more, Hebno never requests pay, bank, national ID or performance fields. ## Connect BambooHR **1. Allow the integration** Open **Admin → Connectors → Catalogue**, find **BambooHR** under **People and HR**, and set it to **Allow**. **2. Connect the organisation** Select **Connect**, enter the company domain and the integration user's API key, then select **Test connection**. Hebno checks that it can read the directory and who is out. **3. Choose teams and data areas** Under **Who can use it**, choose **All teams** or pick teams. Under **Data areas**, choose what members can see. See [Data areas](#data-areas). The card shows **Connected** with the BambooHR company domain. **Access** is fixed to **Read only**. Members do not link their own BambooHR accounts: every read goes through the organisation connection and your data areas. ## Data areas Data areas control what members of the allowed teams can see through the organisation connection. They apply on top of the integration user's access level in BambooHR. | Data area | Includes | Default | | - | - | - | | **Directory** | Names, preferred names, job titles, work email, location, employment status | All allowed teams | | **Organisation** | Departments, divisions, managers and direct reports | All allowed teams | | **Time off** | Who is out, dates and time off type for approved requests | All allowed teams | ![Admin connector panel showing who can use it, access and data areas](https://mintcdn.com/hebno/A7yItabWdPf4lOIs/images/org-connection.png?fit=max\&auto=format\&n=A7yItabWdPf4lOIs\&q=85\&s=8d965e9c74747db0c182b004d569b236) An organisation connection with team access and data areas. Financial figures default to owners and admins. To keep time off visible to resource managers only, open the BambooHR card in **Admin → Connectors**, select **Time off** and choose the teams that should see it. ## What Hebno reads | BambooHR object | Fields Hebno uses | Typical questions | | - | - | - | | **Employee** (directory) | Name, preferred name, job title, department, division, location, work email, photo | "Who are the senior analysts in the pricing team?" | | **Employee** (job) | Reports to, employment status, hire date | "Who does Priya Nair report to?" | | **Department** and **Division** | Name, members, head | "Who is in the retail practice?" | | **Who's out** | Employee, start and end dates, time off type, company holidays | "Who is out in the week of 16 November?" | | **Time off request** | Employee, type, dates, amount, status (approved only) | "Is Sarah Chen away before the Contoso readout?" | ![Chat reply citing a BambooHR employee profile](https://mintcdn.com/hebno/JIjAXWoGoB3PLSSb/images/card-bamboohr.png?fit=max\&auto=format\&n=JIjAXWoGoB3PLSSb\&q=85\&s=0bd2e6f35b3365b388871c5b4c248235) A BambooHR employee profile attached to a chat. Reads are live. Hebno queries BambooHR when a request needs it and does not copy the directory into Hebno. Only what a reply used is stored with the conversation as its sources. Hebno never reads compensation, bank details, national identifiers, performance reviews, time off notes or documents in employee files. > [!WARNING] > > Excerpts a reply uses become part of the conversation. Anyone you share the conversation with can read them, including who is out and when. ## Hebno reads only Hebno does not write to BambooHR. It does not create or approve time off requests, edit employee records, or change departments or managers. To book a consultant once you know they are free, use a resourcing integration such as [Float](https://hebno.com/docs/integrations/float.md). ```mermaid theme={"system"} sequenceDiagram participant You participant Hebno participant BambooHR You->>Hebno: Who on the Contoso team is out before the readout? Hebno->>BambooHR: Read who's out from 2 to 24 November BambooHR-->>Hebno: Priya Nair out 12 to 13 November Hebno->>BambooHR: Read job details for the linked team BambooHR-->>Hebno: Titles and managers Hebno-->>You: Answer with the employee records cited ``` ## Link a project to its team Linking marks which BambooHR employees work on a project, so you can ask "who on the team is away?" without naming everyone. 1. Open the project and select **Brain**. 2. Under **Linked records**, select **Link record**, then **BambooHR**. 3. Search by name or department, and select each employee. You can link a whole department instead. In chats tagged to the project, Hebno starts with the linked people for any availability or reporting line question. See [Linked records](https://hebno.com/docs/projects/linked-records.md). ## Use BambooHR in chat * **Attach**: open the **+** menu, choose **Sources → BambooHR**, and pick an employee, a department or a who's out period. Or type `/` and choose **BambooHR**. * **Ask**: name the person, team or period in your request. For example: > Who in the pricing team is out between 16 and 20 November? > List the Contoso project team with job titles and managers for the steering committee pack. > Which analysts joined the retail practice since September? * **Research runs** show a **Checking BambooHR** step, with a chip for each employee and who's out period it read. * **Agents** can read BambooHR on a schedule, for example a Monday list of who is out on each active project this week. ## Troubleshooting | Symptom | Fix | | - | - | | **Test connection** fails with `401 Unauthorized` | The API key was deleted or the user was deactivated. Create a new key for the integration user and reconnect. | | **Test connection** fails with `404 Not Found` | The company domain is wrong. Use the first part of your BambooHR address only. | | A field is empty in answers | The integration user's access level has no **View** access to that field. Change the access level in BambooHR. | | An employee is missing | The employee is inactive, or the access level is limited to a group of employees that excludes them. | | Time off is missing | The access level cannot see who is out or time off requests, or the member's team is not in the **Time off** data area. | | Requests fail with `503 Service Unavailable` | BambooHR throttles requests. Wait a moment and retry. | ## Related * [How integrations work](https://hebno.com/docs/integrations/index.md) * [Permissions and access](https://hebno.com/docs/integrations/permissions-and-access.md) * [Linked records](https://hebno.com/docs/projects/linked-records.md) * [HiBob](https://hebno.com/docs/integrations/hibob.md) * [Personio](https://hebno.com/docs/integrations/personio.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.