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:| Role | Description |
|---|---|
| Owner | Full control of the workspace, including billing, deleting the workspace, and managing the logo and members. There is one owner per workspace. |
| Admin | Manage content and members, but cannot perform owner-only actions like deleting the workspace. |
| Member | Write, edit, and publish content within the workspace. |
Next steps
Content Model
How posts, authors, categories, and tags fit together.
API Keys
Create a key and make your first request.