Client Manager
| Field | Value |
|---|---|
| Audience | public |
| Page type | reference |
| Area | sg-dashboard |
| Updated | 2026-05-14 |
How agencies manage multiple client accounts in SGEN — client linkage, portfolio routing, operational state.
Client Manager in SG-Dashboard is the agency-facing surface that lists every client account the agency administers. Where Site Manager handles sites within one account, Client Manager handles accounts across many clients. This page is the Reference definition of the Client Manager surface — relevant to agency operators and platform-eng partners who manage SGEN at the multi-account scope.
What is this for?
Read this page when you want the structural definition of multi-client management in SGEN — what the Client Manager surface lists, how routing into individual client accounts works, and what operational state surfaces at the multi-client scope.
Good use cases
- You are an agency operator running SGEN on behalf of multiple clients.
- You are scoping platform-eng partner workflows for managing client portfolios.
- You hit a "where do I see all my clients?" question and want the model laid out.
- You are designing internal SOPs for agency-style operations.
What NOT to use this for
- Per-account billing detail — open Billing Overview inside the relevant client account.
- Per-step procedures — open the relevant Guide.
- Per-release shipped change — open What's New or Changelog.
- Site-level work — open the admin inside the relevant client account / site.
How this connects to other features
- SG-Dashboard Overview — parent surface.
- Billing Overview — per-account billing surface (one click into a client account).
- Analytics — account-tier analytics rollup (per-account scope).
Definition
Client Manager in SG-Dashboard is the multi-client routing surface for agencies and partners. It lists every client account the operator administers, surfaces per-client operational state, and routes the operator into the relevant client account for deeper work.
The defining property is multi-client. Where Site Manager handles sites inside one account, Client Manager handles accounts across many clients.
Purpose
The purpose of this page is to define the Client Manager surface as a Reference layer rather than as a configuration walkthrough. It explains the multi-client routing model and the operational state that surfaces at the multi-client scope.
Scope
This page covers Client Manager at the Reference level.
The page covers:
- The multi-client list and per-client state.
- The routing model into per-client accounts.
- The boundary against per-account work (billing, sites, analytics).
- Per-step procedures — Guides.
- Per-account billing detail — Billing Overview inside the client account.
- Per-release shipped change — What's New or Changelog.
The multi-client list
Client Manager presents one entry per client account.
Per-client card
Each card carries the client identity, current operational state (sites count, subscription state, recent activity), and a routing action that opens the client's SG-Dashboard.
Operational state per client
The state shown per client is summary-level — current site count, subscription health (active / lapsed / pending), recent significant events. Detail lives one click into the client account.
Filter and search
Operators with many clients can filter by state (lapsed clients needing attention) or search by client identity for targeted retrieval.
Agency · Client Manager
Client accounts
Routing into per-client accounts
The routing action on each card opens the client's SG-Dashboard. From there, the operator works as if they were the client owner — Site Manager, Billing, Analytics, Reports — within that client's scope.
Per-client scope
Once routed in, every action stays scoped to that client. Switching clients means returning to Client Manager and routing into a different client.
Permission model
The agency operator's access to each client account is controlled by the per-client permission grant. Client Manager surfaces only the clients the operator has been granted access to.
Constraints and boundaries
Client Manager is a Reference area for the multi-client routing surface. It is not a substitute for per-account work or for per-customer pricing.
Use this Reference for:
- Understanding the multi-client portfolio model.
- Confirming the per-client state that surfaces at the agency tier.
- Reasoning about routing and permission scope.
- Per-account work — descend into the client's SG-Dashboard.
- Per-customer pricing — customer agreement.
- Per-step procedures — Guides.
Public boundary
This page is intentionally public-safe. It does not expose internal multi-account engine internals or protected operational identifiers.
Examples
Example 1 — Agency operator scans portfolio for action items
The agency operator opens Client Manager every morning, scans for clients in unhealthy state (renewal failed, lapsed). They route into the client account requiring action and resolve the issue inside that client's scope.
Example 2 — New client account joins the agency
A new client grants the agency operator access. The client appears in Client Manager. The operator routes in, completes the initial setup or onboarding inside the client's SG-Dashboard.
Example 3 — Stakeholder asks "how many clients are we running?"
The platform lead opens Client Manager, reads the count, provides the number with the per-state breakdown (active, attention-needed, recovery-in-progress).
Documentation guidance
Use this page as the structural definition for the Client Manager surface. Procedural detail belongs in Guides; per-release behavior change belongs in What's New or Changelog.
Reading order
Open this page when scoping agency-style operations or troubleshooting multi-client routing questions.
Related reading
- SG-Dashboard Overview — parent surface.
- Billing Overview — per-account billing surface.
- Analytics — account-tier analytics rollup.
Vocabulary cross-reference
- Client account is one customer's SGEN account.
- Multi-client portfolio is the set of client accounts the agency operator administers.
- Per-client state is the summary state surfaced at the multi-client level.
- Routing action is opening a client's SG-Dashboard from the Client Manager surface.
- Permission grant is the per-client access the operator was granted.
Maintenance discipline
When Client Manager behavior changes across releases (new per-client state field, new routing action, new permission model), update this Reference and log the change in Changelog.
Related reading
| Topic |
|---|
| SG-Dashboard |
| Billing Overview |
| Analytics |