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

# Customization

> Brand the widget: color, logo, and the copy the user sees.

A widget's look and wording are set in the dashboard when you create or edit it, under Customization. These settings travel with the widget's public key, so the same embed code always shows the branding you configured.

## Options

<ParamField path="brandColor" type="string">
  The accent color, applied to buttons and highlights. Also passed in the embed as `data-pruva-color` so the loading spinner matches before the widget has loaded its config.
</ParamField>

<ParamField path="logoUrl" type="string">
  A URL to your logo, shown in the widget header.
</ParamField>

<ParamField path="welcomeTitle" type="string">
  The heading on the opening screen.
</ParamField>

<ParamField path="welcomeText" type="string">
  The body copy on the opening screen, to set expectations before the user starts.
</ParamField>

<ParamField path="successTitle" type="string">
  The heading on the completion screen.
</ParamField>

<ParamField path="successText" type="string">
  The body copy shown once the check is done.
</ParamField>

<ParamField path="redirectUrl" type="string">
  A URL to send the user to after they finish, for example back into your onboarding flow.
</ParamField>

## Copy that reads well

The welcome and success screens are where a user decides whether to trust the flow. A few practices:

* Say what you are about to ask for on the welcome screen: a selfie, an ID, a NIN. A user who knows what is coming completes more often.
* Keep the success copy short and tell them what happens next, especially if you set a `redirectUrl`.
* Match the `brandColor` and `logoUrl` to your app so the widget feels like part of your product, not a detour out of it.

<Note>
  Changes to a widget's customization apply to every embed of that widget's public key at once, since the settings live with the widget, not in your page. You do not need to redeploy your site to change the copy or color.
</Note>


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