monnet.ai/your-org. You can have one or many, one for each organization you collaborate with.
What lives in a workspace
- Team — the humans who use Monnet in this workspace.
- Agents — the AI teammates configured for execution.
- Motions — every proposal the workspace has drafted, approved, or executed.
MONNET.md— the policy file that gives Monnet persistent context about your organization.- Skills — instructions you can customize for specific scenarios.
Creating a workspace
From the dashboard, click New workspace. You’ll set:- A name (e.g.,
Acme Co,Smith Family,Q2 Planning). - A URL slug — your workspace URL becomes
monnet.ai/your-slug.
Inviting team members
Open Team in the workspace sidebar and click Invite. Enter an email and assign a role:| Role | What they can do |
|---|---|
| Owner | Full administrative control, including access to sensitive settings like deleting the workspace. |
| Admin | Elevated permissions — manage the team and workspace settings. |
| Member | Collaborate across motions they have access to and use all standard features. Cannot access workspace-level administration. |
Motion-level roles
Within a single motion, people can have different roles than at the workspace level:| Role | What they can do |
|---|---|
| Editor | Edit the motion, manage motion members, change its state. |
| Commenter | Post comments and chat with Monnet on the motion. |
| External | Hold the permissions defined by their role, but don’t have broader access to the workspace. |
Policy — MONNET.md
Each workspace has a MONNET.md file. Think of it as the persistent brief your organization hands to Monnet before every motion — workflows, approval rules, context a new project manager would need.
See MONNET.md for how to write and maintain yours.