# One login, forty client sites

> Client workspaces give every client their own content, roles and API keys, while your team keeps a single login.

- URL: https://vercel-example.notra.site/blog/client-workspaces
- Published: 2026-10-06
- Authors: Ines Varga, Kofi Mensah
- Tags: product

Most agencies we talk to run between 15 and 60 client sites. Until now, each one was a separate Quillstack project with its own users, so a developer who worked on twelve clients had twelve logins and twelve sets of API keys in a password manager.

Today we’re shipping **client workspaces**.

## What a workspace holds

A workspace is one client. It has its own:

- content models and entries
- roles, so the client’s marketing team can edit pages without seeing other clients
- API keys, scoped to that workspace only
- webhooks and preview URLs

Your agency sits above all of them. Your team signs in once and switches clients from the sidebar or with `Cmd+K`.

## Moving existing projects

Projects you already have become workspaces automatically. Nothing changes for the client: their users, keys and URLs keep working.

> **Note**
>
> Content models can now be shared across workspaces. Mark a model as **Agency template** and new workspaces start with it. Changes to the template show up as a suggested migration in each workspace, never as a silent edit.

## Billing

Workspaces are billed per agency, not per client. The Studio plan includes 25 workspaces, and each extra one is billed at the end of the month only if it had edits in that month. Archived clients cost nothing.

## Numbers from the beta

Eleven agencies tested workspaces since August. The median agency closed 31 browser tabs’ worth of separate projects and rotated 140 API keys into 9 scoped ones.
