> ## Documentation Index > Fetch the complete documentation index at: https://docs.mercora.io/llms.txt > Use this file to discover all available pages before exploring further. # Microsoft 365 > Connect your Microsoft 365 organization once, then turn on Email, Files and Teams. The Copilot and automations read what you allow, and every send or change waits for an Approve. Microsoft 365 is one connection for your workspace, with three parts you turn on separately: | Part | What Mercora can do | | - | - | | **Email** | Read, send, reply, forward and draft from the shared mailboxes you list, and add calendar events. | | **Files** | Find and read files in the SharePoint folders you connect, and read and update the workbooks you connect. Never the freight master. | | **Teams** | The Copilot in Teams chats, deal capture from channels, and posts to channels Mercora was added to. | Mercora uses only the parts you turn on, and only the mailboxes, folders and channels you list. Reading runs on its own. Sending an email, posting in Teams or changing a file always stops on a card that names exactly what will happen, and waits for an **Approve**. Each member can also sign in with their own Microsoft account, so the Copilot can read and draft as them. See [Your own Microsoft sign-in](#your-own-microsoft-sign-in). > [!NOTE] > > Microsoft 365 and its **Email**, **Files** and **Teams** parts are workspace modules. A workspace admin turns each part on from the Microsoft 365 integration page, as described below. ## Connect your organization Before you start: you need to be a Mercora workspace admin, and someone who is an administrator of your Microsoft 365 organization must take part. **1. Open the Microsoft 365 page** Go to **Settings → Integrations** and click **Microsoft 365**. **2. Enter your organization** Under **Connection**, type your organization's Microsoft 365 domain (for example `veltana.example`) or its tenant id, and click **Connect Microsoft 365**. **3. Grant consent and sign in** Microsoft asks an administrator of your organization to grant admin consent, then to sign in. The account must be able to grant tenant-wide consent: a Global Administrator, Privileged Role Administrator, Cloud Application Administrator, Application Administrator or AI Administrator. Mercora then checks with Microsoft that the consent is in place. **4. Turn on the parts you want** Back in Mercora the page reads "Connected. Turn on the parts Mercora may use below." Switch on **Email**, **Files** and **Teams** as needed. If your Microsoft administrator later removes one of the rights a part needs, the part shows **Blocked by your Microsoft admin** and names the missing right. Ask your IT team to grant it to Mercora's app in Microsoft Entra. **Check** confirms the connection works and which parts your IT team left on. If your workspace was connected through an earlier SharePoint setup, the page asks an administrator to sign in once with **Confirm organization** before Email and Teams can be turned on. One Microsoft 365 organization can be connected to one Mercora workspace. ## Email Turn on **Email**, then list the shared mailboxes Mercora may read and send from as the workspace. **1. Add a mailbox** Under **Mailboxes**, enter its address (for example `ops@veltana.example`) and a name your team knows it by, such as "Operations", and click **Add mailbox**. **2. Limit Mercora to these mailboxes (recommended)** Microsoft grants Mercora's app every mailbox in your organization. Open **Limit Mercora to these mailboxes in Exchange**, run the commands it shows in Exchange Online PowerShell, then remove the app's Mail and Calendars permissions in Microsoft Entra, so only the limit applies. Tick **Done in Exchange** when finished. A member's own mailbox is never on this list. It needs that member's own sign-in. With Email on, the Copilot and automations can find and read emails in the listed mailboxes. Sending, replying, forwarding, creating a draft and adding a calendar event each wait for an Approve, on a card that shows who it is from and to, and what is attached. Mercora documents can be attached; each one is checked against the member's access. ## Files Turn on **Files**, then add the SharePoint folders and Excel workbooks Mercora may use as the workspace. **1. Copy a link in SharePoint** In SharePoint, use **Copy link** on a folder or an Excel file. **2. Add it** Under **SharePoint**, paste it into **Add a SharePoint link**, optionally give it a name, and add it. Mercora works out what the link is: * A **folder**: "Copilot can find, read and save files here". * An **Excel workbook**: "Copilot can read and edit its rows". * Any other file is refused. Add the folder it's in, or an Excel workbook. Reading files and rows runs on its own. Updating cells, adding a row to a table and saving a file each wait for an Approve. Saving never overwrites an existing file. ### The freight master One workbook can be your **freight master**: click **Make freight master** on it. It then reads "Changed only through Freight Rates": the ordinary file actions refuse it, whoever asks, and it changes only through the [Freight rates](https://docs.mercora.io/workflows/freight-rates.md) review. ## Teams Turning on **Teams** gives your members the Copilot in Teams, and lets you capture deals posted in your channels. ### Install the Mercora app **1. Download the app package** Under **Setup**, click **Download app package**. The Teams bot behind it is set up by the Mercora team for your workspace; until it is, the button is unavailable. **2. Upload it to Teams** Upload the package in the Teams admin center, or as a custom app. **3. Add Mercora to teams and chats** Add Mercora to the teams and group chats you want. Each one appears under **Chats and channels**, with capture off. ### Chat with the Copilot in Teams Each member links their own Teams account once: **1. Message Mercora** In Teams, open a chat with Mercora and send any message. **2. Link the account** Mercora replies with a card. Click **Link my Mercora account**, and confirm in the window Teams opens, where you sign in to Mercora as usual. If you've already signed in with your own Microsoft account in Mercora (see below), you're linked at your first message, with no card. Mercora then answers you in Teams with your own Mercora access. It is the same Copilot as on Home, so "What's the status of VCS-S-2026-0714?" gets the same answer in Teams. Answers are formatted for Teams, and charts are drawn as Teams charts. When the Copilot would change something, such as a record, the freight master, an email or a Teams post, it shows a card with **Approve**, **Edit** and **Reject**. Only the person who asked can decide. Send a new message and any card still waiting expires, with nothing changed. You can also type `/feedback` with a message, or pick **Send feedback** from the app's commands, to reach the Mercora team. ### @Mercora in channels and group chats Mention **@Mercora** in a channel or group chat and it answers you privately, in your 1:1 chat with Mercora, using your own access. Nothing reaches the thread unless you click **Post to thread** on the answer, which posts it under "Asked by" and your name. **Keep private** leaves it in your chat. Mercora stays silent until mentioned, and doesn't answer people who haven't linked a Mercora account. ### Capture deals from channels Mercora reads nothing from a channel or group chat until an admin picks where its messages go. Under **Chats and channels**, choose for each one: | Setting | What happens | | - | - | | **Off** | Mercora reads nothing. | | **Deal capture** | Each post is screened for deals; deals go to the Inbox for review. Mercora keeps a post's text only until it is screened. See [Deal capture](https://docs.mercora.io/workflows/deal-capture.md). | | **Automations** | Each post goes to the automations listening there. See [Automations](https://docs.mercora.io/workflows/automations.md). | Changing the setting posts a notice in that conversation. 1:1 chats are never captured: there the Copilot answers your members. ### Members **Members** lists who has linked their Teams account. Revoking a link signs that person out of Mercora in Teams. Removing a member from the workspace revokes their link too. ## What automations can do with it The bottom of the page lists every Microsoft 365 action, such as **Find emails**, **Send an email**, **Read rows**, **Update cells** and **Post to a channel**, and whether it reads or always asks first. Every action starts off: switch on what automations and the Copilot may use. See [Integrations](https://docs.mercora.io/integrations/overview.md). Automations act only as the workspace: they use the listed mailboxes, folders and channels, never a member's own sign-in. ## Your own Microsoft sign-in Any member can connect their own Microsoft account under **Settings → Integrations → Personal → Microsoft 365**, once an admin has connected the workspace. * **Your Microsoft account**: click **Sign in with Microsoft**. The Copilot can then read your mail, files and Teams messages and draft as you. Every send waits for your Approve. * **Chat with Mercora in Teams**: shows whether your Teams account is linked, with **Open Mercora in Teams**. With your own sign-in, the Copilot can also search the Teams messages you can read, in any chat, including on Home. Microsoft returns only what you can see. To stop, use **Disconnect** (your Microsoft sign-in) or **Unlink** (your Teams account) on the same page. ## Disconnect **Disconnect** on the Microsoft 365 page stops Mercora using your mailboxes, files and Teams, ends every member's own sign-in and Teams link, and turns capture off everywhere. Your lists stay for when you reconnect. Disconnecting removes Mercora's side. To withdraw the consent itself, your Microsoft administrator removes Mercora's app in Microsoft Entra. ## Who can do what | Permission | What it allows | | - | - | | **Email** (view) | Read the workspace's connected mailboxes and Teams channels. | | **Email** (edit) | Also send, reply, forward, draft, add calendar events and post in Teams as Mercora, each after an Approve. | | **Files** (view) | Find and read the workspace's connected SharePoint files and spreadsheets. | | **Files** (edit) | Also change cells, add rows and save files, each after an Approve. | Only workspace admins can connect Microsoft 365 or change its settings. See [Roles and permissions](https://docs.mercora.io/concepts/roles-and-permissions.md). ## Next steps > **[Deal capture](https://docs.mercora.io/workflows/deal-capture.md)** > > Review deals captured from your Teams channels and mailboxes. > **[Freight rates](https://docs.mercora.io/workflows/freight-rates.md)** > > Make a SharePoint workbook your freight master and keep it current. > **[Automations](https://docs.mercora.io/workflows/automations.md)** > > Start automations from emails and Teams posts. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.