Hosted Signing Branding

Hosted document and packet links can carry your identity while keeping Korala visible as the signing provider. Signers see the same co-branded header in both flows:

Your logo or brand name appears above “Document signing powered by Korala.” The attribution opens the Korala homepage in a new tab, keeping the signing page open.

Configure your brand

Open Settings → General → Branding in the Korala dashboard. Set any of:

• Brand name: Korala also uses this name when your logo cannot load.
• Logo URL: Enter a public HTTPS image URL.
• Primary color: Enter a six-digit hex color such as #315C46.

Korala applies the primary color to signing actions and chooses black or white button text for contrast. If no branding is configured, hosted links keep the standard Korala appearance.

All hosted document links and signing packets from an organization use its saved brand. Korala resolves branding from organization settings, so signing URL parameters cannot change the displayed identity.

Korala continues to send these messages from its configured email domain. Custom domains and Certificates of Completion keep the standard Korala identity.

Logo behavior

Korala preserves the image’s aspect ratio and fits it within 144 × 28 pixels on desktop and mobile, without enlarging smaller images. The browser requests it without sending the signing page as a referrer. If the image is missing or unavailable, the brand name appears in its place and signing remains available.

Use a compact horizontal logo with enough contrast on a white background. PNG, JPEG, WebP, and SVG URLs work when the image host permits browser access.

Embedded signing

Embedded signing keeps its existing per-embed theme options and white-label entitlement rules. See the React SDK when the signer stays inside your application. Organization branding described here applies to normal Korala-hosted links.

Electronic signature disclosure

The final signing action includes an affirmation and a View disclosure link. The link opens the default Korala disclosure unless the sender supplies its own content through the authenticated send API.

A custom disclosure changes the modal content. Korala retains the signing controls and consent capture. Korala sanitizes the HTML and stores a snapshot when the sender sends the document or packet. It records the stored profile version and SHA-256 hash in audit events and Certificates of Completion. See the Documents and Signing Packets guides for request examples.