Skip to main content

Quick start

From installation to your first signed document in 10 minutes. This guide covers the shortest path; each step links to the detailed page.

Before you start
  • System administrator rights on your Salesforce org.
  • A Yousign account (the trial plan is enough for sandbox): app.yousign.com.
  • A test PDF to get signed.

1. Install TrueSign​

Install the TrueSign managed package in your org (a sandbox is recommended for a first run). The installation does most of the work by itself:

  • the TES_Admin permission set is assigned to you automatically (you, the installer);
  • the 5 maintenance jobs schedule themselves (sync, approval reminders, weSign lifecycle, purges) — see Jobs & synchronization;
  • sandbox network access is already packaged.

The TrueSign application appears in the App Launcher, with its tabs: Setup, Envelope Templates, Gen Templates, Envelopes, Status and Logs.

2. Connect your Yousign account​

  1. In Yousign: Settings → API → API Keys → Create API Key. Copy the key — it is only shown once. (Planning to run 100% weSign? The Yousign key is then optional — skip this section.)
  2. In production only, allow the domain: Setup → Remote Site Settings → New with https://api.yousign.app — the sandbox Remote Site ships with the package.
  3. Open the TrueSign app → TrueSign Setup → eSignature → Settings:
    • paste the API key (the field is masked after saving);
    • pick the Sandbox or Production environment;
    • click Test Connection — the "Yousign connected" badge confirms everything works.

Full details (webhook, HMAC secret, global preferences) are in TrueSign setup.

The webhook lets Yousign notify Salesforce in real time — statuses and the interface update on their own, no manual refresh.

  • In production: one click on Provision webhook in the Settings screen is enough — TrueSign creates the webhook at Yousign and the secret is configured automatically, nothing to copy-paste.
  • In sandbox: Yousign only allows creation from its dashboard — Webhooks → Create Webhook, paste the URL shown in Settings, then copy the secret over. Details and traps in TrueSign setup.

The Webhook intake card on the Settings screen confirms events are being received.

4. Add the sending component to a page​

  1. Open a record (Opportunity, Account, Contact…) → ⚙ → Edit Page.
  2. Drag the TrueSign — Signature Request component onto the page.
  3. Save then Activate.

5. Send your first document​

  1. On the record, attach a PDF via Files → Upload Files.
  2. In the TrueSign component: select the PDF, add a signer (first name, last name, email, phone in +33… format), pick simultaneous or sequential routing.
  3. Click Send for signature.

The signer receives a Yousign email with a secure link — no account required. They verify their identity with a one-time code (email OTP by default, SMS OTP for the AES level), sign, and receive their copy by email.

On the Salesforce side: the status moves from Ongoing to Done, and the signed PDF is automatically attached to the record.

Yousign sandbox limitation

In the sandbox environment, the signer's email must belong to your Yousign organization. This restriction disappears in production.

What next?​