> ## 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. # Box > Attach, search and read Box files, folders and metadata in Hebno, link folders to projects, and save deliverables to a linked folder after you confirm. The Box integration makes the documents your firm keeps in Box available in client work. Attach a contract from a client folder, ask which files in an engagement folder mention a renewal clause, or filter by a metadata field such as client or matter number. Hebno saves a deliverable to a linked Box folder only after you confirm. ## At a glance | | | | - | - | | **Connection** | Personal connection. Each member connects their own Box account. | | **Default access** | Read and write. | | **Attach** | Files from folders you can open, including shared team content. Picking a folder attaches a folder reference, not its contents. | | **Search** | Hebno searches Box by file name, description, content, comments and tags, and reads metadata fields when a request mentions them | | **Link** | A project links to one or more Box folders as linked sources | | **Write** | Save a deliverable (Word, PowerPoint, Excel, PDF or Markdown) to a linked folder. Every write needs a person to confirm. | ## Before you start You need: * A Box account that can open the folders you want to use. Access is limited to what your account can already open. * If your firm uses Box Enterprise, a Box admin may need to authorise the Hebno app in the Admin Console under **Apps → Custom Apps Manager** before anyone can connect. Without that approval, members see a message that the app is not authorised for their enterprise. Box sets permissions on the app in its developer configuration rather than in the sign-in request. The Hebno app uses these: | Permission | Why Hebno needs it | | - | - | | **Read all files and folders stored in Box** | Lists folders, searches, reads file text and metadata, and downloads a file you attach | | **Write all files and folders stored in Box** | Uploads the deliverable you chose to save into a linked folder | Hebno does not request permission to manage users, groups, webhooks or enterprise settings. ## Connect Box **1. Check the integration is allowed** An owner or admin controls this under **Admin → Connectors → Catalogue**. If **Box** shows **Blocked**, ask an admin to set it to **Allow**. **2. Start the connection** Open **Settings → Connections**, find **Box** under **Files** and select **Connect**. You can also select **Connect** on the prompt that appears in chat the first time you use Box. **3. Approve access in Box** Sign in to Box, review the access request and select **Grant access to Box**. Hebno returns you to the app with a **Box connected** message. The row shows **Connected** with your Box email. Select **Reconnect** to switch accounts or **Disconnect** to remove the connection. Admins can revoke any member's connection from **Admin → Connectors → Connections**. ## What Hebno reads The folders your organisation selects are stored in the [knowledge index](https://hebno.com/docs/get-started/how-hebno-works.md) and searched by meaning, with permissions inherited from Box. Attaching a specific file reads it as it is now, with your account. Only the excerpts a reply used are stored with the conversation as its sources. | Box object | What Hebno uses | Typical questions | | - | - | - | | **File** | Name, size, parent folder, modified date, description, tags, and the text of Word, PowerPoint, Excel, PDF, text, CSV and Markdown files | "Which Contoso documents mention a termination for convenience clause?" | | **Folder** | Names and contents of a linked or attached folder, including subfolders | "What is in the Contoso Retail engagement folder?" | | **Search** | Matches on file name, description, content, comments and tags, narrowed to a folder or file type | "Find decks about store operations in the Northwind Advisory folder." | | **Metadata** | Values from the metadata templates attached to a file, for example client, matter number or review status | "Show the files in the Contoso folder where review status is Approved." | | **Comment** | Comments on a file | "What did the partner comment on the draft proposal?" | Attached files must be 25 MB or smaller. Images and files of other types appear in lists but cannot be read as text, so you are prompted to open them in Box. > [!WARNING] > > Excerpts a reply uses become part of the conversation. Anyone you share the conversation with can read them, even if they cannot open the file in Box. ## What Hebno writes Every write appears first as a confirmation card. You can change any field before you select **Confirm**. | Action | Box object | Fields on the card | | - | - | - | | **Save to folder** | File in a linked folder | Folder, filename, format (Word, PowerPoint, Excel, PDF or Markdown), template for Word and PowerPoint | ![Confirmation card for Box with editable fields](https://mintcdn.com/hebno/A7yItabWdPf4lOIs/images/card-box.png?fit=max\&auto=format\&n=A7yItabWdPf4lOIs\&q=85\&s=2f3596d0ad713856d980070879657498) A Box change pending confirmation. Nothing is written until you confirm. If the deliverable was saved to the same folder before, Hebno uploads a new version of that file and the card says **This will replace the existing file in** the folder. Hebno writes only the file you chose. It never deletes or moves other files, edits metadata, changes collaborators or creates shared links. ```mermaid theme={"system"} sequenceDiagram participant You participant Hebno participant BoxApp as Box You->>Hebno: Save the findings memo to the Contoso folder Hebno-->>You: Confirmation card with folder, filename, format You->>Hebno: Confirm Hebno->>BoxApp: Upload the file as you BoxApp-->>Hebno: File saved Hebno-->>You: Done, with a link to the file ``` ## Link a project to a folder Linking marks which Box folders belong to a project, so you can ask about "the client's files" without naming the folder. 1. Open the project and select **Brain**. 2. Under **Linked sources**, select **Link source**, then **Box**. 3. Browse to the folder, or paste a Box folder link, and select **Link**. The folder shows on the project, and each person still opens files with their own Box access. In chats tagged to the project, Hebno searches linked folders first, and the **Save** menu on a deliverable lists them as destinations. You can also link a folder to the organisation library from the library's **Linked sources**. See [Linked records](https://hebno.com/docs/projects/linked-records.md) and [Workspace library](https://hebno.com/docs/library/workspace-library.md). ## Use Box in chat * **Attach**: open the **+** menu, choose **Sources → Box**, and pick a file or a folder. Or type `/` and choose **Box**. * **Ask**: name the client, folder or document in your request. For example: > Search the Contoso Retail folder in Box for anything on store labour costs and summarise what each document says. > Which files in the engagement folder have review status Approved? Draft a document index from them. > Save the steering committee pack to the Contoso folder in Box. * **Research runs** show a **Reading a linked folder** step for Box, with a chip for each file Hebno read. * **Agents** can read linked Box folders on a schedule. A save an agent proposes appears in [agent approvals](https://hebno.com/docs/automate/agent-approvals.md) for review. ## Troubleshooting | Symptom | Fix | | - | - | | Box says the app is not authorised for your enterprise | A Box admin must authorise the Hebno app in the Admin Console under **Apps → Custom Apps Manager**, then you can connect again. | | A folder you expect is missing | Your Box account cannot open it. Ask the folder owner to invite you as a collaborator. | | A file is listed but Hebno cannot read it | The file is larger than 25 MB or is an image or another type that cannot be read as text. Open it in Box. | | **Save to folder** says your account cannot write | Your Box role on the folder is viewer only, or the connection needs refreshing. Ask for editor access, or reconnect under **Settings → Connections**. | | Metadata filters return nothing | The template is not attached to those files, or your account cannot see the template. Check the file's metadata in Box. | | A folder link is rejected | Paste a Box folder link you can open, or browse to the folder instead. | ## 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) * [Save and export](https://hebno.com/docs/deliverables/save-and-export.md) * [Dropbox](https://hebno.com/docs/integrations/dropbox.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.