Skip to main content
Settings access requires the admin or owner role. Users without these roles see an “Access denied” message.

​
General

The General tab shows read-only context for the active Studio target: The schema and project configuration remain code-first. To change content type definitions or sync schema metadata, update mdcms.config.ts in the host project and run mdcms schema sync from the CLI.

​
API Keys

API keys provide programmatic access to the MDCMS API for external integrations, CI/CD pipelines, and scripts. Manage them at Settings > API Keys.

​
Creating a key

Click Create API Key and configure: After creation, the full key is displayed once. Copy it immediately — it cannot be retrieved again. All keys use the mdcms_key_ prefix.

​
Available scopes

​
Managing keys

The API Keys table shows all keys with their label, key prefix, assigned scopes, context restrictions, creation date, expiration, and status (Active, Expired, or Revoked). To disable a key, click Revoke. Revoked keys cannot be reactivated — create a new one instead.

​
Users & Roles

Manage team access at Users in the sidebar. This page lets you list users, send invitations, update roles, and remove team members.

​
Inviting users

1

Click Invite User

Opens a dialog with email, role, and optional folder prefix fields.
2

Enter the email address

The invitee receives an email with a link to accept the invitation.
3

Select a role

Choose Admin, Editor, or Viewer. The Owner role cannot be assigned via invitation.
4

Set a folder prefix (optional)

For Editor and Viewer roles, you can restrict access to content under a specific path (e.g., content/blog). Leave empty for full project access.
5

Send

The invitation appears in the Pending Invitations section until accepted or revoked.

​
Role capabilities

Editors and Viewers can be scoped to a folder prefix. When a folder prefix is set (e.g., content/blog), the user can only access documents whose paths start with that prefix. This is useful for teams where different people own different content sections.Admins always have global scope and cannot be restricted to folders.

​
Managing existing users

From the user table, you can:
  • Edit role — Change a user’s role and folder prefix via the row action menu
  • Revoke sessions — Immediately invalidate all active sessions for a user
  • Remove user — Permanently remove the user from the project (with confirmation)
Owners cannot be removed. Ownership must be transferred first.

​
Schema Browser

The Schema Browser at /admin/schema provides a read-only view of all content types synced to the current project and environment. It shows:
  • Type name and directory path
  • Localization mode (Localized or Single locale)
  • Sync timestamp and schema hash
  • Field table for each type with:
    • Field name
    • Kind (string, number, boolean, enum, date, array, reference, object)
    • Required / Nullable status
    • Constraints (defaults, reference targets, enum options, validation checks)
The schema browser is useful for verifying that mdcms schema sync applied your latest type definitions correctly.
The schema is read-only in Studio. To change content type definitions, update your mdcms.config.ts file and run mdcms schema sync from the CLI.

​
Webhooks (post-MVP)

Webhook support will allow you to configure HTTP endpoints that receive notifications when content events occur.Webhook creation and editing open addressable settings pages at /admin/settings/webhooks/new and /admin/settings/webhooks/:id, so refreshing the browser or using back navigation keeps operators in the webhook workflow. The configuration table also includes a direct active/inactive toggle for quick enablement changes.Planned configuration per webhook:

​
Media Library

The Media page at /admin/media lists uploaded files for the current project and environment. Operators can search by filename, filter by media category, uploader, and upload date, sort by filename, size, or upload time, page through results, open assets, and copy asset URLs. Uploads, deletion, folders, tags, CDN transforms, and usage tracking remain outside this library view.