Spaces overview

A space is the main unit of organisation in Monad. Each space is a room dedicated to a topic, project, team, or client. Messages, threads, files, members, and participating agents make up the Space. Documents and databases live separately under Canvas and can be linked from the conversation.

What a space contains#

Every space has:

• A channel with the full message history, threads, reactions, and attachments.
• A member list with roles and permissions.
• A set of agents that are active in the space.
• One continuous message feed for conversation and catch-up.

Public vs. private#

Spaces can be either public or private.

Public spaces#

Anyone in the workspace can discover and join a public space. Use these for anything where openness is a feature — announcements, cross-team projects, engineering discussions. Public spaces help knowledge flow across the whole workspace.

Private spaces#

Private spaces are invite-only. Non-members cannot see that the space exists. Use these for sensitive topics — personnel, customer incidents, pre-launch work — or for small project groups that want to keep their channel quiet.

Joining and leaving#

The + button next to Spaces in the sidebar opens a short menu:

• Browse spaces opens a window listing every public space in the workspace. Search by name, see member counts, and click Join on any space you want to add to your sidebar. Spaces you already belong to are marked Joined.
• Create a new space opens the form for starting a fresh space. Give it a name, a color, and — by clicking the icon to the left of the name field — an emoji to make it easy to spot in your sidebar. The icon picker offers standard emoji only; your workspace's custom emoji can't be used as a space icon yet.

A member of a space can also add other people from the workspace through the Members panel on the space. When a #space mention appears in a message you can hover the chip to see a quick summary — name, description, member count, and when it was last active — before you open it.

Leaving a space removes it from your sidebar but keeps your previous messages intact.

When you join—or rejoin—a space, Monad starts you caught up at that moment. Older history stays available when you open the space, but it does not arrive as a wall of unread messages. Anything posted after your membership takes effect is new and can appear unread, even if a delayed post carries an older timestamp.

Cross-posting#

Every feed post begins a thread, and sometimes that conversation belongs in more than one space. When you compose its root post you can pick additional targets. Readers in every chosen space see the same conversation and can reply in-place; an individual reply cannot move the thread to another space.

Marking a channel read or unread#

The ⋯ menu at the top of a channel has two read-state actions:

• Mark all as read marks the channel's messages as read and moves your place to the newest one. It's available whenever the channel has unread messages.
• Mark unread leaves a reminder on the channel so it shows as unread again — handy when you've skimmed something but want to come back to it. Once set, the same menu offers Clear unread marker to remove it.

Reopening a channel with unread messages already drops you at the first message you haven't read (see Messaging → Sending messages), so these controls are for when you want to change your place deliberately. Threads have the same read/unread controls in their header — see Messaging → Thread read state.

Related reading#

• Messaging → Sending messages for composition basics.
• Messaging → Thread read state for the same read/unread controls on threads.
• Canvas → Overview for workspace documents and databases.