One organization, many workspaces — agency client model
How agencies use one RankWatch organization with a workspace per client for isolation, invites, and shared package limits.
Agencies typically run one RankWatch organization (billing and governance) and one workspace per client (projects, members, and data).
Organization (shared)
Owned by the agency account:
- Package, credits, and seats (limits apply across workspaces)
- Role packs and custom workspace roles
- Whitelabel domains, logos, and portal branding
- Organization email templates and delivery channels
Workspace (per client)
Each client workspace holds that client’s projects, tool jobs, reports, and member list. People are invited to a specific workspace; they only see projects in workspaces they belong to.
Recommended pattern: one workspace per client so invites, reporting, and data stay isolated. Internal specialists can be invited into many client workspaces; clients usually get a read-only role in their own workspace only.
Why this model
| Goal | How the model helps |
|---|---|
| Data isolation | Separate workspaces prevent client A from seeing client B projects |
| Clean invites | Invite clients only to their workspace |
| Shared billing | One package funds all client workspaces |
| White-label portal | Map branding / domain to the client workspace experience |