> ## 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. # Kantata > Read Kantata projects, tasks, time, resource requests, allocations, budgets and margin in Hebno, and log time and update tasks after you confirm. The Kantata integration makes delivery and resourcing data available in your client work. Ask how a project is tracking against budget, who is allocated to it next week, or what margin the engagement is running at, and Hebno answers from Kantata with each project, task and time entry cited. When a request implies a change, such as logging time or requesting a consultant, Hebno shows a confirmation card and writes to Kantata only after you confirm. ## At a glance | | | | - | - | | **Connection** | Organisation connection, made by an owner or admin. Members can link their own Kantata account. | | **Default access** | Read and write. Financial figures are visible to owners and admins until you share them with teams. | | **Attach** | Projects, tasks, a member's timesheet week, resource requests | | **Search** | Hebno searches Kantata when a request mentions a project, client, task, hours, budget, margin, allocations or resource requests | | **Link** | A project links to one or more Kantata projects | | **Write** | Log time, update a task, create a task, draft a resource request, add a project note. Every write needs a person to confirm. | ## Before you start You need: * An owner or admin role in Hebno. * A Kantata OX account administrator who can register an OAuth application. * A dedicated Kantata user for the integration. The organisation connection acts as this user, so its account permissions and project permission levels set the most Hebno can read or write. Register an OAuth application for Hebno on the Kantata developer site under **Your Applications**. Enter the redirect URI shown on the **Kantata** card in Hebno, then copy the client ID and client secret. Kantata does not use scope strings. Access comes from the integration user's permissions in Kantata, and from each member's own permissions for members who link their account. > [!TIP] > > Add the integration user to the projects Hebno should read with the **Financial** or **Project Lead** permission level if you want budgets, rates and margin in answers. A lower level such as **Viewer** returns projects and tasks without financial fields, and Kantata returns a permission error for writes the level does not allow. ## Connect Kantata **1. Allow the integration** Open **Admin → Connectors → Catalogue**, find **Kantata** under **PSA, time and resourcing**, and set it to **Allow**. **2. Connect the organisation** Select **Connect**, enter the OAuth client ID and client secret, and sign in to Kantata as the integration user. Approve the request, then select **Test connection**. Hebno lists the projects and 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, resource requests and notes, or choose **Read only**. The card shows **Connected** with the Kantata account name. Members in the selected teams can use Kantata in chat straight away. ### Link your own account Members can link their own Kantata account so writes are made in their name under their own Kantata permissions. 1. In Hebno, open **Settings → Connections**, find **Kantata** and select **Link your account**. 2. Sign in to Kantata and select **Authorize**. When your account is linked, Hebno reads and writes as you: time entries are logged against your Kantata user, and you see only the projects you participate in or can view as an administrator. ## 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 Kantata. | Data area | Includes | Default | | - | - | - | | **Projects and tasks** | Projects, phases, tasks, milestones, status, dates, project leads, clients, notes | All allowed teams | | **Time** | Time entries, timesheet submissions, billable flag, approval status | All allowed teams | | **Resourcing** | Resource requests, allocations, roles, skills, availability by person | All allowed teams | | **Financials** | Project budgets, budget used, rate cards, bill rates, cost rates, margin, invoices | Owners and admins | | **People** | Names, titles, roles, groups and managers | 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 budgets and margin with delivery leads, open the Kantata 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 Kantata permissions instead of the organisation connection. Data areas still apply, so a member never sees more through Hebno than both Kantata and your Hebno settings allow. ## What Hebno reads | Kantata object | Fields Hebno uses | Typical questions | | - | - | - | | **Project** (workspace) | Title, client, project lead, status colour and message, start and due dates, budget, budget used, rate card, billing mode | "How is the Contoso pricing review tracking against budget?" | | **Task** (story) | Title, type (task, deliverable, milestone, issue), phase, assignees, state, start and due dates, estimated and logged hours | "What is left in phase 2 before the readout?" | | **Time entry** | User, project, task, date, time in minutes, billable flag, notes, approval and invoice status | "How many hours did we log on the Contoso interviews last week?" | | **Resource request** | Project, role, skills, hours or dates requested, status, requester | "Which resource requests for Contoso are still open?" | | **Allocation** | Resource, project, role, period, allocated hours, soft or hard | "Who is allocated to Contoso in the week of 16 November?" | | **Budget and margin** | Fees, cost, budget remaining, percentage used, margin by project | "What margin is the Contoso engagement running at?" | | **Rate card** | Roles, bill rates, cost rates | "What rate are we billing Sarah Chen at on Contoso?" | | **User** | Name, title, role, groups, manager | "Who is the project lead on Contoso?" | Reads are live. Hebno queries Kantata 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 | Kantata object | Fields on the card | | - | - | - | | **Log time** | Time entry | Project, task, date, hours, billable, notes | | **Update a task** | Task | State, assignees, estimated hours, start and due dates | | **Create a task** | Task | Project, phase, title, type, assignees, start and due dates | | **Draft a resource request** | Resource request in **Draft** | Project, role, skills, period, hours, notes | | **Add a project note** | Project post | Project, note text | ![Confirmation card for Kantata with editable fields](https://mintcdn.com/hebno/JIjAXWoGoB3PLSSb/images/card-kantata.png?fit=max\&auto=format\&n=JIjAXWoGoB3PLSSb\&q=85\&s=e079f07b2045e68dac1a69e6d88ff6ef) A Kantata change pending confirmation. Nothing is written until you confirm. A resource request is in **Draft** until a person submits it in Kantata. Hebno never submits or approves timesheets, fulfils resource requests, changes rate cards or budgets, or creates or sends invoices in Kantata. ```mermaid theme={"system"} sequenceDiagram participant You participant Hebno participant Kantata You->>Hebno: Log 3 hours on the Contoso interviews Hebno->>Kantata: Find project and task for Contoso interviews Kantata-->>Hebno: Contoso pricing review, task Stakeholder interviews Hebno-->>You: Confirmation card with project, task, date, hours You->>Hebno: Confirm Hebno->>Kantata: Create time entry as you Kantata-->>Hebno: Time entry 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 notes and the write recorded against you in **Admin → Logs → Integrations**. ## Link a project to a Kantata project Linking marks which Kantata projects belong to a Hebno project, so you can ask "how are we tracking?" without naming them. 1. Open the project and select **Brain**. 2. Under **Linked records**, select **Link record**, then **Kantata**. 3. Search by project title or client, and select the project. Repeat for each Kantata project in the engagement. In chats tagged to the project, Hebno starts with the linked projects for any delivery, budget or resourcing question, and time entry cards default to them. See [Linked records](https://hebno.com/docs/projects/linked-records.md). ## Use Kantata in chat * **Attach**: open the **+** menu, choose **Sources → Kantata**, and pick a project, a task, a resource request or your timesheet week. Or type `/` and choose **Kantata**. * **Ask**: name the client, project or phase in your request. For example: > How is the Contoso pricing review tracking against budget and margin, and what is left before the readout? > Who is allocated to Contoso for the next two weeks, and which resource requests are still open? > Log 2.5 hours on the Contoso pricing review, stakeholder interviews, for yesterday. * **Research runs** show a **Checking Kantata** step, with a chip for each project, task and time entry it read. * **Agents** can read Kantata on a schedule, for example a Monday brief on budget used and open resource requests across active projects. 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 `invalid_client` | Check the client ID and secret, and that the redirect URI on the OAuth application matches the one shown in Hebno exactly. | | A project returns **Permission denied** | The integration user does not participate in the project or has too low a permission level. Add the user to the project in Kantata. | | Budgets, rates or margin are missing from answers | The member's team is not in the **Financials** data area, or the integration user lacks the **Financial** permission level on that project. | | A time entry fails because the timesheet is submitted | Kantata locks entries in a submitted or approved timesheet. Ask the approver to reject the submission, then confirm again. | | Time entries are created under the integration user | Link your own account under **Settings → Connections** so entries are logged as you. | | Requests fail with a rate limit message | Kantata limits requests per account. Wait a minute, or narrow the request to one project. | ## 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) * [Productive](https://hebno.com/docs/integrations/productive.md) * [Float](https://hebno.com/docs/integrations/float.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.