Workspaces

Each Monroe customer gets a dedicated workspace. The workspace is the unit of:

• Billing. One subscription. Credits shared across everyone on your team.
• State. Memory, skills, connectors, audit log all live in the workspace.
• Isolation. Other Monroe customers never see your data. Ever. We don't share infrastructure between workspaces — your Monroe runs in its own container, on its own EFS volume, with its own credentials.

Adding teammates

Anyone in your workspace can talk to Monroe. There's no per-seat fee — invite the whole team. Connect Slack/Teams and Monroe sees @-mentions and DMs from any workspace member.

Admin-only actions:

• Connecting/disconnecting tools (OAuth scopes affect everyone)
• Setting the spend cap
• Approving Enterprise-tier upgrades
• Exporting the audit log

Multi-workspace (Enterprise)

Bigger orgs sometimes want separate Monroes per team — e.g. Marketing Monroe with HubSpot + Mailchimp connectors, Engineering Monroe with GitHub + Linear + PagerDuty. Enterprise contracts include multi-workspace bundles with shared billing and SSO via Clerk Organizations.

Workspace lifecycle

• Created — workspace.created event from Clerk → Monroe provisions a Fargate task + EFS access point + OpenRouter sub-key
• Suspended — past-due billing, hit spend cap with no override, trial ended without conversion → desired_count=0, EFS state preserved
• Resumed — payment recovered → desired_count=1, Monroe is back in <60s
• Deleted — 30-day retention of EFS data after delete, then permanent wipe + SSM parameter sweep

Next: credits and billing, approval gates.