Skip to main content
A workspace is the top-level container for everything in Marble. Each workspace holds its own posts, media, authors, categories, tags, custom fields, API keys, and team members — fully isolated from every other workspace.
Think of a workspace as a single project: a personal blog, a company website, or a documentation site. If you manage multiple sites, create a separate workspace for each.

What lives in a workspace

Content

Posts, authors, categories, and tags — see the content model.

Media

Images and video uploaded to the workspace’s media library.

Custom fields

Workspace-specific metadata fields added to posts.

API keys

Keys that scope API access to this workspace’s content.

Workspaces and the API

A workspace is also the boundary for API access. Every API key belongs to a single workspace, so a key only ever returns content from that workspace. This keeps your projects cleanly separated — there’s no way for one site’s key to read another site’s posts. Create and manage keys from Settings → API Keys in your dashboard. See API Authentication to make your first request.

Team members and roles

Invite collaborators to a workspace from Settings → Members. Each member has a role that determines what they can do:
1

Open member settings

Go to your workspace dashboard and open Settings → Members.
2

Send an invite

Enter the person’s email and choose a role. They’ll receive an invitation to join.
3

They accept and start writing

Once accepted, they appear in the members list and can collaborate on content.
Workspace members and authors are related but distinct. A member is someone with dashboard access; an author is a byline attached to posts. See the content model for how they connect.

Plan seat limits

Every workspace plan includes a maximum number of members. Marble counts existing members and any pending invitations that haven’t been accepted yet against that cap, so a workspace on its last seat can’t queue up extra invites and have them all accepted later. New invitations are blocked once the cap is reached. Marble returns an error explaining which plan you’re on and how many seats it includes, and the Settings → Members page shows a banner while the workspace is at or over the cap. Owners see an upgrade prompt in the banner; admins see the same message without the upgrade action. Downgrades never remove existing members. If a workspace drops to a plan with fewer seats than it currently uses, everyone keeps their access — the workspace simply can’t add anyone new until it’s back under the cap, either by upgrading again or by removing members.

Usage alerts

Marble tracks each workspace’s monthly API request and webhook event usage against its plan limits. When a workspace crosses 75%, 90%, or 100% of a limit, Marble emails the workspace’s owner and admins. The email names the exact date the limit resets in UTC. On plans below the top tier it links to the pricing page so an owner can upgrade immediately. On the top plan there’s nowhere to upgrade to, so the email asks you to reply and the Marble team will raise your limit manually.
Each member can turn off Usage alerts for a workspace under Settings → Notifications. The preference is per-member and per-workspace, so opting out in one workspace doesn’t affect any other. Plain members never receive these alerts because they can’t change the plan or raise the limit.

Next steps

Content Model

How posts, authors, categories, and tags fit together.

API Keys

Create a key and make your first request.