Team spaces: your Markdown documents, shared
A team space brings your organization's documents together in Marko. Each organization has its own address, something like acme.marko.md. You sign in with your Marko account, find your spaces, and work on the same files as your colleagues without leaving the editor.
One address per organization
Your team connects to its own space, not a generic service. The address stands for the organization; the documents, teams and permissions live behind it. You open Marko, pick your space from the list, and your shared documents sit next to your local files.
Nothing else changes: you keep plain Markdown files. A shared document exports to PDF or comes back as .md, like any other.
Teams and sub-teams
A space is organized into teams and sub-teams. Belonging to a team gives access to its documents and those of its sub-teams, never to neighboring teams. Each person has a role on a document: read, comment or edit. The space administration decides who sees what.
| Role | What it allows |
|---|---|
| Read | Open and read the document, export it |
| Comment | Read and leave comments, without changing the text |
| Edit | Change the document and propose edits |
Joining a space
- You receive an invitation at your organization's address.
- You open the link: Marko opens on that space.
- You sign in with your Marko account, on the verified address the invitation reached.
- The space appears in Marko, with its documents and teams.
An invitation is tied to the address it was sent to. A link forwarded to someone else grants nothing: each person joins with their own verified address.
Your AI agents on the space's documents
Claude and Codex go through Marko on your Mac to read and edit the documents of the space you are connected to, within your permissions. ChatGPT, which only talks to an online service, uses the space's address. In every case the agent acts on behalf of the signed-in person and never goes beyond what that person is allowed to do.
A space opens by signing in. Team spaces are a feature of the app, not a second piece of software. You install Marko once; you work locally, and you unlock sharing by connecting to your space.
What stays the same
A team document is a Markdown document. You read and edit it in the same editor, export it to PDF, keep a .md copy. The AI assistant works the same way, on the passage you hand it, with your approval before it writes.
Frequently asked questions
How do I join my organization's space?
You open the invitation link sent to your address, Marko opens on the space, and you sign in with your Marko account. The invitation is tied to the verified address that received it.
Does a team document stay a plain Markdown file?
Yes. You export it to PDF or get the .md back like any document, and your colleagues reopen it in the editor of their choice.
Who can see and edit a document?
Each person has a role per document: read, comment or edit. Belonging to a team opens that team's documents and those of its sub-teams, never neighboring teams.
Can my AI agents work on the space's documents?
Yes, within your permissions. Claude and Codex go through Marko on your Mac; ChatGPT uses the space's address. The agent acts on behalf of the signed-in person.
See it on your document. Install Marko and try this on a real Markdown file, on your Mac.
Full 14-day trial, no account or credit card. See pricing