One workspace per client (or per program)
Structure workspaces around however your clients are organized — one per client, or grouped by retainer.
SolutionsFOR AGENCIES
Every client, isolated. One account to run them all.
Running client pSEO out of shared spreadsheets and one-off CMS instances doesn't scale past a handful of accounts. CMSHub workspaces are tenant-isolated by design, so an agency can operate many client sites from one account without client data, credentials, or content ever crossing workspace boundaries.
01 / ISOLATION YOU DON'T HAVE TO ENGINEER
Workspace-scoped, by construction
Every query is bound to the caller's workspace membership at the database level — there's no cross-tenant leakage to audit for, because the architecture doesn't allow it in the first place.
No shared credentials
Each workspace has its own members and API keys — a compromised client credential can't reach another client's data.
Per-site media, redirects, sitemaps
Assets, redirects, and sitemap generation are scoped per site, so a growing client roster doesn't become one tangled media library.
02 / CLIENT-APPROPRIATE ACCESS
Give clients exactly the access they should have
Per-collection, per-role permissions mean a client stakeholder can review and approve content without touching schema, billing, or another client's workspace.
Reviewer-only access
Grant a client contact find and approve permissions on content — nothing more — for sign-off workflows.
Consistent quality across accounts
The same six-check quality gate applies to every client site, so output quality doesn't depend on which account manager is watching.
One dashboard, every client
Switch between client workspaces from one account instead of juggling separate logins per site.
ONBOARD YOUR FIRST CLIENT
Spin up an isolated client workspace.
Create a workspace, invite a client reviewer with scoped access, and run your first quality-gated batch.