> ## 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. # Deltek WorkBook > Read WorkBook jobs, tasks, time, resource plans and job financials in Hebno, and log time, update tasks and book resources after you confirm. The Deltek WorkBook integration makes delivery data available in your client work. Ask how a job is tracking against budget, who is booked on it next week, or what was logged against a phase, and Hebno answers from WorkBook with each job, task and time entry cited. When a request implies a change, such as logging time or booking a consultant, Hebno shows a confirmation card and writes to WorkBook only after you confirm. ## At a glance | | | | - | - | | **Connection** | Organisation connection, made by an owner or admin. Members can link their own WorkBook account. | | **Default access** | Read and write. Financial figures are visible to owners and admins until you share them with teams. | | **Attach** | Jobs, tasks, a member's timesheet week, resource plans | | **Search** | Hebno searches WorkBook when a request mentions a job, client, phase, budget, hours or bookings | | **Link** | A project links to one or more WorkBook jobs | | **Write** | Log time, update a task, create a task, book a resource, add a job note. Every write needs a person to confirm. | ## Before you start You need: * An owner or admin role in Hebno. * Your WorkBook address, for example `https://yourfirm.workbook.net`, or your own domain for a self-hosted installation. * A WorkBook user for the integration with the **API Only** access role. This user cannot sign in to the WorkBook interface and cannot call administrator endpoints, which separates the integration's access from any person's. * An API key for that user, created by a WorkBook administrator under **Settings → Advanced tools → User access rights → API key setup**. > [!TIP] > > Grant the integration user's access role the requests and verbs Hebno needs under **Settings → Advanced tools → User access rights → Access role requests** in WorkBook. Read access includes jobs, tasks, time, resources, employees, companies and finance. Add create and update for time, tasks and resource bookings if you want members to write back. A request without the verb returns a permission error rather than partial data. ## Connect WorkBook **1. Allow the integration** Open **Admin → Connectors → Catalogue**, find **Deltek WorkBook** under **Projects**, and set it to **Allow**. **2. Connect the organisation** Select **Connect**, enter your WorkBook address and the integration user's API key, then select **Test connection**. Hebno checks that it can connect to WorkBook and lists the areas the integration user can read and write. **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). **4. Set access** Leave **Access** on **Read and write** to let members propose time entries, task changes and bookings, or choose **Read only**. The card shows **Connected** with the WorkBook address. Members in the selected teams can use WorkBook in chat straight away. ### Link your own account Members can link their own WorkBook account so writes are made in their name under their own WorkBook permissions. 1. In WorkBook, open **My settings → Login settings** and create a personal API key. 2. In Hebno, open **Settings → Connections**, find **Deltek WorkBook** and select **Link your account**. 3. Paste the key and select **Link**. When your account is linked, Hebno reads and writes as you: time entries are registered against your employee record, and you see only the jobs your WorkBook role allows. Personal API keys expire after three months in WorkBook. Hebno notifies you a week before your key expires so you can replace it. ## Data areas Data areas control what members of the allowed teams can see through the organisation connection. They apply on top of whatever the integration user can read in WorkBook. | Data area | Includes | Default | | - | - | - | | **Jobs and tasks** | Jobs, job phases and tasks, status, dates, job managers, clients | All allowed teams | | **Time** | Time registrations and timesheet weeks | All allowed teams | | **Resource planning** | Bookings, allocations, capacity and availability by employee | All allowed teams | | **Financials** | Job budgets, budget burn, WIP, invoiced and uninvoiced amounts, cost and revenue | Owners and admins | | **Employees** | Names, departments, roles and cost centres | 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 share job financials with delivery leads, open the WorkBook card in **Admin → Connectors**, select **Financials** and add the teams that should see them. > [!NOTE] > > When a member has linked their own account, Hebno uses that member's WorkBook permissions instead of the organisation connection. Data areas still apply, so a member never sees more through Hebno than both WorkBook and your Hebno settings allow. ## What Hebno reads | WorkBook object | Fields Hebno uses | Typical questions | | - | - | - | | **Job** | Job number, name, client company, job manager, status, start and end dates, job type, department | "What jobs do we have open for Contoso?" | | **Task** | Task name, phase, assigned employees, planned hours, start and end dates, status, milestone | "What is left in phase 2 of job 4120?" | | **Time registration** | Employee, job, task, date, hours, billable flag, description, approval status | "How many hours did we log on the Contoso interviews last week?" | | **Resource booking** | Employee, job, task, period, booked hours, capacity, availability | "Who is free for three days in the week of 16 November?" | | **Job budget** | Budgeted hours and amount by task or phase, actuals, remaining, percentage used | "Are we over budget on job 4120?" | | **WIP and invoicing** | Work in progress, invoiced to date, uninvoiced time and expenses | "How much uninvoiced time is sitting on Contoso jobs?" | | **Company** | Client name, account manager, address, customer number | "Which jobs sit under Contoso Retail Ltd?" | | **Employee** | Name, department, role, cost centre | "Who manages the Contoso jobs?" | Budget burn, WIP and other cross-job figures come from the WorkBook databoard your admin selects under **Financial databoard** on the WorkBook card. Hebno reads the databoard as it is at the time of the request, so figures match what finance sees in WorkBook. Reads are live. Hebno queries WorkBook when a request needs it. Only what a reply used is stored with the conversation as its sources. ## What Hebno writes Every write appears first as a confirmation card. You can change any field before you select **Confirm**. | Action | WorkBook object | Fields on the card | | - | - | - | | **Log time** | Time registration | Job, task, date, hours, billable, description | | **Update a task** | Task | Status, planned hours, start and end dates, assignees | | **Create a task** | Task | Job, phase, name, planned hours, dates, assignees | | **Book a resource** | Resource booking | Employee, job, task, period, hours | | **Add a job note** | Job note | Job, note text | Hebno never approves timesheets, changes budgets, creates or sends invoices, or changes financial postings in WorkBook. ![Confirmation card for logging three hours to a WorkBook task](https://mintcdn.com/hebno/A7yItabWdPf4lOIs/images/confirmation-card.png?fit=max\&auto=format\&n=A7yItabWdPf4lOIs\&q=85\&s=ac66b21d25592ad42341e2d9ba239131) A time entry for WorkBook pending confirmation, with a completed HubSpot note below it. ```mermaid theme={"system"} sequenceDiagram participant You participant Hebno participant WorkBook You->>Hebno: Log 3 hours on the Contoso interviews Hebno->>WorkBook: Find job and task for Contoso interviews WorkBook-->>Hebno: Job 4120, task Stakeholder interviews Hebno-->>You: Confirmation card with job, task, date, hours You->>Hebno: Confirm Hebno->>WorkBook: Create time registration as you WorkBook-->>Hebno: Registration created Hebno-->>You: Done, with a link to the entry ``` If you have linked your own account, the entry is created as you. Otherwise it is created through the organisation connection, with your name in the description and the write recorded against you in **Admin → Logs → Integrations**. ## Link a project to a job Linking marks which WorkBook jobs belong to a project, so you can ask "how are we tracking?" without naming the job. 1. Open the project and select **Brain**. 2. Under **Linked records**, select **Link record**, then **Deltek WorkBook**. 3. Search by job number, job name or client, and select the job. Repeat for each job in the engagement. In chats tagged to the project, Hebno starts with the linked jobs for any delivery or budget question, and time entry cards default to them. See [Linked records](https://hebno.com/docs/projects/linked-records.md). ## Use WorkBook in chat * **Attach**: open the **+** menu, choose **Sources → Deltek WorkBook**, and pick a job, a task, a resource plan or your timesheet week. Or type `/` and choose **Deltek WorkBook**. * **Ask**: name the client, job or phase in your request. For example: > How is the Contoso pricing review tracking against budget, and what is left to deliver before the readout? > Draft a steering committee update for Contoso with hours burned by phase and who is booked for the next two weeks. > Log 2.5 hours on job 4120, stakeholder interviews, for yesterday. * **Research runs** show a **Checking Deltek WorkBook** step, with a chip for each job, task or databoard it read. * **Agents** can read WorkBook on a schedule, for example a Monday brief on budget burn across active jobs. Writes an agent proposes appear in [agent approvals](https://hebno.com/docs/automate/agent-approvals.md) for review. ## Troubleshooting | Symptom | Fix | | - | - | | **Test connection** fails with an authentication error | Check the API key belongs to a user with the **API Only** role and has not expired. Create a new key and reconnect. | | A job or area returns **Permission denied** | The integration user's access role is missing that request or verb. Grant it in WorkBook under **Access role requests**. | | Financial figures are missing from answers | The member's team is not in the **Financials** data area, or no **Financial databoard** is selected on the WorkBook card. | | Time entries are created under the integration user | Link your own account under **Settings → Connections** so entries are registered as you. | | **Your WorkBook key expires soon** notification | Create a new personal API key in WorkBook and paste it under **Settings → Connections → Deltek WorkBook**. | | A job you expect is not found | Search by job number. Closed jobs are included only when you ask for them by name or number. | ## 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) * [Easy Projects](https://hebno.com/docs/integrations/easy-projects.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.