> ## 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. # Scoro > Read Scoro projects, tasks, time entries, quotes, invoices and budgets in Hebno, and log time, create tasks and draft quotes after you confirm. The Scoro integration makes projects, time and commercial data available in your client work. Ask how a project is tracking against its budget, what was quoted to a client, or which invoices are still unpaid, and Hebno answers from Scoro with each project, task and document cited. When a request implies a change, such as logging time or preparing a quote, Hebno shows a confirmation card and writes to Scoro only after you confirm. ## At a glance | | | | - | - | | **Connection** | Organisation connection, made by an owner or admin. Members can link their own Scoro account. | | **Default access** | Read and write. Financial figures are visible to owners and admins until you share them with teams. | | **Attach** | Projects, tasks, quotes, invoices, a member's time entries for a week | | **Search** | Hebno searches Scoro when a request mentions a client, project, task, hours, budget, quote or invoice | | **Link** | A project links to one or more Scoro projects and their client contact | | **Write** | Log time, create a task, draft a quote. Every write needs a person to confirm. | ## Before you start You need: * An owner or admin role in Hebno. * Your Scoro address, for example `https://yourfirm.scoro.com`. * A Scoro administrator who can create an API key. An administrator creates the key in Scoro under **Settings → Integrations → Scoro API**. Copy the API key and the company account ID shown on the same page. The key acts for the whole account, so Hebno narrows what members see with teams and data areas. Scoro does not use scope strings. For members who link their own account, Scoro applies the member's user role and module permissions to every request. > [!TIP] > > The API key reads with the access of the Scoro account. Choose **Read only** on the Scoro card in Hebno if members should not propose time entries, tasks or quotes. A module the key cannot reach returns a permission error rather than partial data. ## Connect Scoro **1. Allow the integration** Open **Admin → Connectors → Catalogue**, find **Scoro** under **PSA, time and resourcing**, and set it to **Allow**. **2. Connect the organisation** Select **Connect**, enter your Scoro address, the API key and the company account ID, then select **Test connection**. Hebno checks that it can connect to Scoro and lists the modules it 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, tasks and draft quotes, or choose **Read only**. The card shows **Connected** with the Scoro address. Members in the selected teams can use Scoro in chat straight away. ### Link your own account Members can link their own Scoro account so writes are made in their name under their own Scoro permissions. 1. In Hebno, open **Settings → Connections**, find **Scoro** and select **Link your account**. 2. Sign in with your Scoro username and password. Hebno exchanges them for a Scoro user token and does not store your password. When your account is linked, Hebno reads and writes as you: time entries are logged against your Scoro user, and you see only the projects and documents your Scoro role allows. Changing your Scoro password ends the link, and **Link your Scoro account again** appears in Hebno. ## Data areas Data areas control what members of the allowed teams can see through the organisation connection. They apply on top of whatever the API key can read in Scoro. | Data area | Includes | Default | | - | - | - | | **Projects and tasks** | Projects, phases, tasks, status, deadlines, project managers, assignees, comments | All allowed teams | | **Time** | Time entries, billable flag, completed flag, activity type | All allowed teams | | **Contacts** | Companies and people, account managers, contact details | All allowed teams | | **Financials** | Project budgets, budgeted and actual revenue and cost, quotes, invoices, payments, profit | Owners and admins | ![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 quotes with delivery leads, open the Scoro 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 Scoro permissions instead of the organisation connection. Data areas still apply, so a member never sees more through Hebno than both Scoro and your Hebno settings allow. ## What Hebno reads | Scoro object | Fields Hebno uses | Typical questions | | - | - | - | | **Project** | Name, number, client, project manager, status, start date, deadline, phases, budget | "How is the Contoso pricing review tracking against budget?" | | **Task** | Name, project, phase, assignee, status, start and end, estimated duration, activity type | "What tasks are open on Contoso before the readout?" | | **Time entry** | User, task, date, duration, billable duration, description, completed flag | "How many hours did we log on the Contoso interviews last week?" | | **Project budget** | Budgeted and actual revenue, labour cost, other costs, gross margin | "What margin is Contoso running at against plan?" | | **Quote** | Number, client, date, status, lines, sum, discount, valid until | "What did we quote Contoso for phase 2?" | | **Invoice** | Number, client, project, date, due date, sum, paid sum, status | "Which Contoso invoices are still unpaid?" | | **Contact** | Company or person name, account manager, email, phone | "Who is our account manager for Contoso Retail?" | Reads are live. Hebno queries Scoro 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**. Commercial writes are drafts only. | Action | Scoro object | Fields on the card | | - | - | - | | **Log time** | Time entry | Project, task, date, duration, billable, description | | **Create a task** | Task | Project, phase, name, assignee, start and end, estimated duration, activity type | | **Draft a quote** | Quote in your draft status | Client, project, date, valid until, lines, quantities, prices, discount | ![Confirmation card for Scoro with editable fields](https://mintcdn.com/hebno/JIjAXWoGoB3PLSSb/images/card-scoro.png?fit=max\&auto=format\&n=JIjAXWoGoB3PLSSb\&q=85\&s=87f587e80fa1c4dd9a3305dc003f8731) A Scoro change pending confirmation. Nothing is written until you confirm. A draft quote is in your draft status in Scoro until a person reviews it there. Hebno never sends or accepts a quote, creates or sends an invoice, records a payment, changes budgets or prices, or edits user permissions in Scoro. ```mermaid theme={"system"} sequenceDiagram participant You participant Hebno participant Scoro You->>Hebno: Draft a quote for Contoso phase 2 Hebno->>Scoro: Read the Contoso contact and phase 1 quote Scoro-->>Hebno: Contact Contoso Retail, quote 2026-118 Hebno-->>You: Confirmation card with client, lines and prices You->>Hebno: Confirm Hebno->>Scoro: Create quote in draft status Scoro-->>Hebno: Quote created Hebno-->>You: Done, with a link to the draft ``` If you have linked your own account, the record is created as you. Otherwise it is created through the organisation connection, with the write recorded against you in **Admin → Logs → Integrations**. ## Link a project to a Scoro project Linking marks which Scoro 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 **Scoro**. 3. Search by project name, number or client, and select the project. Link the client contact too if you want quote and invoice questions to start from it. In chats tagged to the project, Hebno starts with the linked records for any delivery, budget or billing question, and cards default to them. See [Linked records](https://hebno.com/docs/projects/linked-records.md). ## Use Scoro in chat * **Attach**: open the **+** menu, choose **Sources → Scoro**, and pick a project, a task, a quote, an invoice or your time entries. Or type `/` and choose **Scoro**. * **Ask**: name the client, project or document in your request. For example: > How is the Contoso pricing review tracking against its budget, and what margin are we on? > List open Contoso invoices with due dates and draft a short reminder for anything overdue. > Log 3 hours on the Contoso project, stakeholder interviews, for 3 November. * **Research runs** show a **Checking Scoro** step, with a chip for each project, document and time entry it read. * **Agents** can read Scoro on a schedule, for example a Monday brief on budget against actuals 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 an authentication error | Check the API key and company account ID, and that the Scoro address is correct. Create a new key if the old one was revoked. | | A module returns a permission error | The API key or the member's Scoro role has no access to that module. Change it in Scoro. | | Budgets, quotes or invoices are missing from answers | The member's team is not in the **Financials** data area. | | A time entry fails on a locked period | Scoro locks time entries in a closed period. Ask a Scoro administrator to reopen the period. | | **Link your Scoro account again** appears | Your Scoro password changed, which ends the user token. Select **Link your account** again. | | Requests fail with a rate limit message | Scoro limits requests per account. Wait a moment, or narrow the request. | ## 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) * [Accelo](https://hebno.com/docs/integrations/accelo.md) * [Xero](https://hebno.com/docs/integrations/xero.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.