Short answers about brand names, logos, colours, portal titles, custom domain storage, powered-by badge removal, domain-shape validation, and what still needs DNS or TLS verification.
White Label & Branding is a shared add-on for tenant-facing brand settings. The verified module exposes branding settings, custom domain storage, landing template selection, and a hide-powered-by flag for client-facing branding workflows.
The verified branding response includes brand name, logo URL, logo initial, primary colour, portal title, custom domain, landing template, tenant slug, and hide-powered-by status. Admin users can update these fields when the White Label module is enabled.
The verified module stores a custom domain on tenant branding settings and returns it through the branding endpoint. Public copy should say custom-domain configuration is supported, while DNS records, routing, and certificate behaviour still need deployment-level verification.
The schema rejects clearly invalid custom-domain values: protocols, paths, trailing slashes, invalid hostname shape, single-label names, overly long labels, and domains longer than 253 characters. It does not prove DNS ownership or certificate readiness by itself.
Yes. The module description and branding response include hide_powered_by. Treat this as a client-facing branding setting, not as a claim that every email, invoice, or infrastructure touchpoint is fully white-labelled unless each surface has been verified.
No. White Label & Branding is a shared add-on priced at EUR 99/month. Businesses should verify DNS setup, TLS certificate behaviour, login links, portal emails, legal footer requirements, and brand-surface coverage before launch.