Signers sign. CC recipients just need to know.

On almost every document there's a gap between who has to act on it and who needs to see that it happened. The two parties to a contract sign it. But the salesperson who closed the deal, the finance inbox that has to invoice against it, the legal address of record, the candidate's future manager on an offer letter — none of them sign anything. They just need the finished document and proof it's done.

That's what a CC recipient (carbon copy) is for. A CC is added to a signature request not to sign, but to receive a copy of the completed document — usually the moment everyone has signed. It's the e-signature equivalent of the CC line on an email: in the loop, not on the hook. Using it well keeps the right people informed without cluttering the signing flow or accidentally turning a bystander into a required signer.

What a CC recipient can and can't do

The distinction that trips people up is that a CC is a recipient role, not a signer with the signing taken out. The behavior is deliberately limited:

  • A CC does not sign and is not assigned fields. They have no signature, initial, or date block to complete. The document doesn't wait on them.
  • A CC does not block completion. Because they have nothing to do, an envelope reaches "completed" status when the signers finish — a CC never holds it open. This is the key difference from making someone a signer "just so they get a copy."
  • A CC usually receives the document on completion. The standard behavior is that CC recipients are emailed the final, fully-signed PDF once the last signature lands — so what they get is the finished record, not a half-signed draft.
  • A CC appears in the audit trail. Adding a CC is itself an event, and the delivery of the completed copy is logged. The audit trail shows who was copied and when, which matters when "who had a copy of this?" becomes a real question later.

When to use a CC instead of a signer

The rule of thumb: if the person's signature has no legal or procedural meaning on this document, they should be a CC, not a signer. Some common cases:

  • The deal owner or account rep. They need the executed contract for their records and to trigger their own next steps, but they aren't a party to it.
  • A finance or operations inbox. Invoicing, provisioning, or fulfillment keys off the signed document. CC the shared mailbox so the executed copy lands where the work happens — without a person having to forward it.
  • A manager or stakeholder who needs visibility. On an offer letter or HR document, the hiring manager often wants the countersigned copy for onboarding but isn't a signatory.
  • A legal or compliance address of record. Some teams CC a monitored archive address on every executed agreement so there's always a second copy outside the originating account.

The anti-pattern is the reverse: adding someone as a signer with an unnecessary signature field just to make sure they get a copy. That makes a non-party block the document, pads the audit trail with a meaningless signature, and muddies who actually agreed to what. If they don't need to sign, don't make them.

CCs, automation, and bulk sends

A CC is often the simplest alternative to building automation. Before you wire up a webhook to forward completed documents to a person, ask whether a CC recipient does the job — for a human who just needs the PDF in their inbox, it usually does, with nothing to maintain. Reserve the envelope.completed webhook for when a system (not a person) has to react: filing the document, updating a CRM record, kicking off provisioning.

CCs also scale cleanly with bulk send. When you blast the same document to hundreds of signers, you can CC a single internal address on every one, so a complete set of executed copies accumulates in one place automatically — no per-document forwarding, no gaps. Bake the CC into a reusable template and the right people are copied on every document of that type by default, so "did finance get a copy?" stops being a question anyone has to ask.

The takeaway

A CC recipient is how you keep people informed without making them sign: they receive the completed, fully-signed document, they never block the envelope, and their inclusion is logged in the audit trail. Use a CC whenever someone needs the executed record but isn't a party — the deal owner, a finance inbox, a manager, an archive address — and resist the temptation to add a throwaway signer just to deliver a copy. Done right, the people who need to know always have the finished document, and the signing flow stays limited to the people who actually have to sign.