--- title: Branding description: Making every screen look like your product. --- import Callout from '../../../components/Callout.astro'; Set your brand once in the console, under **Customisation**. It applies everywhere your users see us: the SDK components, the hosted pages, and every authentication email. ## What you set **A logo.** An https URL you host, so you can change it without us. A wide mark works better than a square icon: it sits above the form at a fixed height, so a tall logo shrinks to nothing. **One accent colour.** Not a palette. Hover, active and disabled states are derived from it, and contrast is our problem to solve rather than yours to guess at. **A radius, a font and a colour scheme.** ## Contrast is handled for you Your accent is adjusted server-side so it stays legible on both light and dark surfaces, and the corrected values are what every surface paints. A colour that is beautiful on white can be invisible on near-black; a single stored hex would make one of the two unreadable. The text **on** your accent is chosen the same way, so a pale yellow brand gets dark text on its buttons rather than white. This is computed once, on the server. The console preview, the hosted pages and the SDK components all read the same resolved values. Three consumers running their own contrast rule is three chances to disagree, and the disagreement is invisible until somebody screenshots a button nobody can see. ## Your name under the logo By default your app's name prints under your logo. If your logo is already a wordmark, turn that off, or your name appears twice. With no logo the name always shows: it is then the whole identity, and a card with no identity at all is worse than either. ## The ZevAuth badge "Secured by ZevAuth" appears under every card. Removing it is a paid feature, and the decision is made on the server. A client cannot turn it off. Development always shows it, on every plan, so you never design against a screen production will not give you.