Branding and White-Label: Firm Name and Accent Color in the Workspace

White-label branding makes the workspace carry the firm’s identity instead of the platform’s: the firm’s name where the product name would be, and the firm’s accent color across the application shell. Two fields — name and accent — drive the whole effect, and its reach is the interface, not the deliverables.

The Branding tab

Plan feature: This capability requires the white_label plan feature (see Plan Features).

The Branding tab exists in Firm Settings only when the firm’s plan holds the white_label feature — without it, the tab is not shown and saving the branding block returns a 403 (the panel’s other tabs, its reads and its reset are not gated by white_label; the panel as a whole rides the separate firm_settings feature). The tab holds exactly two fields:

• Brand name — the firm’s display name, up to 80 characters. Empty means “use the platform brand (Quartyl)”.
• Accent color — a 6-digit hex code (for example #2563EB), validated on save. Empty means “use the platform palette”.

Where the brand shows

A configured brand runs through the application surface:

• The sidebar header — the brand name replaces the platform name at the top of the navigation.
• The sign-in overlay — the full-screen sign-in that covers the workspace carries the brand name and accent.
• The claim page — an invited member sees the firm’s brand on the claim-account page before their first sign-in: the activation flow returns the brand name and accent color to the invitee’s browser as part of validating the invitation token.
• The reports — where they do not show. The Word and PDF deliverables carry the platform’s house identity, not the firm’s. Their palette, type stacks and name lines come from one frozen token set in the report engine (services/reporting/report_engine/branding.py), which is deliberately the same for every tenant so the Word and PDF renderings can never drift apart. There is no per-firm logo, font, letterhead or report template, and white_label does not reach the deliverables. What the reports do record is who prepared them — the engagement details entered when the final document is generated, covered in the Word master report.

For unbranded firms, the three interface surfaces show the platform identity — branding is an overlay, not a fork — and the deliverables show the platform identity either way.

The accent token override

The accent color is not a single stylesheet value; it is a design-token override. When a brand accent is applied, the client injects a scoped style block (<style id="tpip-accent"> on :root) that redefines the brand tokens from the hex value:

• --color-primary — the base accent, plus --color-primary-hover and --color-primary-strong darkened from it and --color-primary-alpha-15 as a translucent step, so buttons, links and active states follow the brand;
• --color-accent — the accent used on indicators such as the seat-allocation ring;
• --color-progress — progress surfaces, so run progress and quota bars match the brand.

The applied accent and brand name are kept in browser storage and re-applied on load, so they survive a page reload and a logout, and the profile re-confirms them each session. They clear when the brand is reset or saved empty (an invalid hex falls back to the platform palette too), so an unbranded workspace never keeps a stale accent.

Resetting to platform branding

• Reset the panel. The Firm Settings reset (Firm Admin) restores the Branding block to its defaults — brand name and accent back to empty — and the workspace falls back to the platform identity. That action is guarded by firm_settings, not by white_label, so losing the branding feature does not lock a firm out of clearing its own branding.
• Clear the fields. Saving the Branding tab with both fields empty has the same effect: unset means “use the platform”.
• What a missing feature does. Without white_label, saving branding is refused (the change returns a 403) while reads and reset remain open — a firm that loses the feature keeps a working, unbranded workspace rather than a broken one.

The full configuration context — what else the panel holds and who may change it — is in Firm Settings: Tenant Configuration Overview.

FAQ

Do the Word and PDF reports come out in our brand? No. white_label covers the workspace surfaces listed above. The report engine renders every tenant’s deliverables from one frozen brand token set — palette, fonts, footer and copyright lines — so a rebrand of the workspace never changes a client-facing report.

Do I need to touch CSS to rebrand? No. The accent is a hex field; the derived tokens (hover, strong, progress) are computed from it automatically.

Does the brand change the product name in the URL or the API? No — branding is a presentation layer over the platform; routes, data and identifiers are unchanged.

If we lose the white-label feature, does the branding break? No. Reads and reset stay open; the firm simply cannot set new branding, and clearing the fields (or resetting) returns the platform identity cleanly.