Workspaces

Share document-to-Markdown conversion credits, API tokens, and settings across your team with workspaces.

A workspace is the central unit of organization in Markdown Anything. Every account starts with a personal workspace, and you can create additional workspaces for teams or projects.

What Is a Workspace?

A workspace groups together:

  • Credits — All plan credits and overages are billed to the workspace, not individual users.
  • Conversions — Every conversion belongs to a workspace and counts against its credit balance.
  • API Tokens — Tokens are scoped to a workspace. A token created in Workspace A cannot access Workspace B's resources.
  • Members — Invite teammates to collaborate within the same workspace.
  • Settings — Preferences like Enhanced AI defaults, token optimization, and data retention are per-workspace.

The workspace is the billing entity. Your subscription, credit balance, and invoices are all tied to the workspace — not to your personal account.

Shared Credits

All members of a workspace draw from the same credit pool. When any member (or API token) performs a conversion, credits are deducted from the workspace balance.

This means:

  • A single subscription covers your entire team.
  • You can monitor total usage in one place.
  • Overage charges apply to the workspace as a whole.

Team Collaboration

Workspace owners can invite members by email. Invited users receive a notification and can accept or decline.

Invite a Member

Go to Settings > Workspace > Members and enter the email address of the person you want to invite.

Accept the Invitation

The invited user receives an email notification. They click the link to join the workspace.

Collaborate

Once joined, the member can perform conversions, view history, and use workspace API tokens.

Switching Workspaces

If you belong to multiple workspaces, you can switch between them from the workspace selector in the navigation. Your active workspace determines:

  • Which credit balance is used for conversions.
  • Which API tokens are visible in settings.
  • Which conversion history you see.

API Token Scoping

API tokens are created within a workspace and inherit that workspace's context.

  • Tokens are prefixed with mda_ for easy identification.
  • A token authenticates as the workspace, not as a user.
  • Rate limits are applied per-workspace based on the workspace's plan.

Treat API tokens like passwords. If a token is compromised, revoke it immediately from Settings > API Tokens.

Workspace Preferences

Each workspace can configure default behavior for conversions:

SettingDescription
Enhanced AIEnable by default for all conversions in this workspace.
Token OptimizationApply token optimization by default.
Data RetentionChoose whether to store converted markdown and metadata. When disabled, filenames are anonymized and content is not persisted.

These defaults can be overridden on a per-request basis via the API or dashboard.

Next Steps