Per-team branding

Out of the box, every signing page Pacta hosts says “Pacta” at the top and uses Pacta’s brand colors. For most teams that’s fine for a few months — but the moment you start sending to customers or external partners, you want your own logo there. Pacta lets you swap it out on Pro and Business plans.

What branding affects

When you brand an org, the following surfaces change:

• Signing page that recipients land on — your logo top-left, your accent color on buttons + accents, your name in the subject area
• Signing email that recipients receive — sent from your custom domain, with your logo in the email body and the email “from” name
• Signed PDF footer — every page of the final sealed PDF carries a small “Verified by sign.pacta.ink · Envelope <id> · Signed <timestamp>” line. The sign.pacta.ink URL stays (it’s the verification path), but the sender in audit records is your org
• Certificate page in the final PDF — branded with your org name
  • logo

What it doesn’t affect:

• The Pacta URL — recipients still see sign.pacta.ink/sign/... in the address bar (white-labelling the URL itself is Enterprise)
• The footer “powered by Pacta” line — visible on Free; hidden on Pro and Business

Setting up org-level branding

Settings → Branding in your org. You configure:

Logo

Upload a PNG or SVG. SVG is strongly preferred — it scales cleanly across signing pages, emails, and PDFs without pixelation.

Constraints:

• Minimum width: 240px
• Maximum file size: 1 MB
• Recommended aspect ratio: 4:1 horizontal (matches typical wordmark logos)
• Format: SVG, PNG (transparent background), or PNG (solid bg — works but less flexible)

If your logo doesn’t render well on dark backgrounds, also upload a dark-mode variant. Pacta uses it whenever a signing page is in dark mode or in emails with dark themes.

Accent color

Pick one HEX color. Pacta uses it for:

• Primary call-to-action buttons on signing pages
• Hover states on links
• The signature widget border when active
• Status badges in the signing flow

Stick to your brand primary. Don’t pick a color too close to red (which Pacta uses for “error” and “rejected” states) or too close to green (which Pacta uses for “completed” and “verified”).

Sender domain

The email signing requests come from. By default it’s noreply@sign.pacta.ink — works but feels generic + sometimes gets caught in corporate spam filters.

Configure a verified domain (e.g., contracts@yourcompany.com) under Settings → Email Domains. See Configure your email + sender domain for the DNS setup.

Custom footer text

Replace the default footer copy on signing pages with your own. Common choices:

• Your support email (“Questions? help@yourcompany.com”)
• A link back to your product
• A legal disclaimer specific to your industry

Per-team branding (Business and up)

If you have multiple teams under one org (e.g., separate legal entities, multiple product lines), each team can carry its own branding overrides.

Team Settings → Branding in a specific team lets you:

• Override the org-level logo with a team-specific one
• Override the accent color
• Set a different sender domain for that team’s documents
• Set a different signing-page footer

When a member of that team sends a document, the recipient sees the team’s brand instead of the parent org’s. Useful when, say, Acme Capital (parent org) operates two DBAs — AC Lending and AC Capital Services — that need different visual identities.

Branding the signing page

Beyond logo + color, you can fine-tune the recipient experience:

• Signing-page title — the heading recipients see when they land (“Sign your Acme Capital agreement” instead of generic Pacta copy)
• Welcome message — a custom intro paragraph above the document
• Theme — light or dark (matches your customer’s product if you’re embedded)
• Custom CSS (Enterprise) — full control over the signing page appearance

Hiding “Powered by Pacta”

Free tier shows a small “Powered by Pacta” badge at the bottom of every signing page + email footer. Pro and Business tiers can hide this:

Settings → Branding → Display options → toggle off “Show Powered by Pacta”

This isn’t enabled by default — it’s a deliberate flip. Some customers leave it on to credit Pacta and reassure recipients that the signing infrastructure is reputable. Most customers turn it off because the branding feels cleaner that way.

Testing your branding

The fastest way to QA: send a document to yourself.

1. From a branded org, click Send Test in the templates panel (or manually send a one-off doc to your own email)
2. Open the email — check the sender, the logo, the email body
3. Click through to the signing page — check the logo, accent color, footer
4. Sign it — check the confirmation email
5. Once “complete,” check the final PDF — every page footer, the certificate page

If anything looks off, settings → branding → save → re-send. Pacta applies branding changes immediately to new envelopes; documents already in flight keep the branding they were sent with.

Common gotchas

• “My logo looks blurry on the signing page.” Upload an SVG, or upload a PNG that’s at least 480px wide (we display at ~240px but use 2x for high-DPI screens).
• “My accent color shows wrong on the button.” Double-check the HEX value is 6 characters (e.g., #1f2937 not 1F2937 or #1f293).
• “My team brand isn’t showing — it’s still org branding.” Team branding is Business and up. On Pro you only get org-level branding. Upgrade to enable team-specific overrides.
• “Emails still come from noreply@sign.pacta.ink.” Sender domain is a separate setting (Email Domains), not part of Branding. See Email Domains.

Where to go next

• Configure your email + sender domain — the next deliverability win after logo
• Audit trails + verification — what recipients can independently verify about the signature