Set up your organisation

Name your org, pick a URL, configure branding, invite your team, and set up the basics that every member will see.

Last updated May 12, 2026

When you sign up for Pacta, you get a default Personal Organisation. That’s enough to send documents on your own — but if you have a team, multiple legal entities, or just want branded signing pages, you’ll want to set up a proper organisation.

This guide covers the basics every org needs.

Personal Org vs Team Org — what’s the difference?

  • Personal Organisation — auto-created when you sign up. Bound to your user account 1:1. Use it for your own signing or as a scratchpad. Always carries your name + email as sender.
  • Team Organisation — a workspace you create separately. Has its own name, URL, branding, billing, members, and (optionally) Teams inside it. Use it when more than one person needs to send under a shared identity.

You can have both — many users keep a Personal Org for personal stuff and a Team Org for company stuff. Switch between them via the org switcher in the top-right.

Creating a new organisation

From your top-right menu → Create Organisation +. Pacta asks for:

  • Name — what shows up in emails and on signing pages (e.g., “Acme Capital”, “Northwind Lending”)
  • URL slug — the bit that goes in sign.pacta.ink/o/<slug> (e.g., acme-capital). This is permanent — pick something stable.

After creation, you land on the org’s dashboard with the URL you chose.

Step 1 — Brand the org

Org settings live at /o/<slug>/settings/. The first stop:

  • General — change the name, upload an avatar (used as org icon), set a description. The URL slug is fixed at creation; if you really need to change it, contact support.
  • Branding — upload a logo that replaces the Pacta wordmark on signing pages your recipients see. Pick an accent color that ties to your brand. Toggle “Hide powered by Pacta” if you’re on Pro or Business (Free shows a small Pacta footer).

A signed PDF from a branded org carries that brand visually — your logo shows up on the certificate page, the audit footer carries your sender domain, and the signing page itself wears your colors.

Step 2 — Configure email

By default, Pacta sends signing emails from noreply@sign.pacta.ink. That works, but corporate spam filters often strip emails from unknown senders. Two things to set up:

  • Sender domain (Pro and Business) — connect your own domain so emails go from contracts@yourcompany.com. See Email Domains for the DNS setup.
  • Custom SMTP (Business) — if you’d rather have Pacta send through your own mail server entirely (Postmark, AWS SES, Postfix), point Pacta at your SMTP credentials. Same end result, more control over deliverability monitoring.

Step 3 — Invite team members

/o/<slug>/settings/members → Invite member. Pacta asks for:

  • Email — where the invite goes
  • Role — controls what they can do:
    • Admin — full access including billing, member management, branding, and SSO
    • Manager — can send/receive documents, manage templates, but can’t change billing or add members
    • Member — can send/receive their own documents and view team docs they’re added to

The invited person gets an email with a one-click link. When they click it, Pacta automatically:

  1. Creates their account (if they don’t have one) or signs them in
  2. Adds them to your org with the role you picked
  3. Drops them on your org’s dashboard

Heads up: if the person has signed up before and landed in a Personal Org, accepting your invite makes them a member of your org in addition to keeping their Personal Org. They can switch between orgs from the top-right menu.

Step 4 — Set up Teams (optional)

For larger orgs, you can split work into Teams within the organisation. A Team is a sub-group with its own:

  • Members (a subset of the org)
  • Documents (visible only to that team’s members)
  • Templates (private to the team)
  • Email sender domain (if Pro/Business)
  • Branding overrides (if you want different legal entities to look different — e.g., MFG vs MORG-CAP under one parent org)

Teams are useful when you have multiple legal entities, multiple products, or multiple departments that shouldn’t see each other’s documents. They’re overkill for a 5-person startup.

Step 5 — Default document preferences

Settings → Preferences → Document sets defaults for every document sent from this org:

  • Signature types allowed — draw, type, upload, or any combination
  • Authentication required — should signers verify their email or enter a one-time code before signing?
  • Auto-reminders — chase non-signers every N days
  • Document expiration — auto-cancel after N days if not completed

You can override any of these per-document, but setting the defaults saves a click on every send.

Things to check on Day 1

After creating an org, run through this quick checklist:

  • Name + avatar set
  • Branding logo uploaded
  • Accent color picked
  • At least one teammate invited (it’s lonely solo)
  • Sender domain verified (Pro/Business)
  • One test document sent to yourself to make sure the email looks right

Common gotchas

  • “I can’t change the URL slug.” Right — it’s permanent. If you really need to change it (e.g., you renamed the company), contact support. We can rename it but it requires forwarding the old slug, which we’d rather not do casually.
  • “My teammate didn’t get the invite email.” Pacta sends the invite from your verified sender domain. If you haven’t set one up, it goes from noreply@sign.pacta.ink which often gets filtered. Set up a domain first, then re-invite.
  • “My logo looks pixelated on the signing page.” Upload at least a 240px-wide PNG or (better) an SVG. Tiny logos get upscaled and look fuzzy.

Where to go next

Have a question this doc didn't answer? Email us and we'll fix it.