Multi-Tenant Workspaces & Sites
Many clients, one dashboard
Run separate organisations for each client or internal unit. Each keeps its own sites, pages, and team members, and data stays separated between accounts. One login can cover a whole agency portfolio while permissions and dashboards follow the organisation you are in. Scale from a handful of properties to dozens without spreadsheets or per-site tooling.
Why it matters
Isolated data, clear roles, room to grow.
Organisations, not folders
Each workspace keeps its own sites, pages, billing, and members. Nothing from one organisation appears in another.
Built for portfolios
Add clients or internal units without redoing how permissions work. Watcher was built with separate workspaces from the start.
Least-privilege by design
Pair workspaces with Admin, Manager, and Viewer roles so auditors and clients stay read-only where appropriate.
Organisation → Site → Page
-
Organisation: billing, plan, team members.
-
Site: a domain with its own pages, budgets, and schedule.
-
Page: a monitored URL (auto-discovered or manual). One mental model for the whole portfolio.
No juggling separate accounts for every client.
Roles at a glance
These role permissions are the same on every plan.
| Role | Create / edit | View |
|---|---|---|
| Admin | Yes | Yes |
| Manager | Yes | Yes |
| Viewer | No | Yes |
Platform sysadmins bypass org scoping for support and operations.
Discovery & quota in context
Workspaces stay clean when page sets stay current: sitemap-first discovery and crawl fallback (detailed on Automated page discovery). Each organisation has plan-based API quota; usage is visible so you can right-size schedules (see API access & quota visibility).