AgentSkillsCN

signnow-branding

指导 SignNow 的品牌化与白标化配置——自定义 Logo、配色、邮件模板，以及签名会话的外观样式。

SKILL.md
--- frontmatter
name: signnow-branding
description: Guides branding and white-labeling configuration for SignNow — custom logos, colors, email templates, and signing session appearance.
model_invokable: true
auto_activate:
  - "signnow branding"
  - "signnow brand"
  - "white label"
  - "whitelabel"
  - "custom logo"
  - "signing session appearance"
  - "email branding"
  - "signnow customize"

SignNow Branding & White-Labeling

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.

Behavior

  1. •

    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.

  2. •

    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.

  3. •

    What can be branded:

    ElementCustomizable
    Signing session UILogo, colors, button styles
    Embedded editor UILogo, colors
    Embedded sending UILogo, colors
    Email notificationsLogo, subject line, sender name
    Email for CC recipientsSeparately customizable
    Document view (after signing)Logo, colors
    Redirect pagesCustom post-signing redirect URLs
  4. •

    Branding API workflow:

    code
    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 properties
    • •Returns a brand_id for subsequent operations

    Step 2: Upload brand resources (logos)

    • •Upload logo for signing sessions
    • •Upload logo for email notifications
    • •Upload logo for the editor
    • •Upload logo for the sending interface
    • •Each resource type has its own endpoint

    Step 3: Apply the brand

    • •Attach the brand to documents, invites, or applications
    • •Brand is applied automatically to all sessions using that document/invite
  5. •

    Organization vs personal brands:

    • •Individual users can create personal brands
    • •Organization administrators and moderators can create organization-level brands
    • •Organization brands can be shared across all members
    • •Both personal and organization brands can be applied to documents and invites
  6. •

    Brand resource types:

    • •Logo — displayed in signing sessions and document view
    • •Email logo — displayed in email notification templates
    • •Editor logo — displayed in the embedded editor
    • •Send invite page logo — displayed in the embedded sending UI
  7. •

    Best practices:

    • •Create separate brands for different client-facing applications if needed
    • •Use high-resolution logos (recommended dimensions vary by placement)
    • •Test branding in sandbox before deploying to production
    • •Remember that email branding for CC recipients is configured separately
    • •Keep branding consistent across all touchpoints (signing, emails, editor)
    • •Use the accessibility.enabled attribute for editor brand resources to support accessibility
  8. •

    Important notes:

    • •Branding is included in all SignNow API plans — no extra cost
    • •To create a logo brand resource, you must own the brand
    • •Only organization administrators/moderators can create and modify organization brands
    • •Brand changes apply to new sessions; existing sessions retain their original branding
  9. •

    Reference documentation: