> ## 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. # Google Workspace > Connect one Google account to use Drive, Gmail, Calendar and Meet in Hebno, approving each product's permissions only when you use it. The Google Workspace integrations make a client's files, email, calendar and meetings available in your work from a single Google connection. Hebno reads Drive documents, Gmail threads, Calendar events and Meet transcripts with your own Google permissions, cites each one, and writes back (a saved file, a sent email, a calendar invitation) only after you confirm. ## At a glance | | | | - | - | | **Connection** | Personal. Each member connects their own Google account once. Hebno shows one connection for all Google products. | | **Default access** | Read and write. Sending email and sending invitations are separate permissions you grant on top of read access. | | **Attach** | Drive files, Gmail messages, Calendar events, Meet transcripts and notes | | **Search** | Hebno searches the Google products you have granted when a request mentions a client, a person, a file, an email or a meeting | | **Link** | A project links to Drive folders (including shared drives) | | **Write** | Save a deliverable to a linked Drive folder, as a Google Doc, Slides deck or Sheet if you choose, send an email, send a calendar invitation | ## The integrations | Integration | What Hebno reads | What Hebno writes | | - | - | - | | [Google Drive](https://hebno.com/docs/integrations/google-drive.md) | Files in My Drive and shared drives, including Docs, Sheets and Slides | Deliverables saved to a linked folder, as Office files or Google formats | | [Gmail](https://hebno.com/docs/integrations/gmail.md) | Messages and threads in your mailbox | Emails you send from a confirmation card | | [Google Calendar](https://hebno.com/docs/integrations/google-calendar.md) | Your events, colleagues' free and busy times | Calendar invitations with a Meet link | | [Google Meet](https://hebno.com/docs/integrations/google-meet.md) | Conference records, transcripts, Gemini notes, recording details | Nothing. Meet is read only. | ## One connection, approved step by step Hebno connects to Google once per member. The first time you use a product, Google requests approval of only that product's permissions. A member who connects Drive is never asked for Gmail, Calendar or Meet permissions until they use those products. Grants are cumulative, so approving Calendar later leaves your Drive access in place. **1. Open Connections** Go to **Settings → Connections**. Or start in chat: type `/`, choose a Google product, and select **Connect**. **2. Connect Google** Find the product (for example **Google Drive**), select **Connect**, sign in to Google and approve the permissions on the consent screen. You return to the chat. **3. Add products as you need them** Each other Google product shows **Grant access** on its row. Select it to approve that product's permissions. The row shows **Connected** once Google has granted them. **4. Allow sending, if you want it** Gmail shows **Allow sending** and Google Calendar shows **Allow invitations** after you connect them. These are separate grants, so reading and sending are your own choices. ![Settings Connections page listing connected systems with Connect and Grant access buttons](https://mintcdn.com/hebno/n4ZjS29g8cTdiNHz/images/settings-connections.png?fit=max\&auto=format\&n=n4ZjS29g8cTdiNHz\&q=85\&s=79b5a753a62568960ed57fbe057a2328) Google products listed on the Connections page, each with its own status. > [!NOTE] > > Disconnecting any Google product removes the whole Google connection, including Drive, Gmail, Calendar and Meet. You can connect again at any time. ## Permissions Hebno requests Every authorisation includes `openid`, `email` and `profile` to identify the account. Each product adds its own scopes. | Product | Scopes | Grant | | - | - | - | | Google Drive | `https://www.googleapis.com/auth/drive` | Base | | Gmail | `https://www.googleapis.com/auth/gmail.readonly` | Base | | Gmail, sending | `https://www.googleapis.com/auth/gmail.send` | **Allow sending** | | Google Calendar | `https://www.googleapis.com/auth/calendar.readonly`, `https://www.googleapis.com/auth/calendar.freebusy`, `https://www.googleapis.com/auth/directory.readonly` | Base | | Google Calendar, invitations | `https://www.googleapis.com/auth/calendar.events` | **Allow invitations** | | Google Meet | `https://www.googleapis.com/auth/meetings.space.readonly`, `https://www.googleapis.com/auth/drive.meet.readonly`, `https://www.googleapis.com/auth/calendar.readonly` | Base | Each product page explains why Hebno needs its scopes. ## What Google enforces Hebno uses your Google token, so it can read only what your account can already open. Google's own sharing, shared drive membership and Meet participation rules apply on every request. Hebno stores the excerpts a reply used with the conversation, and nothing else from your Google account. > [!WARNING] > > Excerpts from Gmail, Calendar and Meet that a reply uses become part of the conversation. Anyone you share the conversation with can read them. ## Admin trust and organisation settings Google Workspace administrators decide whether third-party apps can access restricted data such as Gmail and Drive. If your organisation restricts these services, a super admin marks Hebno as trusted once, and members then connect as normal. See [Google Workspace admin](https://hebno.com/docs/integrations/google-workspace-admin.md). Owners and admins can allow or block each Google integration under **Admin → Connectors → Catalogue**, choose **Read only** or **Read and write** for each, and revoke any member's connection under **Admin → Connectors → Connections**. A blocked integration disappears from chat and cannot be authorised. > [!NOTE] > > An owner or admin can also select **Enable for the organisation** on a Google card. A Workspace super admin approves that product's permissions once for the domain, and members connect without seeing a Google consent screen. This removes a prompt only. Each member still connects their own account and sees only what their own permissions allow. ## Where to go next > [card] [Google Drive](https://hebno.com/docs/integrations/google-drive.md) > > Search and attach files, link folders and save deliverables as Docs, Slides or Sheets. > [card] [Gmail](https://hebno.com/docs/integrations/gmail.md) > > Search threads and send emails from a confirmation card. > [card] [Google Calendar](https://hebno.com/docs/integrations/google-calendar.md) > > Read events, find shared free time and send invitations with a Meet link. > [card] [Google Meet](https://hebno.com/docs/integrations/google-meet.md) > > Read transcripts, Gemini notes and recording details from client meetings. > [card] [Google Workspace admin](https://hebno.com/docs/integrations/google-workspace-admin.md) > > Trust Hebno, scope it by organisational unit and revoke access. ## Related * [How integrations work](https://hebno.com/docs/integrations/index.md) * [Permissions and access](https://hebno.com/docs/integrations/permissions-and-access.md) * [Microsoft 365](https://hebno.com/docs/integrations/microsoft-365.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.