# Put your brand on the sign-in code screens

Add your logo, accent color, a heading and a line of your own to the two-factor code screen and the setup screen with BetterShield Ultra.

After the password, BetterShield shows screens of its own: the code screen that asks for the **Authentication code**, and, when a [sign-in policy](/docs/sign-in-policies/) sends someone to set up two-factor, the setup screen. On **BetterShield › Ultra › Sign-in screens**, part of BetterShield Ultra, the card **The code and set-up screens** dresses both with your logo, an accent color and a line of your own. The WordPress sign-in form before them is left as it is.

## The options

| Option | What it does | Default |
|---|---|---|
| **Logo** | **Choose an image** picks one from the Media Library (**Replace** once one is set, **Remove** to clear it), or paste an image address into **Or paste an address**. Square works best, up to about 84 pixels tall. It takes the place of the WordPress mark at the top. | Empty: the WordPress mark |
| **Accent color** | **Choose a color** opens a picker, and **Clear** empties it. It colors the button, the focus ring around the code field, and the links under the form when pointed at. | Empty: the WordPress blue |
| **Heading above the form** | A short line above the form, up to 80 characters. | Empty |
| **A line under it** | A sentence under the heading, up to 200 characters. | Empty |

Press **Save** to apply. A field left empty keeps the WordPress look for that part, so you can set just a logo. **Remove** and **Clear** change only the draft until you save.

## Preview

**Preview**, beside the fields, draws the code screen with your choices as you type: the logo, your heading and line, the card that asks for the code, and the button in your accent color. These screens only appear partway through a sign-in, so the preview is a drawing of the screen rather than the live page. It always shows the light look, as the sign-in screens have no dark one.

## Readable colors

If white text on your accent color would reach less than a 4.5 to 1 contrast ratio, the field says what ratio it reaches. The color still works, but some people will struggle to read the button. A darker shade of the same color usually clears it.

## Who sees these screens

- Anyone with two-factor on, after their password, on the code screen. With [trusted devices](/docs/trusted-devices/) on, that screen also carries the checkbox to trust the browser.
- Anyone a two-factor policy sends to set it up, on the setup screen and the backup codes after it.

People who sign in with a passkey that counts as both factors, or from a browser they trusted, skip the code screen, so they do not see it.

## Where else it shows

The [client report](/docs/client-report/) uses the same logo and accent color, so the report a client receives and the screens they sign in through look like one thing.

## Good to know

- The logo is loaded by each person’s browser from the address saved, so it must be an http or https address the browser can reach.
- On multisite, each site sets its own.
- With **Ask for my password before an action that removes a protection** on (**Settings › General**), saving asks for your password.

## Related

- [Sign-in policies](/docs/sign-in-policies/)
- [Trusted devices](/docs/trusted-devices/)
- [Client report](/docs/client-report/)
- [Two-factor and passkeys](/docs/two-factor-and-passkeys/)