Monroe

Documentation

Hire Monroe. Then put it to work.

Monroe lives in Slack, Microsoft Teams, and email. The chat channels connect from the dashboard (a Microsoft admin approves Monroe if your organization requires it); email needs nothing installed, since every workspace gets its own Monroe address. After a 5-minute setup, you connect the tools you already use, set a budget, and Monroe starts handling the deal work your team would otherwise do manually: OM screens, rent roll reviews, IC memo drafts. These docs split into two lanes. Pick the one that matches what you came to do.

If you run Monroe in your workspace, start here

The operator path: get Monroe live, give it its first real task, then learn the model that makes it trustworthy day to day.

  • Hire Monroe in 5 minutes: Sign up, check out, add Monroe to Slack, run your first task. Most teams have Monroe shipping real work by the end.
  • Your first task: Four example workflows new teams run on day one. Copy them, adapt, tell Monroe to handle them on a schedule.
  • Workspaces: one Monroe per workspace, isolated, persistent. How shared state works across your team.
  • Credits and billing: what a credit is, how to read your usage, when overage starts, how to raise or lower your cap.
  • Approval gates: how Monroe decides what needs your OK before executing, and how to customize the approval rules for your team.
  • Skills: how Monroe picks up your team’s house style and standing rules. How to teach it, how to inspect what it remembers, how to roll back.
  • Security overview: per-workspace isolation, OAuth-only credentials, spend caps checked before every run, approval gates, a logged run history, SOC 2 status.
  • Audit log: every run logged: who, where, when, credits. Browser + exports on the roadmap; Enterprise CSV export on request.
  • Data residency: US-East today. EU residency on the Enterprise roadmap; AP-Southeast on the 2027 roadmap.

If you’re extending Monroe, start here

The builder path: wire Monroe into the tools, internal systems, and backends your firm already runs.

  • Slack install: one-click install, then choose channels, then set approval rules.
  • Microsoft Teams install: start in Channels, sign in with Microsoft, then add Monroe to a team or chat.
  • Email channel: your workspace’s own Monroe address: approved senders, how to CC or forward work, and what replies look like.
  • App connectors: Drive, Microsoft 365, SharePoint, HubSpot, Salesforce, QuickBooks, CRE systems, and thousands more. Per-connector scoping and revocation.
  • Model Context Protocol (MCP): advanced path for internal tools that already expose MCP.
  • Webhook API: coming soon: trigger Monroe runs from any system that can POST JSON.
  • Run log: what gets logged for every run and where to see it in your dashboard.

Stuck? Email support@getmonroe.com. We reply within a business day on Solo, faster on Team / Business / Enterprise.

Two specialist inboxes for when you need them: hello@getmonroe.comfor billing questions (the spend cap itself is owner-adjustable from the dashboard’s Billing & usage page, under Plans & credits), and enterprise@getmonroe.com for contract terms, roadmap commitments, and security review.