A ministry’s admin already says the ministry’s name everywhere, but it is not yet THEIRS: it draws their name as text, ships a plain tab icon, and wears whichever colour the theme came with. Four values change that. Nothing here is a secret — it all travels in the build, because the sign-in card has to draw a logo before anybody has signed in, which is too early to read anything from the database.
Open the tenant’s Console branding panel.
Give it a dark-rail logo and a sign-in logo.
Full web addresses. The rail is dark, so that one wants light artwork; the sign-in cards are light, so that one wants dark. Either can stand on its own.
Give it a square tab mark.
What shows in the browser tab. Leave it empty and the plain shipped icon stays — never a blank one.
Give it ONE accent colour, like #7b2d8e.
It tints whichever theme their staff picked, and the console works out on its own whether to draw dark or light text on top of it. One colour, never a palette.
Deploy the ministry.
The panel saves immediately, but the admin only wears it after the next deploy builds with it.
A ministry with no artwork needs nothing here. Its name drawn as text is a finished look, not a gap — do not chase a logo to close this.
Branding is never inherited. A second-tier customer carries its own or draws its own name; it will not borrow its parent’s logo, on purpose.