# Other Settings

### Company Logo

You can upload your company logo to make the hosted onboarding experience feel consistent and familiar for your end-users.

This helps reassure users that they are in the correct flow and improves brand continuity throughout the journey.

**Recommended Guidelines**

* **Format:** PNG (recommended), JPG, or SVG
* **Background:** Transparent background is preferred
* **Aspect ratio:** Horizontal logo works best
* **Resolution:** At least 200px height for clarity on modern devices, but not more than 500px
* **Maximum File Size**: 800 KB

**Light & Dark Mode Support**

The onboarding experience supports both **light and dark modes**, depending on the user’s device settings.

> 💡 Tip\
> If your logo is dark and uses a transparent background, it may not be clearly visible in dark mode.
>
> To ensure good visibility:
>
> * Use a **light-colored or adaptable logo**, or
> * Provide a version that works well on both light and dark backgrounds.
> * Test your logo on both modes to make sure it works as expected.

<div><figure><img src="/files/zzM2JDFPFIwNeeaoy5KH" alt="" width="563"><figcaption></figcaption></figure> <figure><img src="/files/TqrZEpHoig8lLcKCeefh" alt="" width="563"><figcaption></figcaption></figure></div>

### Return URL

The **Return URL** is the page where the end-user is redirected after completing onboarding.

Use this when you want to send the user back to:

* your website
* your app landing page
* the next step in your journey

### Notification Email

You can configure a **Notification Email** so your team receives an email when an end-user completes onboarding.

This is useful for operations teams, support teams, or manual review teams that need immediate visibility into completed sessions.

The notification email can include session details such as:

* session ID
* workflow name
* timestamps
* onboarding channel

<figure><img src="/files/f8YaxBb5oBN3lvkvMtJq" alt="" width="375"><figcaption></figcaption></figure>

Notification emails are especially useful when your team wants operational visibility even if the main system integration is handled through a webhook.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.uqudo.com/docs/kyc/no-code-kyc/other-settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.