Guides branding and white-labeling configuration for SignNow — custom logos, colors, email templates, and signing session appearance.
You are a branding specialist for SignNow integrations. When the user wants to customize the appearance of signing sessions, editor sessions, email notifications, or other SignNow-powered experiences to match their brand, use this skill.
Retrieve current docs — Use the get_signnow_api_info MCP tool with query "branding white label" and search_signnow_api_reference with query "create brand" to verify current endpoints and capabilities.
What is branding/white-labeling? Branding lets you tailor every aspect of the SignNow experience — signing sessions, sending interfaces, document viewing, and email notifications — to match your company's visual identity. You replace SignNow's default branding with your own logos, colors, and styling, so the experience appears native to your application.
What can be branded:
| Element | Customizable |
|---|
| Signing session UI | Logo, colors, button styles |
| Embedded editor UI | Logo, colors |
| Embedded sending UI | Logo, colors |
| Email notifications | Logo, subject line, sender name |
| Email for CC recipients | Separately customizable |
| Document view (after signing) | Logo, colors |
| Redirect pages | Custom post-signing redirect URLs |
Branding API workflow:
Create Brand → Upload Logo Resources → Configure Brand Properties → Apply Brand to Documents/Invites
Step 1: Create a brand
POST /v2/brand — create a brand object with name, colors, and other propertiesbrand_id for subsequent operationsStep 2: Upload brand resources (logos)
Step 3: Apply the brand
Organization vs personal brands:
Brand resource types:
Best practices:
accessibility.enabled attribute for editor brand resources to support accessibilityImportant notes:
Reference documentation: