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

# White-label contract branding

> Send contracts for signature under your own brand — your logo and colors on the signing experience.

On enterprise plans, contracts can be signed under **your** brand instead of Soundcheck's. Your logo and colors appear on the signing experience your clients and crew see, so the agreement feels like it comes straight from your company.

<Info>
  White-label contract branding is an **enterprise** capability and is provisioned by the Soundcheck team. [Contact support](mailto:support@soundcheck.live) to set it up for your organization.
</Info>

## How it works

E-signature runs on **SignWell**, which applies branding at the level of a SignWell *Application*. Soundcheck stores a per-organization SignWell Application for white-label customers, so:

* Each white-labeled organization gets its **own** SignWell Application carrying your logo and colors.
* Contracts that organization sends are dispatched through that Application, so the branding follows every signature request.
* Organizations without a white-label Application send through Soundcheck's default branding — nothing changes for them.

## Setting it up

Because branding lives in a SignWell Application, provisioning is done **with the Soundcheck team** — it isn't yet self-serve:

<Steps>
  <Step title="Request white-label">
    Reach out to support and confirm your organization is on a plan that includes white-label contracts.
  </Step>

  <Step title="Provide your brand assets">
    Share the logo and colors you want on the signing experience.
  </Step>

  <Step title="We provision your Application">
    Soundcheck sets up your dedicated SignWell Application and wires it to your organization.
  </Step>

  <Step title="Send branded contracts">
    From then on, every contract your organization sends carries your brand. Day-to-day, you send contracts exactly as described in the [contracts overview](/features/contracts/overview).
  </Step>
</Steps>

## Related

<CardGroup cols={2}>
  <Card title="Contracts & e-signatures" icon="file-signature" href="/features/contracts/overview">
    The day-to-day signing workflow.
  </Card>

  <Card title="Compare plans" icon="credit-card" href="/subscriptions/feature-comparison">
    What's included at each tier.
  </Card>
</CardGroup>