> ## 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. # Front > Search Front shared inboxes, conversations, comments and tags you can access, and add comments, draft replies and tag conversations after you confirm. The Front integration makes your team's shared client inboxes available in client work. Ask what Contoso Retail last asked the support inbox about the data extract, pull the internal discussion on a conversation into a status update, or draft a reply for a teammate to review. Hebno searches Front live with your own access, cites each message and comment, and writes only after you confirm. Hebno never sends a reply: you send it from Front. ## At a glance | | | | - | - | | **Connection** | Personal connection. Each member connects their own Front teammate account. | | **Default access** | Read and write. | | **Attach** | A conversation, with its messages and comments, from an inbox you can open | | **Search** | Hebno searches Front when a request mentions a client, an inbox, an email thread, a tag or a teammate's comment | | **Link** | A project links to a Front tag or a shared inbox | | **Write** | Add an internal comment, create a draft reply, tag a conversation. Every write needs a person to confirm. | ## Before you start You need: * A Front teammate account with access to the shared inboxes you want to use. Hebno reads only the inboxes and conversations your Front teammate can open, including your own individual inbox. * An allowed integration. An owner or admin sets **Front** to **Allow** under **Admin → Connectors → Catalogue**. * If your Front company restricts app installs, a Front admin approves Hebno under **Settings → Company → App store** first. Hebno connects with OAuth to the Front Core API. Front groups its OAuth scopes by namespace, and Hebno requests these: | Scope | Why Hebno needs it | | - | - | | **Shared resources: Read** | Search and read conversations, messages, comments and tags in shared inboxes you can open | | **Shared resources: Write** | Add comments, create drafts and apply tags in those inboxes after you confirm | | **Private resources: Read** | Read conversations in your own individual inbox when you ask about them | | **Private resources: Write** | Create a draft or comment on a conversation in your individual inbox after you confirm | Hebno does not request **Send** or **Delete** scopes, so it cannot send a message or delete a conversation. ## Connect Front **1. Check the integration is allowed** An owner or admin controls this under **Admin → Connectors → Catalogue**. If **Front** shows **Blocked**, ask an admin to set it to **Allow**. **2. Start the connection** Open **Settings → Connections**, find **Front** under **Communication** and select **Connect**. You can also select **Connect** on the prompt that appears in chat the first time you use Front. **3. Approve access in Front** Sign in to Front, review the permissions and select **Authorize**. Hebno returns you to the app with a **Front connected** message. The row shows **Connected** with your Front teammate name and company. Admins can revoke any member's connection from **Admin → Connectors → Connections**. ## What Hebno reads Hebno searches Front live, with your account, using Front's conversation search. Only the messages and comments a reply used are stored with the conversation as their sources. | Front object | Fields Hebno uses | Typical questions | | - | - | - | | **Inbox** | Name, type (shared or individual), teammates with access | "Which inboxes receive Contoso email?" | | **Conversation** | Subject, status (open, archived, snoozed), assignee, tags, inbox, last message time, link | "What is still open from Contoso Retail in the client services inbox?" | | **Message** | Sender, recipients, date, subject, body text, attachment names | "What did Contoso ask about the store-level pricing extract?" | | **Comment** | Author, date, text of internal discussion on a conversation | "What did Priya say internally about the Contoso data request?" | | **Tag** | Name, conversations with the tag | "Show every conversation tagged Contoso pricing review this month." | | **Contact** | Name, email handles, linked conversations | "When did Sarah Chen last email us?" | Each message and comment in a source links back to the conversation in Front. > [!WARNING] > > Excerpts a reply uses become part of the conversation. Anyone you share the conversation with can read them, including client emails and internal comments from inboxes they cannot open in Front. ## What Hebno writes Every write appears first as a confirmation card. You can change any field before you select **Confirm**. | Action | Front object | Fields on the card | | - | - | - | | **Add a comment** | Comment on a conversation | Conversation, comment text, teammates to mention | | **Create a draft reply** | Draft on a conversation | Conversation, recipients, body, shared or private draft | | **Tag a conversation** | Tag on a conversation | Conversation, tags to add | ![Confirmation card for Front with editable fields](https://mintcdn.com/hebno/JIjAXWoGoB3PLSSb/images/card-front.png?fit=max\&auto=format\&n=JIjAXWoGoB3PLSSb\&q=85\&s=c1d4169e95fb8e40169cc9a4d205d549) A Front change pending confirmation. Nothing is written until you confirm. A draft reply appears on the conversation in Front with you as its author. A shared draft is visible to teammates on the inbox, so a colleague can review it. You or a teammate send it from Front. Hebno never sends messages, assigns or archives conversations, removes tags, or deletes anything. ```mermaid theme={"system"} sequenceDiagram participant You participant Hebno participant Front You->>Hebno: Draft a reply to Contoso confirming the readout on 20 November Hebno->>Front: Search conversations from Contoso Retail about the readout Front-->>Hebno: Conversation Readout date, last message from Sarah Chen Hebno-->>You: Confirmation card with conversation, recipients, body You->>Hebno: Confirm Hebno->>Front: Create a shared draft as you Front-->>Hebno: Draft created Hebno-->>You: Done, with a link to the draft in Front ``` ## Link a project to a tag Linking marks which Front conversations belong to an engagement, so you can ask "what has the client asked?" without naming the inbox. 1. Open the project and select **Brain**. 2. Under **Linked records**, select **Link record**, then **Front**. 3. Search for the tag your team applies to the engagement, for example **Contoso pricing review**, or pick a shared inbox, and select it. In chats tagged to the project, Hebno starts with conversations under the linked tag or inbox, and comment and draft cards default to them. Each person still reads Front with their own access. See [Linked records](https://hebno.com/docs/projects/linked-records.md). ## Use Front in chat * **Attach**: open the **+** menu, choose **Sources → Front**, and pick a conversation. Or type `/` and choose **Front**. * **Ask**: name the client, inbox, tag or teammate in your request. For example: > Summarise every open Contoso conversation in the client services inbox and who each is assigned to. > What has Sarah Chen asked us about the pricing extract since 1 November? Quote her messages. > Add an internal comment on the Contoso readout conversation for Priya with the three open questions from this chat. * **Research runs** show a **Reviewing Front** step, with a chip for each conversation Hebno read. * **Agents** can read Front on a schedule, for example a morning list of unanswered client conversations. Writes an agent proposes appear in [agent approvals](https://hebno.com/docs/automate/agent-approvals.md) for review. ## Troubleshooting | Symptom | Fix | | - | - | | Front shows that the app needs admin approval | Your Front company restricts app installs. Ask a Front admin to approve Hebno, then connect again. | | An inbox you expect does not appear | Your teammate account has no access to it. Ask a Front admin to add you to the inbox or its team. | | A write fails with a forbidden message | The conversation is in an inbox where you have no access, or in another teammate's individual inbox. Comment from a conversation you can open. | | A draft does not appear for a colleague | The draft was created as private. Choose **Shared** on the card next time, or share it from Front. | | Requests fail with a rate limit message | Front limits API requests per minute for your company. Wait a minute and retry. | | **Reconnect Front** appears | The authorisation was revoked or your Front session ended. Select **Reconnect** under **Settings → Connections**. | ## Related * [How integrations work](https://hebno.com/docs/integrations/index.md) * [Permissions and access](https://hebno.com/docs/integrations/permissions-and-access.md) * [Gmail](https://hebno.com/docs/integrations/gmail.md) * [Outlook](https://hebno.com/docs/integrations/outlook.md) * [Slack](https://hebno.com/docs/integrations/slack.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.