Branding
Put your logo, colors and email wording on what signers see.
Note
Available on Pro and Platform. Owners and admins can edit branding. On a plan without branding, your settings are kept but not shown; they come back when you upgrade.
Every plan
Signer emails come from “{your name} via eSignStack”, replies go to whoever sent the envelope, and the email signs off with your workspace name. Workspace and platform keys use the workspace name and the support email when there is no sending member. Account emails, including password resets, verification and invitations, keep the eSignStack logo image.
Where branding shows
- Signing pages and the signing disclosure
- Kiosk start forms and share links, including embedded share links
- Signer emails, including verification codes, requests, reminders and completed copies
- Workspace footers on envelope notifications to senders
- The verify page and browser tab icon on branded public pages
- The certificate page of completed PDFs
Changes apply as soon as you save, including to signing pages of envelopes already sent. Completed PDFs keep the logo they were made with.
Edit branding
Open Settings → Branding. The preview has Signing page, Email, Kiosk and Completed PDF tabs, and shows unsaved changes. The Kiosk preview shows the existing start form: visitors can enter their name and email immediately.
| Setting | What it does |
|---|---|
| Logo | PNG, JPEG, WebP, GIF or SVG, up to 5 MB. A wide logo, about 4:1, works best. Empty edges are trimmed and images are saved as PNG. Emails show it on white, so it stays clear in dark mode. SVG is converted in your browser. |
| Logo for dark backgrounds | Optional. Shown in dark mode. Without it, the main logo is used. |
| Icon | A square logo for browser tabs, small phone headers and workspace avatars. At least 512 × 512 px works best. |
| Primary color | Buttons, links and the progress bar. |
| Accent color | The sign-here flag and required fields. |
| Corner radius | Rounding for buttons, fields and cards. |
| Font | The typeface on signing pages and kiosks. |
| Website | Linked from the logo and footer in emails, and from the finished screen. Use an HTTP or HTTPS URL. |
| Support contact | An email address or phone number for signers with questions. An email address also gets replies when no person sent the envelope. |
| Email header text | Shown above the message in signer emails. |
| Email footer text | Shown at the bottom of emails. |
Leave a field empty to inherit its default. Select Save branding when you're done. Reset to defaults removes your own kit and its files.
Customer workspaces on Platform
A platform sets default branding for all its customer workspaces. Each workspace can override fields in Settings → Branding. Empty fields use the named platform's defaults. A light/dark logo pair comes from one kit.
Only the platform decides whether sent with eSignStack shows. White label signer emails use the workspace as their From display name. Reset to defaults removes a workspace's own branding and restores the platform defaults.
Test keys can't change branding: the sandbox uses the live workspace's kit. Platforms set defaults in the platform console or through the API. See the platform guide.
Through the API and MCP
/api/v1/brand_kits reads and changes the owner's kit. GET /api/v1/brand_kits/effective returns resolved fields such as primary_color, logo_light_url, icon_url and website_url, after inheritance. It does not return CSS or theme variables.
Changes require brand_kits:write, a live key and a plan with custom branding (or a platform workspace). Only platform keys can write show_powered_by. Upload logo_light, logo_dark or icon as multipart raster files, up to 5 MB; SVG must first be converted to PNG. remove_assets[] accepts those three slots.
The workspace provisioning and update brand_kit field accepts an object of kit fields, or null to remove the own kit and use platform defaults. It does not accept a bk_… reference. The workspace response's brand_kit remains its own kit reference, or null when inherited.
AI agents use get_brand, save_brand_kit (colors, font, radius, website, email text and support contact) and delete_brand_kit. Logos and icons are uploaded in the app or REST API. Signing session appearance also needs a plan with custom branding or a platform workspace; theme URL query parameters have no effect.