How it works
The Microsoft 365 components involved, what each one does, and what data moves between them.
Clad connects to your Microsoft 365 tenant through an application that Clad registers in Microsoft Entra ID for your organization alone. It has its own application ID and is not shared with any other Clad customer. Your administrators approve it once, then decide what it can reach.
Components
| Component | Where it lives | Role |
|---|---|---|
| Clad application | Clad's Microsoft Entra ID tenant | The identity Clad uses to call Microsoft Graph, dedicated to your organization. Appears in your tenant as the Enterprise application Clad for your organization's name after approval. |
| Mail access group | Your Exchange Online | A mail-enabled security group. Clad works with its members' mailboxes. |
| Exchange role assignments | Your Exchange Online | Grant Clad mail access, scoped to the group. |
| SharePoint site permissions | Your SharePoint Online | Grant Clad access to the sites it works in. |
| Clad environment | Clad (AWS, United States) | An environment dedicated to your organization, in its own AWS account with its own database and compute. Not shared with any other customer. |
Data flow
| # | Direction | What moves | How |
|---|---|---|---|
| 1 | Microsoft 365 → Clad | New messages and attachments in the inboxes of group members | Read through Microsoft Graph. |
| 2 | Clad → Microsoft 365 | Outgoing email | Sent from the responsible employee's own mailbox, so replies return to that employee. Each email is sent only after one of your employees approves it. |
| 3 | Microsoft 365 → Clad | Documents in granted SharePoint sites | Read through Microsoft Graph. |
| 4 | Clad → Microsoft 365 | Filed documents | Written to granted SharePoint sites through Microsoft Graph. |
| 5 | Employee → Clad | Sign-in | Microsoft Entra ID single sign-on (OpenID Connect). Passwords stay with Microsoft. |
Authentication
Clad calls Microsoft Graph with the client credentials flow. It authenticates as your organization's Clad application with a federated identity credential: Clad's workload in AWS presents a short-lived token from its own identity, and Microsoft Entra ID exchanges it for a Graph access token. The application has no client secret and no certificate, and no credential is created, shared or stored in your tenant.
Clad is operated by Docshield Inc. · Wilmington, DE · New York, NY