Skip to content

Atlas

Answers from this help and cites its sources. 20 questions a day.

Send for signature

A PDF from the record goes out for electronic signature in three steps. Signing goes through Arcane eSign (Firma.dev technical process), included in your plan; the signed PDF and its certificate come back to the record on their own.

Depending on your plan, within the monthly sending quota A record › Files › Send for signature Every member, for the PDFs they can see

On a PDF’s row, click Send for signature (or pick it in the … menu). The window shows the real PDF on the right, as the signers will see it.

The button only shows on an added PDF that has never been sent; otherwise the row shows its signature status. In the … menu, the item is greyed out, with the reason on hover, for a file that is not a PDF, a signed PDF or an audit trail, a document already out for signature, or a colleague’s private document.

123456
  1. 1The three steps
  2. 2Add a contact, a colleague or an address
  3. 3Add yourself as a signer
  4. 4Sign in order
  5. 5The PDF, as the signers will see it
  6. 6This month's sends
Hover a number to find the area. Click the screenshot to enlarge it.
The Signers step: the search to add a signer, Camille Laurent as signer number 1, the Sign in order box and the PDF preview on the right.
  • The record’s contact is already added when they have an email address.
  • Search for a contact or a colleague, or type a full address. Add me puts you in the list. Ten recipients at most.
  • Each person is a Signer or In copy: a person in copy does not have to sign. At least one signer is needed.
  • Sign in order (checked by default) sends the document to the next signer only once the previous one has signed. The arrows change the order.
  • If you are a signer, you can sign in the app right after sending.
The Placement step: Automatic, I place the fields (selected) and Tags in the PDF, with the Signature, Camille Laurent and Add bar above the preview.
  • Automatic: one signature per person at the bottom of the last page.
  • I place the fields: choose the type (signature, initials, date, text or checkbox) and the signer, click Add, then drag the field onto the page. Each signer needs at least one Signature field.
  • Tags in the PDF: the PDF already contains tags such as {{s1|signature|161|70}}, which the service replaces with fields.
The Review step: the summary of signers and placement, the Simple (SES) level, the expiry date, the message to signers and the Send to 1 signer button.
  • Level:
    • Simple (SES): everyday commercial contracts.
    • Advanced (AES): each signer enters a verification code received by email.
    • Qualified (QES): only if the organization has connected a Youtrust account that enables it; each signer checks their identity at Youtrust.
  • Expires on: in 30 days by default, between tomorrow and 90 days.
  • Message to signers: optional, added to the invitation.

Click Send. The invitation and reminders are sent by Arcane, at most one reminder a day.

Each Arcane eSign send counts toward your organization’s monthly quota, shown at the bottom of the window and on the Signatures page. Once it is reached, sending is refused, unless the organization owner has allowed overage in Settings › Templates and signature › E-signature: further sends are then billed, up to the monthly cap they set.

An administrator can connect the organization’s Youtrust account with its API key in Settings › Templates and signature › E-signature. The CRM checks the key and creates the webhook itself.

  • The Qualified level then goes through that account.
  • For an Advanced signature, the Use the organisation’s Youtrust account box sends through Youtrust instead of Arcane eSign.
  • With Youtrust, signatures are placed automatically or with tags.
  • Youtrust sends count toward your Youtrust account’s quota, not Arcane eSign’s.