admin/branding, inside the admin section of the
console.
What branding controls
The screen manages two values:
Everything the screen changes is presentation. It does not change
tenant, org, or trunk configuration, and it is not part of the
authentication flow — only the chrome around it.
Where each value is rendered
The screen describes its own scope as the product name and logo “shown on login, top bar & title”. In practice that is three surfaces:
Because the login page is one of the surfaces, branding is visible to
people who have not authenticated yet. Treat the product name and the
logo as public.
Scope: deployment-wide, not per-tenant
Branding is a property of the deployment, not of a tenant, org, or user. The screen sits behind the admin shell and describes itself as white-labelling “this deployment”, and it exposes a single product name and a single logo — there is no per-tenant variant on this screen. Every tenant served by that deployment therefore sees the same name and logo, including on the shared login page. If you need two different brands, you need two deployments.Both consoles render one implementation
The branding form itself lives in a shared package (agent-ui/screens/branding). Each console ships only a thin host
wrapper that supplies its own chrome — the admin navigation shell, the
page icon, and the header’s title and subtitle. The contact-centre
wrapper is the one shown above.
The practical consequence: the fields, validation, and behaviour of the
branding form are identical in both consoles. Only the surrounding
navigation differs. A screenshot from one console is an accurate guide
for the other.
Relationship to the shipped defaults
A deployment always has a name and a logo before you touch this screen — the ones compiled into the build, which is why an untouched console reads as TeleQuick. Saving branding values overrides that presentation for the deployment; it does not alter the build. Self-hosted deployments use the same screen. There is nothing to configure at the image or environment level to enable it: the branding values are set from the console, by an admin, after the deployment is running.Logo constraints and propagation
The console source that this page documents establishes that a logo is uploaded and where it is rendered. It does not establish:- accepted image formats, pixel dimensions, aspect ratio, or file size;
- where the uploaded image is stored or from what URL it is served;
- whether a session that is already open picks up a new name or logo immediately, on navigation, or only after a reload;
- whether a reset-to-shipped-defaults control exists.