Workspaces

A workspace is the top level of organization in MDflow. Keep separate workspaces for different projects or areas of life — Work, Personal, a side project — so unrelated content never mixes.

Workspaces are available on every plan, with no limit on how many you create.

What a workspace contains

Each workspace has its own:

• folder tree,
• documents,
• search index,
• description,
• integrations (a GitHub or Google Drive connection is made per workspace).

Switching workspaces swaps the entire sidebar to that workspace's content.

Switching

Use the workspace switcher in the sidebar header. Your choice is remembered between visits, so you return to where you left off.

New accounts start with a ready-made default workspace, so there is nothing to set up before writing.

Creating and renaming

Create a workspace at any time from the switcher, and rename it later. Give it a description too — like folder descriptions, a workspace description is a retrieval signal for AI agents, helping them pick the right workspace for a topic.

Moving content between workspaces

You can move a folder — together with its documents and any subfolders — from one workspace to another.

This is a web app action. It is deliberately not available through the API or MCP server, where folder moves only reparent within the same workspace.

Deleting

Deleting a workspace removes it along with every folder and document inside it. This is not a soft delete and there is no trash.

The last remaining workspace cannot be deleted, so you can never end up with an account that has nowhere to write.

Export first if you are unsure — see 02 Exporting a Workspace.

Two deliberate exceptions to workspace scoping

Workspaces are a strong boundary in the UI, but two things cross it on purpose:

1. Collections are cross-workspace. A single collection can gather folders and documents from any of your workspaces. When you build one, you pick from across all of them, grouped by workspace. This is the point: how you file something and how you present it to a reader are different problems.

2. The API and MCP server are account-wide. Full-text search in the app is scoped to the active workspace, but a Personal Access Token can see every workspace in your account. There is no per-workspace token.

That second point deserves emphasis if you are connecting an AI agent:

A Personal Access Token is not scoped to one workspace. An agent you connect can read and write all of your workspaces, including private ones. Separating content into workspaces organizes your sidebar; it does not sandbox an agent.

If you want an agent to work in one area only, say so in its instructions — or keep genuinely sensitive material in encrypted documents, whose contents no token can read. See 01 Document Encryption.