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

# Branding

Fiskil hosts the **consent authorization screens** and optional **consumer dashboard** on your behalf.
You can configure branding so customers interact with a trusted, familiar experience that reflects your organisation’s identity.

Branding is configured per instance in the [**Console → Settings → Branding**](https://console.fiskil.com/data-holder/settings/domains).

***

## What You Can Brand

You can edit the following elements for each instance:

* **Font** — choose typography that matches your brand.
* **Logos** — upload your organisation’s logo for use on consent flows and dashboards.
* **Brand Colors** — apply primary/secondary colors for buttons, highlights, and UI accents.
* **Business Identity Information** — display your organisation name and related identifiers.
* **Support Information** — provide customer support contact details (email, phone, link).
* **Policy Links** — link to your privacy policy, terms of service, or help center.
* …and more.

***

## Consent Screens

All users complete their consent through the **Fiskil-hosted consent flow**.
Branding ensures these screens feel consistent with your product experience.

The consent flow always displays:

* The **Data Recipient** requesting access
* The **scopes and datasets** requested
* The **duration** of access
* Your configured logo, font, and brand colors
* Any **support or policy links** you provide

***

## Consumer Dashboard (Optional)

If enabled, Fiskil provides an **end-user dashboard** where customers can:

* View their active consents
* Revoke consents at any time

Your branding applies here as well:

* Logo and display name
* Font and brand colors
* Custom domain

***

## Best Practices

* Clearly distinguish your **Staging** and **Production** branding to reduce chances of using the wrong instance.
* Use a **custom domain** for production instances (e.g., `consent.acme.com`).
* Provide clear, accessible **support information** and **policy links** to build trust.
* Use high-resolution assets for logos and icons to ensure accessibility.

***

## Related

* [Custom Domain](/docs/configure/custom-domains)
* [Consent](/docs/build/consents)
* [Instances](/docs/get-started/instances)