> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developers.hellosign.com/llms.txt.
> For full documentation content, see https://developers.hellosign.com/llms-full.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.hellosign.com/_mcp/server.

# Features

> Premium features available in Dropbox Sign including Premium Branding, SMS Delivery & Verification, and Signer PIN / Access Code.

# Features

Premium features available depending on the Subscription plan.

---

## Premium Branding

**Brief:** Customizing the visual appearance of the signing experience (colors, logo) to match application branding.

**Description:**
Allows customizing the look and feel of the signing experience to match an application's branding. Configured per API App.

**Customizable Elements:**
| Element | Description |
| --- | --- |
| `primary_button_color` | Color of primary action buttons |
| `primary_button_text_color` | Text color on primary buttons |
| `primary_button_color_hover` | Button hover state color |
| `secondary_button_color` | Secondary button color |
| `secondary_button_text_color` | Secondary button text color |
| `header_background_color` | Header area background |
| `page_background_color` | Page background color |
| `text_color1` | Primary text color |
| `text_color2` | Secondary text color |
| `link_color` | Hyperlink color |

**Key Facts:**
- Configured per API App (different apps can have different branding)
- Applies to both embedded and email-based signing
- Logo upload available in dashboard
- Requires a paid Subscription with the Premium Branding feature enabled

**Related docs:** See [Premium Branding](/api/manual-reference-pages/premium-branding) for supported branding options.

---

## SMS Delivery & Verification

**Brief:** Sending signing notifications via SMS and/or requiring phone-based verification before signing.

**Description:**
SMS features in Dropbox Sign serve two distinct purposes:

1. **SMS Delivery:** The signing link is sent to the signer via text message instead of (or in addition to) email.
2. **SMS Verification:** The signer must verify their phone number via an SMS code before accessing the documents (2FA-style identity verification).

**Important Distinctions:**
- SMS Delivery is about *how the signer receives the signing link* — it replaces or supplements email delivery.
- SMS Verification is about *identity verification before signing* — an additional security layer regardless of how the link was delivered.
- These are independent features: a request can use SMS delivery without verification, verification without SMS delivery, or both.

**Related docs:** See the [SMS Tools walkthrough](/docs/guides/sms-tools) for setup requirements and examples.

---

## Signer PIN / Access Code

**Brief:** An additional security layer requiring signers to enter a PIN before viewing and signing documents.

**Description:**
Signers can be required to enter a PIN (access code) before accessing documents. This adds identity verification beyond email access. The PIN must be communicated to the signer through a separate channel (phone, SMS, in-person).

**How It Works:**
1. Set `pin` on the signer when creating the request
2. Signer receives the signing notification
3. Before viewing documents, signer must enter the correct PIN
4. After entering the PIN, normal signing flow continues

**Important Distinctions:**
- The PIN must be communicated through a separate channel from the signing notification (e.g., phone or SMS), otherwise the additional security layer is ineffective.
- PIN is set per-signer — different signers on the same request can have different PINs or no PIN at all.

**Related docs:** See the [SMS Tools walkthrough](/docs/guides/sms-tools) for signer authentication options.