Monroe

Documentation

Microsoft Teams install

Pilot only today. Slack is fully wired through the dashboard's Connect apps OAuth flow. Microsoft Teams installs are happening, but in a guided one-by-one fashion — you click the Connect apps → Microsoft Teams button in the dashboard and it opens an email draft to hello@getmonroe.com. We reply within one business day with the manifest .zip + the steps below. Self-serve "Get manifest" inside the dashboard is on the roadmap for the next release; the install instructions in the rest of this page describe the operator-assisted flow as it works today.

Teams setup takes a bit more coordination than Slack because Microsoft requires tenant-admin approval. Plan for 1–2 hours total, mostly waiting on your admin.

Step 1 — Request the manifest

In your dashboard → Connect apps → Microsoft Teams, click "Get manifest." We email your tenant admin a .zip with the Monroe app manifest + a one-page install summary.

Step 2 — Admin approves the manifest

Your tenant admin uploads the manifest in Microsoft Teams Admin Center:

1. Apps → Manage apps → Upload custom app

2. Approve the requested permissions (chat, file, calendar scoped to the channels Monroe will be in)

3. Set the app policy to allow Monroe for the relevant users

This is the part that takes 1–2 hours — admin queue time, not technical complexity.

Step 3 — Connect your tenant in the dashboard

Once admin approves, you'll get a "Tenant connected" notification in the Monroe dashboard. From there:

1. Choose teams/channels where Monroe should be active

2. Set the same approval rules as Slack would have

3. @-mention Monroe in a channel to confirm it's responsive

Capability parity with Slack

Everything Monroe can do in Slack, it can do in Teams:

  • Channel reading + posting
  • Direct messaging
  • Approvals via adaptive cards
  • File reading from SharePoint/OneDrive
  • Calendar integration via Outlook

Caveat: a few features ship Slack-first by a 1–2 week lag (most recently: voice memo input). Tracked in /changelog.

Troubleshooting

  • Admin queue backed up. Email enterprise@getmonroe.com — we can sometimes accelerate with a direct admin call.
  • "App not approved" — admin needs to add it to the org-wide allowlist. The manifest email contains the exact steps.
  • Multi-tenant orgs — each tenant needs its own install. Enterprise contracts support tenant-bundle billing.

Next: OAuth connectors.