> ## Documentation Index
> Fetch the complete documentation index at: https://docs.plastics.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Setup

> Requirements, deployment through the Microsoft 365 admin center, and sideloading for a single device.

Deployment is an administrator task. Individual sideloading is available for testing.

## Requirements

**Client and platform**

| Requirement | Value |
| - | - |
| Host application | Outlook (Mailbox host only) |
| Minimum requirement set | Mailbox 1.1 |
| Requirement set for the ribbon button and pinnable pane | Mailbox 1.5 |
| Form factor | Desktop form factor, which covers Outlook on Windows, Outlook on Mac, and Outlook on the web |
| Activation | Message items in read form |
| Surfaces | Message read command surface, and message compose command surface |
| Transport | HTTPS only. The add-in refuses to build a manifest for a non-HTTPS origin |

No mobile form factor is declared, so the add-in does not appear in Outlook mobile.

**Accounts and network**

* Each user needs a plastics.com account. They sign in from inside the pane.
* Pricing, agent status, and RFQ conversion additionally require a merchant organization and a merchant role. See [Feature availability](https://docs.plastics.com/integrations/outlook/overview.md#feature-availability).
* The manifest declares application domains for your plastics.com workspace origin and for the identity endpoints used by the sign-in dialog: `api.workos.com`, `login.microsoftonline.com`, `login.live.com`, and `accounts.google.com`. Clients must be able to reach these.

## Install

**1. Copy the manifest URL (plastics.com org admin)**

In plastics.com, open **Integrations**, find the **Outlook Add-in** card, and choose **Deploy**. The dialog shows your manifest URL, which follows the pattern:

```text theme={null}
https://<your-plastics-workspace-host>/api/outlook/manifest.xml
```

The **Deploy** action is limited to organization admins. The Integrations page itself is limited to merchant roles.

Prefer the manifest URL over the downloaded file: Microsoft 365 polls the URL, so the add-in stays current without a re-upload. A **Download** option is available if your process requires a file.

**2. Upload to the Microsoft 365 admin center (M365 tenant administrator)**

Signed in as a Global Administrator or Exchange Administrator:

1. Go to `admin.microsoft.com`.
2. Open **Settings**, then **Integrated apps**, then **Upload custom apps**.
3. Choose **Office Add-in**, and provide the manifest URL. Uploading the XML file is also supported.

**3. Assign users (M365 tenant administrator)**

Assign the add-in to specific users, to groups, or to the whole organization. Centralized deployment can take up to 24 hours to reach every user's ribbon.

**4. Open an email and sign in (end user)**

In Outlook, open any message and click **Ask Herman** in the ribbon. The pane opens on the **This email** tab and prompts for sign-in. Sign-in happens in an Outlook dialog window, and the session persists across messages. The **Settings** menu in the pane header offers unit preferences and sign out.

## Sideloading for a single device (testing)

**Outlook desktop**

1. Open Outlook on Mac or Windows.
2. Go to **Insert**, then **Get Add-ins**, then **My Add-ins**.
3. Choose the overflow menu, then **Add a Custom Add-in**, then **Add from file**.
4. Select the downloaded manifest XML and confirm.
5. Open any email and click **Ask Herman** in the ribbon.

**Outlook on the web**

1. Open Outlook on the web.
2. Go to **Settings**, then **View all Outlook settings**, then **General**, then **Manage add-ins**.
3. Choose **Add a custom add-in**, then **Add from file**.
4. Upload the manifest XML.

## Updates

The add-in ID is stable across releases, so updating the manifest never requires users to reinstall. If you deployed by URL, Microsoft 365 picks up changes on its own polling schedule. If you uploaded a file, re-upload it to take a new version.

> [!NOTE]
>
> Before rolling out widely, your IT reviewer will want [Security and data](https://docs.plastics.com/integrations/outlook/security-and-data.md), which covers the mailbox permission, what leaves the mailbox, and where it is processed.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.