Skip to main content
A workspace is the home for your team, your agents, your motions, and the context Monnet uses to help you decide. This page covers the workspace-side tasks. For the concept itself — what a workspace is, roles, how it fits together — see How Monnet works.

​
Create a workspace

From the sidebar, click New workspace and give it a name. The URL slug is generated from the name and can’t be changed after creation. You’re the first member, with the Owner role.

​
Workspace settings

Open the menu beside the workspace name in the top-left of the sidebar and select Settings. This opens the unified Settings window on Workspace → General. You can also open Settings from your avatar and choose any of the five workspace pages: General, Team, Scheduled, Playbooks, or Integrations. To go straight to the member list, select Invite members from either the workspace menu or your avatar menu. This opens Workspace → Team.

​
General

  • Workspace logo — upload a PNG, JPG, or WebP up to 5MB (256×256px recommended).
  • Workspace name — the display name.
  • URL slug — read-only; fixed at creation.
  • Timezone — your team’s clock. Monnet reads it whenever nobody’s at the keyboard: a scheduled check-in firing, the daily pass over dated plan steps. Set it, or Monnet will schedule things in the wrong hours.
  • Require two-factor authentication to access this workspace — require a verified second factor. See Two-factor authentication.
  • Danger zone — Owners can Delete workspace. This removes all motions, members, and files, and can’t be undone.
Click Save changes to apply.
Deleting a workspace is permanent. All motions, messages, files, and context are removed and cannot be recovered.

​
Two-factor authentication

Owners and admins can enable Require two-factor authentication to access this workspace in Settings → Workspace → General. New workspaces default to OFF. Workspaces that existed when this setting was introduced have it ON. Existing accounts keep their enrolled second factors. Turning the setting on does not sign anyone out. If your current session has not been verified with a second factor, the web app asks you to verify before continuing. If you haven’t set up a second factor, the 2FA screen guides you through setup first. Having a second factor set up is not enough: you must verify it once in your current session.
If you belong to, or have a pending invitation to, any workspace that requires 2FA, you must verify before continuing anywhere in the web app, including your other workspaces.

​
Team

The Team tab has two sub-views: Members (people) and AI Agents.

​
Invite and manage members

Click Invite a member, enter an email, and pick a workspace role:
  • Owner — can do anything, including delete the workspace.
  • Admin — can manage the team and settings, but can’t delete the workspace.
  • Member — collaborates on motions.
Monnet emails the invitee a link to accept or decline. You can resend or cancel a pending invitation from the team list. Click a member to open their panel, where admins and owners can set:
  • Function — what this person does on the team (e.g. “Designer”).
  • When to involve this person — guidance telling Monnet when to loop them in, and when not to. Worth filling in: it’s how Monnet stops pinging your CTO about copy changes.
  • Role — Owner, Admin, or Member.
From the same panel you can Remove from workspace (or Leave workspace for yourself).
A workspace must keep at least one Owner — you can’t remove or downgrade the last one.

​
AI agents

Agents are AI teammates that execute plan steps. Add one from Onboard a new agent — see Agents. People imported from Slack or Microsoft Teams also appear here. They join without a Monnet account and take part from their DMs; if they follow a motion link and sign up, they become full members.

​
Scheduled

Controls the nightly company brain ingest: whether it runs, and what instructions it runs with. See Company brain.

​
Playbooks

Playbooks are reusable instructions for a particular kind of motion — a competitive brief, an incident report, an onboarding checklist. Monnet loads the right one when it fits. Three ship with every workspace:

​
Write your own

Click Add playbook. It’s a guided form, not a blank page. Required:
  • Name — short and lowercase, like competitive-brief.
  • Description — when to use this playbook, and when not to. Monnet reads this to decide whether it applies, so the “not to” half matters as much.
  • Document outline — the section headers and writing rules for the document Monnet will produce.
Under Advanced:
  • Summary template — e.g. 🚀 Launch review of {feature}.
  • Before drafting — what Monnet should know or check first.
  • Typical plan — who gets looped in, to do what, in what order.
  • Other rules — facilitation style, exit criteria, anything else.
The form assembles these into a document you can keep editing as free text afterwards.
Monnet won’t always stop to confirm before drafting. When a playbook clearly fits what you asked for, it drafts and shows you the result.

​
Integrations

Connect Slack and Microsoft Teams, listen for new work in Notion, and connect tools Monnet can act on while it facilitates. See the Integrations section.

​
Policies and context

Your workspace’s standing rules — how the team works, what it prioritizes, who approves what — live on a page in the company brain named after your workspace. Supporting documents go in the brain’s Sources tab.
Policies used to be a MONNET.md field in a Context settings tab, alongside MEMORY.md and workspace files. All three moved into the brain: policies became a page, memory became the brain itself, and files became sources. The Context tab is gone.