Copying someone in
A recipient in copy (CC) follows a request without ever signing: a lawyer, a broker, an end customer, a colleague who must be kept informed. They need no Salesforce licence — they live on a link, just like signers.
Adding a CC
In the sending form or in the template, add a recipient and give them the In copy (CC) role. Fill in their name: it is used in the emails ("Hello Claire Observer" rather than "Hello claire@…").
A CC never counts towards progress, is in no signing order, carries no field to fill in, and never delays completion.
What the CC receives
| Moment | Button | |
|---|---|---|
| On sending | "For your information: document title" | View the request → their tracking page |
| On every signature | "Paul Premier signed document title" | Download the document |
| On completion | "Everyone has signed" | Download the signed document |
The last signature triggers the completion email, which says everything "X signed" would say — plus the signed document. Two emails landing together is noise, not information.
Their tracking page
The link leads to a dedicated page, in guest access:
- the document title and the sender;
- the progress — "1 signature out of 2", with a bar. It only counts signers: an approver or another CC do not enter it;
- the list of signers: name, language, status (to sign / signed / declined);
- the expiration deadline;
- a download button: the document as sent while signing is in progress, then the signed version and the proof certificate once the envelope is complete;
- a "restricted guest access" banner and an EN / FR switcher.
Neither the email address nor the phone number of the signers. An observer has no business knowing the contact details of the people signing — the restriction is enforced server-side, not by simply hiding things on screen. (An approver does see them: they decide precisely who is going to receive the envelope.)
The CC has no access either to the other parties' signing links, nor to any access code.
Security and lifecycle
- The CC's link is personal: every party has their own, and it never allows signing.
- It is revoked along with the request: cancellation or expiry cuts access.
- An unreachable CC (invalid address, email quota reached) never causes a signature that took place to fail.
On a request sent before this feature
Requests created before the CC role arrived carry on normally: their copied recipients receive their emails, without a button — they have no personal link. There is nothing to redo; new requests benefit from it automatically.