Workspaces
updated
Everything in Meldoc lives inside a workspace — projects, documents, members, settings and assets. Most teams need just one; create a second only for a completely separate organization.
Create a workspace
In the sidebar, select the workspace name, then + Create workspace. Name it, choose a plan, and optionally invite your team and connect GitHub. The workspace exists once you name it and starts on Free; every later step can be skipped and done from settings.
Overview
The workspace Overview opens on the Start tab: search, your projects, what needs your attention and what changed recently. Other tabs hold the Glossary, Duplicate Radar and the asset library.
Settings
Admins open Settings in the sidebar:
- General — name, timezone, date format, glossary access, export, and agent instructions.
- Team, Integration Tokens, AI Provider, Audit Log, Webhooks, Plans & Billing.
- Danger zone — the Owner deletes the workspace here; every other member leaves it with Leave workspace. Leaving revokes the integration tokens you created in the workspace, and only an invite brings you back.
Agent instructions tell AI assistants connected over Meldoc MCP where things belong — for example, “contract facts live in the backend project, product intent in the product one”. They are advice, not permissions. Projects can add their own instructions on top.
Public page
Projects with Public access appear on your workspace’s public page. To change their order, select Edit public projects order on the projects list and drag them. Public content is also discoverable by AI assistants through LLMs.txt Protocol.
What’s next?
Projects — Create and configure projects.
Team — Invite your team and assign roles.