White-Label Branding: Firm Name and Accent Colour

A firm that runs benchmarks on Quartyl has two identities available to it: the platform’s (Quartyl) and its own. The white label capability puts the firm’s identity into the workspace its team works in — the name in the sidebar, the accent colour on the chrome. It does not re-brand the generated deliverables: the Word, PDF and Excel outputs are rendered from the platform’s own brand tokens. This page is what the feature unlocks, where it is configured, where the brand flows, and exactly what stays platform-branded.

What the feature unlocks

White-label branding is a plan-level entitlement, not a per-user setting:

Plan feature: This capability requires the white_label plan feature (see Plan Features). Without it, the branding configuration is not available and the workspace carries the platform identity.

With the feature held, the Firm Admin can set two things for the firm:

• The brand name — up to 80 characters, the firm’s identity as it appears in place of “Quartyl”.
• The accent color — a 6-digit hex value (for example, #4f46e5), the firm’s brand color applied across the design tokens.

That is the whole of it: a name and a colour. There is no logo upload, no font selection and no report template to swap.

The backend enforces the entitlement on the write path: a patch to the branding fields from a tenant without the feature is rejected (403). Reading the current branding and resetting it to the platform default stay open to everyone.

Where it is configured

Firm Settings → the Branding tab (the tab itself exists only for firms that hold the feature — without it, there is no greyed-out entry point, only the other firm settings). The full configuration walkthrough is in Branding and White-Label.

The tab holds:

• Brand Name — the text field with a live character counter against the 80-character limit.
• Accent Color — a color input with a live preview of the initial mark, validated as a 6-digit hex.
• Save / Reset — save applies the brand to the firm; reset returns to the platform defaults.

Where the brand flows

Once saved, the branding travels with the firm, not the user:

• It rides on the identity endpoints. The firm’s brand_name and accent_color are delivered on the user’s profile (/users/me) and on the account-activation token validation — so the brand is present on the claim-account page before a member has signed in for the first time.
• The accent recolors the workspace. The accent color overrides the brand design tokens — the primary colors, the accent, the progress colors — by injecting a firm-level style, so the workspace’s chrome (active navigation, buttons, progress) carries the firm’s color, not a theme the user picks.
• The name replaces the platform’s in the sidebar header, the sign-in overlay and the claim-account page — the three surfaces a new member or a client-facing screen meets first.
• The reports are not part of this flow. Every generated deliverable — the Word master report, the branded PDF and the Excel workbook — renders its colours, fonts and identity line from the platform’s frozen report brand tokens (the same palette as the Quartyl web presence). The tenant’s brand name and accent colour never reach the generators. The white_label entry in the plan catalog reads “Branded reports and custom subdomain”; that describes the capability as catalogued for sale, not the implementation — there is no branded report surface and no subdomain feature today. What the Word master report carries as firm-supplied text is the engagement block typed into the final-document popup — prepared for / prepared by, the report date, the jurisdiction — which is engagement data set per study, not branding.

What stays platform-branded

The boundary is clean, and it is visible.

Without the feature:

• The workspace identity. The sidebar header, the sign-in overlay and the claim-account page carry the Quartyl name and the platform logo.
• The accent palette. The workspace runs on the platform’s default design tokens; there is no firm color to inject.

Always, feature or not:

• The deliverables. The Word master report’s cover identity line, the PDF’s running header and footer, and the workbook styling all come from the platform’s report brand tokens. The “Prepared by” field on the cover is engagement text the author types (it defaults to the platform identity when left blank) — it is a signature line, not a brand switch.
• Everything else — the product, the features, the reports themselves — is unchanged; branding touches workspace identity surfaces, nothing functional.

FAQ

Does branding change what is in the reports? No. Branding is workspace identity — the firm’s name and colour on the screens its team logs into. The reports are platform-branded either way; the chapters, the numbers, the appendices and the engagement block on the cover are the same with or without the feature.

How does a new team member see the brand before their first sign-in? From the account-activation validation response: the claim-account page renders the tenant’s brand name and accent from that payload, so the brand is present on the claim screen itself.

Can I change the brand after reports have been generated? The branding is a live firm setting — changing it changes the workspace immediately. It changes nothing on a generated artifact, because the artifact never carried the firm’s brand: the only thing to regenerate is the engagement detail on the cover (prepared by/for, date), which is typed per study.

Is there a per-user or per-study brand? No. Branding is a tenant-level setting: one brand per firm, applied firm-wide. Per-study identity on the report cover comes from the engagement details at generation time (prepared by/for, date), not from branding.