Opening proof path
SIRJ is loading the workspace, connector, or public page with the same proof path intact: ad spend, lead, booked job, invoice, paid.
See how SIRJ lets agencies manage client workspaces, visible-client rollups, role-scoped access, invitations, white-label branding, weekly recipients, and client reporting.
Buyer answers
Client workspaces turn SIRJ from one dashboard into an agency operating surface: portfolio metrics, scoped access, per-client branding, weekly recipients, and report handoff.
A client workspace is the scoped unit for a client's integrations, dashboard, Ask Data context, branding, weekly recipients, invitations, reports, and exports inside an agency account.
Agency teams can sell one platform to many clients without turning every client into the same data pool or the same public-facing report.
Follow the workspace proofThe agency overview aggregates only clients the current membership can access, then totals managed spend, attributed revenue, average client ROAS, and per-client health labels such as performing, needs attention, at risk, or setup needed.
Owners can spot portfolio risk quickly while analysts and viewers stay limited to the clients they are allowed to see.
Follow the workspace proofClient invitations are role-scoped, store token hashes instead of raw invite secrets, expire, and create scoped client memberships after acceptance. Owner-level permission is required before invite and client-management actions run.
Agencies can invite client viewers or analysts without giving them access to other client workspaces or agency administration.
Follow the workspace proofWorkspace settings carry branding and weekly recipients into the reporting path, so exports and scheduled insights can use the active client's display name, logo, accent color, footer notes, and recipient list.
The agency can deliver client-ready reports from the same workspace that owns the source data, access model, and dashboard context.
Follow the workspace proofAgency surfaces
The agency buyer needs both levels at once: the account-wide view that shows what needs attention, and the client workspace that owns the source data behind each answer.
What users see
The public page makes the product boundaries explicit: agency rollups are useful, but client-specific proof still belongs to a selected workspace.
| Surface | User sees | Source path |
|---|---|---|
| Agency overview | Total clients, managed spend, attributed revenue, average client ROAS, and a table of visible client performance states. | Agency overview reads client workspaces, membership permissions, dashboard configs, and derived client metrics before returning only visible clients. |
| Client workspace creation | An add-client form with owner-only controls and a plan-limit message before a new client workspace is saved. | Client creation requires manage-client permission, uses the active account scope, creates normalized branding, and is checked against billing client limits in runtime routes. |
| Client dashboard handoff | A client selector and dashboard context that keep source data, readiness, Ask Data answers, and reports tied to the selected workspace. | Dashboard state and request context resolve the active client before reading connections, events, dashboard configs, Ask Data queries, or report snapshots. |
| Team invitations | Invite forms, pending invitations, role labels, expiration dates, revoke actions, and current user access status. | Client access modules normalize email, limit invite roles, hash tokens, require manage-client permission, and create scoped client memberships on acceptance. |
| Branding and weekly recipients | White-label display name, logo, accent color, footer note, and weekly report recipients for the active client workspace. | Workspace branding and weekly recipients are saved on the client workspace, then reused by report rendering and weekly delivery workflows. |
Workspace workflow
The multi-client story is strongest when the setup path is simple and the evidence path stays narrow: create, connect, roll up, invite, and deliver.
| Step | What happens | User-visible proof |
|---|---|---|
| Create the client workspace | An owner creates a workspace under the active agency account with a client id, client name, optional branding, weekly recipients, and creation timestamp. | The account gains a named client workspace that can hold its own integrations, dashboard, reports, and client access. |
| Connect that client's sources | Each client workspace connects its own ad, call, CRM, booking, invoice, payment, and communication sources before dashboard cards or reports can use those records. | The dashboard and integration health views show source readiness for the selected client instead of an account-wide connector list. |
| Roll up only visible clients | Agency overview filters client workspaces through membership access before deriving totals, average ROAS, and per-client performance status. | Owners see the account portfolio, while scoped users see only the clients their membership permits. |
| Invite the right client users | Client invitations support analyst and viewer roles, expire, can be revoked, and create scoped client memberships when accepted. | A client can review the workspace or receive access without gaining permission to manage the agency account. |
| Deliver branded reporting | The active workspace's branding and weekly recipients flow into report snapshots, PDF exports, weekly delivery, and client-ready proof surfaces. | The report looks client-specific while its metrics still trace back to the workspace source records and dashboard context. |
Proof standards
The platform should make scale feel controlled: visible-client filters, matching dashboard scope, limited invite roles, and plan checks before workspace expansion.
Agency overview filters client workspaces through membership access before calculating totals, client rows, or performance status.
Client metrics are derived from dashboard configs that must match the same account id and client id as the workspace.
Client invitations only allow analyst or viewer roles, normalize email, store token hashes, and require pending, unexpired status before acceptance.
Client creation routes require manage-client permission and runtime billing checks before a new workspace is created.
FAQ
These answers explain how SIRJ handles multiple clients, role-scoped access, white-label reporting, and plan limits without making the product feel vague.
Yes. SIRJ agency accounts can create client workspaces, connect each client's own sources, review visible-client portfolio metrics, and open each client dashboard separately.
No. Client memberships are scoped to the accepted client workspace, and agency overview filters clients through the current user's membership before showing rollup rows.
Yes. Workspace branding can carry display name, logo, accent color, and footer notes into report rendering while keeping the metrics tied to the same client scope.
Public plans are framed around client workspace volume and reporting depth, and runtime routes check plan limits before creating additional client workspaces.
Ready when the numbers need to hold up
Open the demo to see agency rollups, client dashboards, source health, and report handoff in the same product shell.