Configure white-label controls

Set agency brand defaults for client-facing reports and portals while preserving WebRiskOps internal workflow boundaries.

Agencies and account owners

Feature availability

Product, package, provider and deployment boundaries for this page.

Available from
Current documentation
Deployment modes
cloud

Product screenshots

Current customer-safe screenshots are generated from the application so examples do not drift from the product.

Generated customer-safe screenshot of the WebRiskOps agency white-label report branding controls.

Before you update brand controls

White-label controls apply agency branding to eligible client-facing surfaces without changing the underlying workflow ownership. Use this page when an agency needs report and portal presentation to match an approved agency brand before sharing client links. Branding affects presentation only. It does not change scan evidence, severity, remediation recommendations, billing ownership or internal WebRiskOps diagnostics. White-label branding is a resale boundary, not a product ownership transfer. It does not authorize reselling WebRiskOps as a separate scanner, certification product or support desk, and client-facing wording must not imply that the agency independently performed automated evidence capture outside WebRiskOps.

Set report branding

Follow the path `Agency → Agency workspaces → Report brand → Public reports → Exports`.

  1. Open /agency and find the agency workspace that owns the client reports. Result: the workspace shows branding badges, plan state and report sharing controls before you change presentation.
  2. In Report brand, enter the agency or approved client-facing brand name. Result: report and portal surfaces have a readable display name instead of a blank or internal account name.
  3. In Logo URL, enter an approved HTTPS logo asset. Result: WebRiskOps can render the logo on eligible public report and export surfaces without storing an unsafe upload.
  4. Add Report footer text that explains who prepared the report. Result: exported or shared reports carry the agency delivery context without changing evidence or severity.
  5. Turn on Enable white-label report branding, Use branding on public reports and Use branding on exports only for approved client-facing surfaces. Result: branding appears where allowed while internal diagnostics and platform controls remain WebRiskOps-owned.
  6. Click Save branding. Result: the agency workspace shows updated Branding enabled, Public on and Export on states before report links are shared.

Verify client-facing surfaces

After saving, open the report or portal link you plan to send and confirm the visible brand name, logo and footer are legible. If the public report or export still shows default branding, return to /agency and confirm the public or export toggle is enabled.

Continue to report sharing

After the brand controls are correct, continue to [Share client reports](/docs/accounts/share-client-reports) so the right public token and client-safe links are enabled. If the client workspace is missing or wrong, return to [Manage client accounts](/docs/accounts/manage-client-accounts) before sharing.

Availability boundaries

White-label controls depend on agency eligibility, plan state and valid brand assets.

  • Agency eligibility required means direct client accounts cannot manage white-label report controls.
  • Plan state unavailable means branding controls may be read-only until the Agency Plan supports them.
  • Invalid logo URL means the logo will not render on reports until the asset is reachable and approved.
  • Public report toggle off means shared public links keep default presentation even if internal brand defaults are saved.
  • Evidence unchanged means branding never edits findings, severity, confidence, screenshots or legal boundary wording.
  • Resale boundary means white-label output can present an approved delivery brand, but it cannot relabel WebRiskOps as a separate certification, scanner or managed support service.

Related documentation

Was this page helpful?

Feedback goes into the product documentation review queue.