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 handles client branding, white-label dashboard mode, branded report exports, scoped invitations, and source-backed reporting under a client brand.
Buyer questions
White-label reporting should reassure both sides of the review: the agency gets a polished client handoff, and the client still gets the source path behind the claim.
White-label reporting changes the client-facing presentation layer: display name, logo URL, accent color, footer note, dashboard brand node, and branded report snapshot output. It does not change how metrics are computed.
Agencies can present the work under the client brand without letting design settings change the revenue evidence behind the report.
Follow the proof pathYes. A viewer membership can open a client-focused portal view with simplified navigation, while the account and client access checks still decide which workspace, dashboard, reports, and team controls are available.
A client reviewer can get the focused report experience they expect without gaining the agency-wide controls or other client workspaces behind it.
Follow the proof pathYes. Report export captures client branding inside the same report snapshot that holds date range, dashboard metrics, cards, insights, recommendations, source breakdown, campaign rows, and generated timestamp.
The exported report can look client-specific while still answering where the spend, lead, revenue, ROAS, and recommendation rows came from.
Follow the proof pathBranding belongs to the client workspace. Runtime context resolves the active account and client before reading branding, dashboard state, report snapshots, invitations, recipients, exports, or notification rows.
Client presentation can be customized without turning multiple clients into one shared reporting surface or one shared export history.
Follow the proof pathWhite-label surfaces
The public promise is narrow on purpose: SIRJ changes the client-facing presentation while preserving the same access boundary and evidence path used by dashboards, weekly insights, and exports.
What users see
These are the buyer-visible places where white-label reporting matters: workspace setup, client portal, branded export, weekly handoff, and invitation/access review.
| Surface | User sees | Source path |
|---|---|---|
| Client workspace branding | A workspace-level branding form for display name, logo URL, accent color, footer note, and the white-label toggle before client-facing outputs use those values. | Client workspace updates pass branding through createClientBranding, then save normalized brand metadata on the selected client workspace rather than a global account setting. |
| Client viewer portal | A simplified portal view with client-branded sidebar treatment, selected workspace context, reduced navigation, and access limited to the viewer's client membership. | Dashboard state separates portalMode from whiteLabel so client viewers get the right navigation boundary while branding only appears when the client workspace has enabled it. |
| Branded report export | A report title, logo area, brand accent, optional footer note, summary metrics, source breakdown, campaign rows, attention items, and recommendations in one export. | Report export reads the active client context, freezes the report snapshot with clientBranding, renders escaped report HTML, and hands that artifact to PDF output. |
| Weekly recipient handoff | Weekly recipients saved beside the same client workspace settings that control branded reporting, so delivery and presentation stay tied to the selected client. | Workspace weekly recipients and branding are stored with the client, then weekly delivery and report workflows use the active client context before sending or exporting. |
| Invitation and access boundary | Invite role labels, pending state, expiration, revoke controls, and accepted client memberships for the client workspace that owns the branded report. | Client invitations normalize email, store token hashes, limit roles, require manage-client permission, and create scoped memberships before the client can see portal or report surfaces. |
Brand settings
The brand profile is small and explicit: name, logo URL, accent color, footer note, and white-label mode. That keeps the presentation layer understandable before a report goes to a client.
| Brand field | Client impact | Validation |
|---|---|---|
| Display name | The client-facing portal and report can show the client's name instead of a default SIRJ label when the workspace has a saved brand profile. | Branding normalization requires a non-empty display name or a fallback client name before the value is allowed into report rendering. |
| Logo URL | Reports can include a client logo when the agency supplies a usable public asset URL for that client workspace. | Logo URLs must be absolute HTTP or HTTPS URLs, which keeps unsupported schemes out of report HTML and dashboard rendering. |
| Accent color | The client-facing portal and report can use a saved accent color for headings, dividers, and brand treatment without changing metric logic. | Accent colors are accepted only as six-digit hex values and are normalized before they are used in dashboard style variables or report CSS. |
| Footer note and toggle | A workspace can add a short footer note and decide whether the dashboard shell should render under the client brand. | Footer notes are treated as optional strings and the white-label setting is stored as a boolean, so branded mode is explicit instead of inferred from incomplete brand fields. |
Client-facing boundary
White-label reporting needs a clean boundary between the branded experience, the viewer role, the evidence included in the artifact, and the export history behind it.
| Area | User sees | Boundary |
|---|---|---|
| Viewer navigation | Client viewers see a focused portal experience instead of the full agency navigation, while analysts and owners keep their broader workspace controls. | Portal mode is derived from viewer membership, and client access modules still control account id, client id, accepted membership, and role before data is exposed. |
| Brand surface | Client-specific name, logo, accent color, and footer note appear on eligible portal and report surfaces when the workspace brand settings are enabled. | Brand settings are presentation metadata. They do not override source rows, metric calculations, report dates, dashboard scope, or supported-answer rules. |
| Evidence preserved | Branded reports still include source breakdowns, campaign performance, top performer context, attention items, recommendations, and generation timestamp. | Report snapshots preserve client scope and dashboard evidence first, then render branding into the artifact after the supporting metrics are already frozen. |
| Export history | Completed and failed exports can be reviewed with snapshot id, format, status, output reference, generated timestamp, byte length, and error message when applicable. | Export records stay scoped to the active account and client context, so branded deliverables remain tied to the same report history and audit path. |
Workflow
The workflow starts with the workspace, then moves through saved brand settings, invitations, portal presentation, and exportable proof.
| Step | What happens | Visible proof |
|---|---|---|
| Create the client workspace | The agency creates a client workspace under the active account, giving the client its own id, name, branding metadata, weekly recipients, integrations, invitations, reports, and exports. | The product can show one agency overview while each client keeps its own dashboard context and reporting settings. |
| Save the client brand | The workspace branding form saves display name, logo URL, accent color, footer note, and white-label preference after normalizing those values through the shared branding module. | The same brand profile can feed portal presentation and report output without requiring separate manual report formatting. |
| Invite the right reviewers | The agency invites client analysts or viewers with scoped invitations, expiration, revoke controls, token hashing, and accepted memberships tied to the selected client workspace. | A client can review the portal or report surfaces without receiving owner-level account controls or access to other clients. |
| Render the branded portal | When a client viewer enters the workspace, portal mode reduces navigation and the white-label toggle decides whether the saved client brand appears in the dashboard shell. | The client sees a focused reporting experience while the agency keeps the same underlying dashboard, source health, reports, and client scope. |
| Export the proof package | A report export freezes the dashboard metrics, recommendations, date range, client scope, and branding into a snapshot before rendering the report HTML and PDF output. | The exported report carries the client brand and still shows source-backed rows that can be checked after the review meeting. |
Proof standards
The strongest white-label promise is not that the report looks custom. It is that the custom look does not hide scope, source, export status, or missing evidence.
SIRJ normalizes branding as presentation metadata, then report snapshots keep date range, source metrics, recommendations, account scope, and client scope as separate evidence fields.
Request context resolves the active account and client first, and client access checks govern invitations, memberships, dashboard state, report snapshots, and export actions.
Branding normalization requires non-empty display text, accepts only HTTP or HTTPS logo URLs, validates six-digit hex colors, and treats notes and toggles as explicit fields.
PDF export stores request and result records with snapshot id, scope metadata, output reference, byte length, status, error, and audit information before the artifact is treated as complete.
FAQ
The FAQ separates presentation from evidence so a buyer can understand what branding changes before they hand a report to a client.
Yes. Agencies can save client workspace branding for display name, logo URL, accent color, footer note, and white-label mode, then use that branding in reports and eligible client-facing workspace surfaces.
No. White-label mode changes presentation. Attribution metrics, dashboard cards, report snapshots, source rows, recommendations, and supported-answer rules still come from the scoped data path.
No. Client access is scoped through account membership, client membership, role checks, and accepted invitations before the viewer can see portal, dashboard, report, export, or team surfaces.
Yes. Branded reports still rely on report snapshot evidence and should keep missing campaign rows, unavailable source breakdowns, setup gaps, and unsupported recommendations visible when the data does not support a claim.
Ready when the numbers need to hold up
Start from the client workspace, preview the sample report, and keep every export tied to scoped source proof.