Key concepts

Understanding the core model makes every other guide easier to follow. This page explains the four foundational concepts you’ll encounter throughout the platform.

Workspaces

A workspace is the top-level container for your organization. It holds all projects, members, settings, and billing information. Every user belongs to at least one workspace, and each workspace operates independently with its own configuration and data.

Workspaces are identified by a unique slug used in URLs and API calls.

Projects

Projects are the primary unit of work within a workspace. Each project has its own members, settings, and data. You can create as many projects as you need, and the same user can belong to multiple projects with different roles in each.

Note

Project-level role overrides take precedence over workspace-level roles. A user who is a Viewer at the workspace level can be granted Admin access on a specific project.

Members and roles

Every workspace member is assigned a role that controls what they can see and do:

Role	Description
Admin	Full access to workspace settings, billing, and all projects. Can invite and remove members.
Member	Can create and manage projects they belong to. Cannot access billing or workspace-level settings.
Viewer	Read-only access to projects they are added to. Cannot create or modify content.

Custom roles with granular permissions are available on higher-tier plans. See roles and permissions for details.

API credentials

API keys allow external tools and services to interact with your workspace programmatically. Each key is scoped to a specific workspace and can be restricted to read-only or read-write access.

Treat API keys as secrets—rotate them immediately if they are exposed. See the API reference for authentication details and endpoint documentation.