> For the complete documentation index, see [llms.txt](https://prehledne-navody.gitbook.io/prehledne-navody-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prehledne-navody.gitbook.io/prehledne-navody-docs/help-center/getting-started/whats-the-difference-between-a-workspace-and-a-project.md).

# What's the difference between a workspace and a project?

A **workspace** is your top-level organisational container — think of it as your company or team's home. Everything lives inside a workspace: members, billing, settings, and all your projects.

A **project** is where your actual work happens. Each project has its own content, permissions, and settings, but it always belongs to a workspace.

### Quick comparison

|             | Workspace                  | Project                  |
| ----------- | -------------------------- | ------------------------ |
| Contains    | Members, projects, billing | Content, pages, files    |
| Billing     | Per workspace              | Inherited from workspace |
| Permissions | Org-wide roles             | Project-level roles      |
| Limit       | 1 per account (Free)       | Unlimited                |

### When to create a new workspace vs. a new project

Create a **new project** when you're starting a distinct piece of work — a new product, a separate documentation site, or a team initiative. Projects are cheap and easy to manage.

Create a **new workspace** only when you need a completely separate billing and membership boundary — for example, an agency managing work for a different client, or a personal account kept separate from your employer.

{% hint style="warning" %}
Switching content between workspaces is not straightforward. If in doubt, start with a new project inside your existing workspace.
{% endhint %}

### Related articles

* Inviting team members to your workspace
* Setting up a custom domain