> ## Documentation Index
> Fetch the complete documentation index at: https://docs.didit.me/llms.txt
> Use this file to discover all available pages before exploring further.

# Branded Sign-In Pages, Sign-In Emails and Custom Auth Domain

> Make Didit's hosted sign-in pages and emails yours: your brand, page texts in five languages, terms and privacy links, and your own sign-in domain.

Didit Authentication's hosted sign-in pages and sign-in emails use your brand, the same brand as your verification flow.
You set the page texts and legal links for Authentication, and you can move sign-in to your own domain, such as `auth.example.com`.

Manage it in the console under **Authentication > Branding and emails**, which shows a live preview of the hosted sign-in page in light and dark.

![The Branding and emails page in the Didit Business Console for a sandbox application, with the brand from Customization, the page texts and a preview of the hosted page](https://mintcdn.com/didit-0f962782/RpqZjIB1GnUPdMTN/images/authentication/console-branding.png?fit=max\&auto=format\&n=RpqZjIB1GnUPdMTN\&q=85\&s=9653e0d5b5556cec809139cfa6eaf055)

Authentication > Branding and emails, with a preview of the hosted page.

## Your brand

The logo, brand color, background, corner radius and font come from your application's **Customization** settings in the console, and the hosted pages and emails follow them.
Choose **Edit in Customization** to change them: one change updates the verification flow and the sign-in pages together.

* The pages follow the person's device in light or dark mode, and the brand color is adapted for dark backgrounds.
* The pages show your application's name.
* On the Free plan, the hosted pages show a **Secured by Didit** badge.

![Didit's hosted sign-in page for a sandbox application in light and dark mode, with a passkey button and email and password fields](https://mintcdn.com/didit-0f962782/RpqZjIB1GnUPdMTN/images/authentication/hosted-sign-in-light-dark.png?fit=max\&auto=format\&n=RpqZjIB1GnUPdMTN\&q=85\&s=835219dfc253b7bfcb830255aff8ff93)

The hosted sign-in page follows the person's device in light or dark mode.

## Page texts and legal links

| Field | Limit | Where it shows |
| - | - | - |
| **Sign-in title** | 120 characters | The heading of the sign-in page. |
| **Subtitle** | 160 characters | The line under the heading. |
| **Sign-up title** | 120 characters | The heading of the sign-up page. |
| **Terms of service URL** | 500 characters | A link on the pages. When set, the sign-up form asks the person to accept your terms. |
| **Privacy policy URL** | 500 characters | A link on the pages, next to your terms. |

The hosted pages are translated into English, Spanish, French, German and Japanese, and pick the language from the person's browser, or from `ui_locales` on the sign-in URL.
Set your own texts per language: a language without your text keeps Didit's translated default.

By API, `PATCH branding/` on the [Authentication management API](https://docs.didit.me/authentication/set-up-by-api.md) sets the same fields:

```bash theme={null}
curl --fail-with-body --request PATCH "${MANAGEMENT_BASE}branding/" \
  -H "x-api-key: $DIDIT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "texts": {
      "en": {"sign_in_title": "Welcome back", "subtitle": "Sign in to manage your account.", "sign_up_title": "Open your account"},
      "es": {"sign_in_title": "Hola de nuevo"}
    },
    "terms_url": "https://example.com/legal/terms",
    "privacy_url": "https://example.com/legal/privacy"
  }'
```

A text you send empty goes back to the default.

## Sign-in emails

The emails view of **Branding and emails** lists the sign-in emails of your application, with a preview of each and **Send a test**:

| Email | Sent when |
| - | - |
| Email code | A person signs in or signs up with an email code. |
| Magic link | A person asks for a sign-in link. |
| Password reset | A person starts [forgot password](https://docs.didit.me/authentication/sign-in-methods.md#forgot-and-reset-password). |
| New device sign-in | A person signs in from a new device. |
| Invitation | You invite a person to sign up, with the `invited` sign-up policy. |
| Organization invitation | You invite a person to one of your [organizations](https://docs.didit.me/authentication/organizations.md#invitations). |
| Agent approved, Agent access ended | A person's [AI agent](https://docs.didit.me/authentication/agent-access.md) gets or loses access. |

Each email is marked **On** or **Off** for your application.
Emails are sent from your verified email domain when you set one up in Customization, and from `Didit <no-reply@didit.me>` otherwise.

## Custom domain

By default, your application signs people in on `https://<slug>.auth.didit.me`.
A custom domain moves the hosted pages, the runtime API and the token issuer to a subdomain of your own, such as `auth.example.com`.
Custom domains are for live applications: a sandbox application always signs people in on its Didit domain.

> [!WARNING]
>
> Passkeys belong to the domain people sign in on.
> Activating a custom domain means existing passkeys must be enrolled again, so add your domain before people start adding passkeys.

### Set it up

1. Under **Custom domain**, enter **Your domain**, for example `auth.example.com`, and choose **Add domain**. Use a subdomain: a CNAME cannot sit at the root of your domain.
2. Create the DNS record the console shows: a `CNAME` from your domain to your application's Didit host.
3. Choose **Check DNS now**. A new record can take up to an hour to show. Once Didit finds it, it issues a certificate for your domain, which renews on its own.
4. When the domain shows **Verified**, choose **Use this domain** to make it your application's sign-in origin.

| Status | Meaning |
| - | - |
| Waiting for DNS | Didit has not found the `CNAME` record yet. |
| Issuing certificate | The record is there, and the certificate is being issued. |
| Verified | Your domain serves the hosted pages. It is not your sign-in origin until you activate it. |
| Active | Your domain is the sign-in origin and the issuer. |
| Not found | The check failed. Fix the record and check again. |

By API, `PUT domain/` with `{"domain": "auth.example.com"}` adds it, `POST domain/verify/` checks it, `POST domain/activate/` activates it and `DELETE domain/` removes it.

### What changes when you activate it

* **The issuer.** New tokens name your domain in `iss`, and discovery and the JWKS move to it. Update the issuer your backend checks, or accept both issuers until older tokens expire. See [tokens and JWKS](https://docs.didit.me/authentication/tokens-and-jwks.md).
* **The publishable key.** It encodes the issuer, so it changes: copy the new key from **Authentication > Developers** into your app.
* **Sessions and tokens** under the old domain end within 5 minutes.
* **Passkeys** must be enrolled again on the new domain.
* **Redirect URLs, settings and the people who signed up** stay the same.

Keep the publishable key in one setting of your app, so the switch is one change.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.