> ## 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. # Microsoft Teams > Read Teams meetings, transcripts, Copilot notes, channel messages and chats in Hebno, and post a channel message after you confirm. The Microsoft Teams integration lets client work start from what was actually agreed. Ask what Contoso committed to in last week's call, and Hebno reads the Copilot notes or the transcript and cites the meeting. It also reads channel messages and chats you can open, and posts a message to a channel when you confirm the card. ## At a glance | | | | - | - | | **Connection** | Personal connection. Each member connects their own Microsoft account. A Microsoft directory administrator approves the transcript and message permissions once. | | **Default access** | Read and write | | **Attach** | A Teams meeting's details, Copilot notes, transcript or full record | | **Search** | Hebno searches meetings, channel messages and chats when a request mentions a client, a person, a decision or a discussion | | **Link** | Not linkable. Teams is searched by client, person or domain. | | **Write** | Post a message to a channel. Every post needs a person to confirm. | ## Before you start You need a Microsoft work or school account. Teams permissions need a Microsoft directory administrator to approve them, because meeting transcripts and messages are sensitive. | Permission | Why Hebno needs it | | - | - | | `User.Read` | Show which account is connected | | `Calendars.ReadBasic` | List your Teams meetings from the last 60 days, without message bodies | | `OnlineMeetings.Read` | Look up a meeting you organised or were invited to | | `OnlineMeetingTranscript.Read.All` | Read transcripts of meetings you can already open | | `OnlineMeetingAiInsight.Read.All` | Read Copilot meeting notes and action items. Copilot notes also need a Microsoft 365 Copilot licence. | | `ChannelMessage.Read.All` | Read messages in channels you can already open | | `Team.ReadBasic.All` | List the teams you are a member of | | `Channel.ReadBasic.All` | List the channels in those teams | | `Chat.Read` | Read your own chats | | `ChannelMessage.Send` | Post a channel message you confirmed. Added when you select **Allow posting**. | `OnlineMeetingTranscript.Read.All`, `OnlineMeetingAiInsight.Read.All` and `ChannelMessage.Read.All` need administrator consent even though they are delegated. Approving Teams does not approve SharePoint or any other Microsoft integration. > [!NOTE] > > Copilot notes need a Microsoft 365 Copilot licence on the account, and the organisation must allow apps to read transcripts. Without them, meetings, details and transcripts still work. ## Connect Microsoft Teams **1. Enable Teams for the organisation** An owner or admin opens **Admin → Connectors → Catalogue**, finds **Microsoft Teams** under **Communication**, selects **Enable for the organisation** and approves in Microsoft as a directory administrator. **2. Connect your account** Open **Settings → Connections**, find **Microsoft Teams** and select **Connect** or **Grant access**. You can also type `/` in chat and choose **Microsoft Teams**. With the organisation enabled, you see no consent screen. **3. Allow posting (optional)** Select **Allow posting** on the **Microsoft Teams** row to add `ChannelMessage.Send`. The same button appears on a channel message card if you try to post first. If a member sees "Microsoft Teams reads meeting transcripts, which a Microsoft administrator in your organisation must approve", an admin needs to complete step 1. Enabling for the organisation removes a prompt only. Each member still connects their own account, and Microsoft enforces each member's own permissions. See the [Microsoft Entra admin guide](https://hebno.com/docs/integrations/microsoft-entra-admin.md). ## What Hebno reads | Teams object | Fields Hebno uses | Typical questions | | - | - | - | | **Meeting** | Title, time, organiser, Teams link, attendees (optional ones marked) | "When did we last meet Contoso?" | | **Copilot notes** | Meeting notes with subpoints, and action items with owners | "What actions came out of the Contoso kickoff?" | | **Transcript** | Timed lines in the form `[mm:ss] Speaker: text` | "What exactly did Priya say about the budget?" | | **Channel message** | Team, channel, sender, time, text, replies | "What did the delivery channel decide about the interview schedule?" | | **Chat** | Participants, time, sender, text, in chats you are part of | "What did Marcus and I agree about the survey sample?" | Hebno reads meetings that your calendar shows as online meetings from the last 60 days, up to 200 meetings. Teams retains meeting records for 60 days after a meeting ends. For a recurring meeting, Hebno uses only the notes and transcript from 30 minutes before to 3 hours after the occurrence. When Hebno reads a meeting, it uses Copilot notes first (they are already a summary), then a transcript excerpt, then the meeting details. The source label shows **Copilot notes**, **Transcript** or **Meeting details**, with the attendee count. A meeting search returns up to 3 meetings. Attaching a meeting offers its **Full meeting record**, **Meeting details**, **Copilot notes** and **Transcript** as separate files. Gaps are explained inside the file, for example "No Copilot notes yet. They can take up to four hours after the meeting ends." or "No transcript. Transcription must be turned on during the meeting." Channel messages and chats are searched by the people, words and time range in your request, and only in channels and chats your account can open. Reads are live, and only the excerpts a reply used are stored with the conversation as its sources. ## What Hebno writes Every post appears first as a confirmation card. You can change any field before you select **Confirm**. | Action | Teams object | Fields on the card | | - | - | - | | **Post a channel message** | Channel message | Team, channel, message text | ![Confirmation card for Microsoft Teams with editable fields](https://mintcdn.com/hebno/A7yItabWdPf4lOIs/images/card-microsoft-teams.png?fit=max\&auto=format\&n=A7yItabWdPf4lOIs\&q=85\&s=d1c97d30c31345e68b6c489a94421578) A Microsoft Teams change pending confirmation. Nothing is written until you confirm. The message is posted as you. Hebno never posts to a channel on its own, never starts or joins meetings, never sends direct chat messages, and never edits or deletes messages. ```mermaid theme={"system"} sequenceDiagram participant You participant Hebno participant Teams You->>Hebno: Post the action list to the Contoso delivery channel Hebno->>Teams: Find the Contoso team and delivery channel Teams-->>Hebno: Team and channel Hebno-->>You: Confirmation card with team, channel, message You->>Hebno: Confirm Hebno->>Teams: Post the message as you Teams-->>Hebno: Message posted Hebno-->>You: Done, with a link to the message ``` ## Use Microsoft Teams in chat * **Attach**: open the **+** menu, choose **Sources → Microsoft Teams**, and pick a meeting from the last 60 days, then one of its files. Or type `/` and choose **Microsoft Teams**. * **Ask**: name the client, the person or the decision. For example: > Summarise what Contoso agreed in our last two Teams meetings and list who owns each action. > What did the delivery channel say about the interview schedule this week? > Post a short status update to the Contoso delivery channel with this week's three actions. * **Research runs** show a **Reviewing recent Teams meetings** step, with a chip for each meeting, formatted as **Teams meeting, date**. * **Agents** can read Teams on a schedule, for example a Monday digest of last week's client meetings. Posts an agent drafts appear in [agent approvals](https://hebno.com/docs/automate/agent-approvals.md). > [!WARNING] > > Transcripts, notes and messages a reply uses become part of the conversation. Anyone you share the conversation with can read them. ## Troubleshooting | Symptom | Fix | | - | - | | Teams asks for an administrator | An owner or admin selects **Enable for the organisation** on the **Microsoft Teams** card. | | **Copilot notes need your administrator to approve them for Hebno** | An admin approves the Teams permissions again with **Enable for the organisation**, so the Copilot notes permission is included. | | **Copilot notes need a Microsoft 365 Copilot licence** | The account has no Copilot licence. Hebno uses the transcript instead. | | **No transcript. Transcription must be turned on during the meeting** | Turn on transcription in future meetings. | | **Your organisation has turned off transcript access for apps** | A Microsoft administrator must allow apps to read transcripts. | | **Meeting not found. Teams keeps meetings for 60 days after they end** | Use the notes you saved, or ask for a more recent meeting. | | **No Teams meeting in the last 60 days matched** | Name the client, an email domain or a person. | | **Allow posting** appears on a card | Select it to grant `ChannelMessage.Send`, then confirm again. | ## Related * [Microsoft 365](https://hebno.com/docs/integrations/microsoft-365.md) * [Outlook Calendar](https://hebno.com/docs/integrations/outlook-calendar.md) * [Microsoft Entra admin guide](https://hebno.com/docs/integrations/microsoft-entra-admin.md) * [Permissions and access](https://hebno.com/docs/integrations/permissions-and-access.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.