Organizations, Workspaces, Collections and Documents¶

What a project knows lives in nested things: an Organization, the Workspaces it owns, the Collections inside them, and the Documents inside those. The first one is the only one you may never meet, and that is by design.

Organization¶

An Organization owns Workspaces. It is what the plan is attached to, and it is where the seats that allow Users to write are counted.

Every account has one from the day it is created, and it stays out of sight while you are the only person in it. Working alone, you will not see the word anywhere, and nothing asks you to deal with it.

It shows up when it starts to make a difference, which is when someone else comes in. Open one of your Workspaces to another person and that Workspace moves into a shared Organization of yours, created at that first invitation. If you already share another Workspace with the same person, that existing Organization is used instead of opening a second one.

From then on Meridiaan names the Organization wherever an action depends on which one you are using, and stays quiet everywhere else. It never becomes a level you navigate through: you still open a Workspace, not an Organization that contains it.

What the first invitation does to a Workspace:

A few things follow from this:

• A shared Organization starts without a plan, and a Workspace under it cannot be written to until one is chosen. This is a stated condition, not a failure: whoever administers the Organization resolves it by picking a plan.
• It starts without a name, and shows its identifier until someone gives it one. The name is read by everyone inside it.
• One person can administer more than one, each with its own plan and its own bill.
• Being Admin of an Organization and Owner of a Workspace are two different things, at two different levels. Whenever one of the two words appears, it says what it is Admin of, or Owner of.

Who pays, what a seat is and who takes one are on the Plans and seats page.

Workspace¶

A Workspace is one project's knowledge base. It holds the Collections, the Users invited to it, and the connection an Agent uses to reach it: every Workspace has its own MCP endpoint, protected by a key of its own.

Access is granted per Workspace, not once for everything: you invite a person to the Workspace you want them in, with the role you want them to have. The other Workspaces of the same Organization stay invisible to them, personal ones included.

Collections¶

A Collection groups Documents of the same kind inside a Workspace. A Workspace about a piece of software may keep its decisions in one Collection, its open questions in another and its technical reference in a third.

Two things make a Collection more than a folder:

• A workflow, when it has one. A Collection can define the statuses its Documents move through, and a Document can only take one of those. A Collection without a workflow has no statuses at all.
• Instructions written by the Owner. They say how that Collection wants to be written, and the Agent receives them when it connects, so the rule travels with the Collection instead of living in a prompt someone has to remember.

The Owner decides which Collections exist, what they are called and whether they are exposed to Agents at all.

Documents¶

A Document is the unit of content: a title, a summary of what it is about, and the content itself. When its Collection defines a workflow, the Document also carries one of those statuses.

Documents can be archived when they stop being current, which keeps them readable without leaving them in the way, and a single Document can be kept out of what the Agents see.

The summary matters more than it looks: when an Agent lists a Collection it reads the titles and the summaries, and decides from those which Documents to open in full.

Who can do what¶

Changing the shape of a Workspace, which means creating, renaming, deleting a Collection or writing its instructions, is reserved to its Owner. Whoever collaborates works on the Documents inside the Collections that exist. The Roles page describes the three roles one by one.