Skip to main content
For AI agents: a documentation index is available at https://docs.coverbase.com/llms.txt. This page is also available in markdown by appending .md to the URL.
This guide is part of the User Guides collection. Read the e-signature overview for how the pieces fit together, and templates for building the paper you send from.
An envelope is one agreement, out for signature, addressed to named people. It is the object that binds the parties, and the one that carries the record of what happened.

​
Start an envelope

New Envelope on Contracts → Signatures opens a four-step wizard. You can also start one with Send for signature in the Signature step of a contract’s Workflow tab, which files the envelope against that contract. Nothing is saved until you send, so leaving the wizard part way leaves nothing behind.

​
Step 1: the document

Send wizard step one showing envelope name, the five paper sources with Upload selected, associated vendor and expiration

Step 1. Name the envelope, choose its paper, file it against a vendor, and set how long it stays open.

Envelope Name names the agreement in every email Coverbase sends about it, and is the name the executed copy is filed under. Make it something the counterparty will recognize. Then pick the paper. From a template copies a template’s roles and field layout across. From a document, From a contract, Upload and Write all start you with paper and no fields, which you place yourself in step 3. Upload takes several files, which travel as one envelope. Write lets you write the agreement in Coverbase, inserting passages from your library, and renders it to a PDF. Associated vendor files the agreement against a counterparty. Set it even when it feels obvious: it puts the envelope on that vendor’s record, and it pre-fills a Company field for the signer. Expiration starts at 30 days, or at whatever the template or your organization’s settings specify. Change the number, or switch to Expires on and pick a date.
The unit selector next to the number changes how the deadline is written, not what it is. If the day count does not divide evenly into weeks or months the selector stays on days rather than showing a rounded figure that disagrees with what is sent.

​
Step 2: the recipients

Send wizard recipients step showing name, email, private note, recipient type, signing step and identity check for a party

Step 2. Each card is one party: who they are, what they do, when they are asked, and whether they have to prove who they are.

If you are signing something yourself and nobody else is involved, turn on I am the only signer at the top. It sends the envelope to you alone in a single step, and drops any other party you had added. Otherwise, each party gets a card. Four kinds: Name and email autocomplete from you, your colleagues, and the people on the associated vendor (its relationship owners, risk analysts, watchers and contacts), so a party you have dealt with before is two keystrokes. Signs in step is the routing order, and reads Approves in step on an approver. Parties in step 1 are asked immediately; step 2 is notified when step 1 finishes, and so on. Give two parties the same step and they are asked at the same time. Drag a card by its handle to reorder the list.
A copied party has no step number, because copies go out as soon as the envelope is sent, regardless of routing. Their card reads Delivery: emailed a copy when the envelope is sent. That email says who sent the agreement and carries the document as a PDF attachment, with no signing link. If it cannot be sent, Coverbase sends it again when the next signing step goes out. When every party has signed, they also get the executed copy. If you need someone to receive the agreement only after it is executed, a copied party is not that.
Private Note is a line only that one recipient sees. It is the place for “this is the revised schedule we discussed” without putting it in front of everybody else on the envelope. Identity Check is per party, and defaults to None. Set it to Access code and Coverbase generates a code for that recipient, which they must enter before the document opens.
Send an access code to the signer by some other channel: a call, a text, anything that is not the signing email. Coverbase stores it as a digest and never shows it again once the envelope is sent, so copy it before you send. The refresh icon beside the field mints a new one if you lose it.
If a template supplied the roles, the seats are already there and you are only filling in names and addresses. Fields follow the role, so changing who sits in a seat keeps their placements.

​
Step 3: the fields

Same canvas as the template builder: parties down the left, palette below them, document in the middle, inspector on the right. If you came from a template the fields are already placed and this step is a review; if you came from a bare document, this is where you place them.
Send wizard fields step with the document canvas and field palette

Step 3. Placing fields on the envelope itself, for envelopes that did not come from a template.

Everything in the field types applies here unchanged.

​
Step 4: review and send

Send wizard review step showing signing order, signing emails, signature meaning and the notify and authenticate toggles

Step 4. The signing order, the email that carries it, and the two switches that decide how it goes out.

Signing Order at the top is the last look at who is asked, in what order, and how many fields each one owns. The step numbers are still editable here and the rows still drag, so a routing mistake spotted at the end does not send you back a step. Signing Emails is the invitation. Subject is the invitation’s subject line for this envelope. Leave it blank and the invitation uses your organization’s own invitation subject from Signing Settings, or, without one, Coverbase’s built-in Jordan Lee sent you Mutual NDA. Opening line is added to every party’s invitation. Rewrite drafts both from the document itself, which is usually a better starting point than a blank box. What does signing mean? is recorded with every signature on the envelope. Most agreements do not need it. Regulated workflows do, and some organizations require it on every envelope. The step says so if yours does. Two switches decide how it goes out: Send for signature emails the first routing step, emails each copied party their copy, and gives the agreement one permanent portal address.

​
Track what is out

The envelope’s Overview tab is the working view. Down the middle: the source document with Open the original, Download full packet and Verify now, and under it Fields and Values, listing every field, whose it is, what it holds, which page it sits on and when it was filled. Down the right: the signing order, the envelope’s details, and the portal link.
Envelope detail overview showing document actions, fields and values, signing order, details and portal link

An envelope in flight. Signing Order reads party by party, and Fields and Values shows what has been entered.

Signing Order is where you look when someone asks “where is this?” It reads per party (approved, opened but not signed, not yet asked) rather than as one envelope-level status. The badge beside the envelope name says which template version it came from. Details carries the vendor the agreement is filed against, when it was sent, when it expires, when it completed, and how many documents it holds. The vendor can be changed from here if it was set wrong.
The portal link is a permanent address for the agreement, for handing it over out of band or back to a party whose invitation link has expired. Holding the link is not enough to open it. The visitor enters their email address, and Coverbase emails a one-time code only to a party on the envelope whose turn it is, or to any party once the envelope is executed. Nothing is shown until that code is entered.

​
Nudging, correcting, cancelling

Resends a reminder link to the parties currently pending. It does not touch anyone who has already signed and it does not disturb the routing order.
For when the document or the recipients were wrong. The original is voided with its trail intact and you rebuild it in the send flow with everything carried across, so you are not retyping the whole envelope. The voided original stays in the list for the record, and a banner across the rebuild says which envelope you are correcting.Field values are not carried: a value belongs to the signature that was collected on the old envelope, not to the new one. Access codes are not carried either. A party who had one comes back with Identity Check set to None, so set a new code if you still want one.
Closes every signing link immediately. Signatures already collected stay on the record. Voiding cancels the agreement; it does not erase what happened. A reason is required, and it goes into the audit trail beside the void.
A signer can also decline, and a decline stops the envelope rather than skipping that person. Nobody further down the routing order is asked.

​
What you get when it completes

Once the last party signs, Coverbase flattens every field into the page, seals the PDF, and generates a signing certificate beside it.
Executed envelope detail with Download signed copy as the primary action, every field signed, and both parties green in the signing order

An executed envelope. The status reads Executed, the document line names the seal level achieved, and Download signed copy takes the place of Send Reminder.

  • Download signed copy: the sealed PDF, with every signature, initial and stamp burned into the page and attributed. It appears in the envelope’s header, in place of Send Reminder, once every party has signed.
  • Download certificate: the certificate of completion, under Actions. It only exists once every party has signed.
  • Download full packet: the signed copy and the certificate together, for handing to a counterparty or an auditor.
  • The document line under the file name reads sealed at B-B (or whatever level was achieved), so you can see what the executed copy carries rather than what was asked for.
Where the executed copy and the certificate are filed depends on where the paper came from:
  • Paper from a vendor’s documents. When the paper was picked From a document or From a contract, or came from a template built on one, both are added to the documents of the vendor that owns that document.
  • An envelope sent for a contract. When the envelope was started from a contract’s Workflow tab, or its paper was picked From a contract, the executed copy is also added to that contract’s documents. Signed from one of the contract’s own documents, it takes that document’s role, and the unsigned version stays on the contract as a Redline of it. So signing the contract’s Root document makes the signed copy the new Root. Paper the contract never held becomes its Root if it has none, and otherwise joins its documents as Unmatched, for you to set its role. Uploaded or written paper is filed on the contract’s vendor.
  • Anything else. Uploaded or written paper on an envelope that is not for a contract stays on the envelope, where Download signed copy and Download certificate fetch it. The Associated vendor does not file it.

​
The audit trail

Every event is recorded in order and hash-chained: each entry carries a sequence number and a hash that covers the one before it. Removing or editing an entry breaks the chain, so tampering is detectable.
Audit trail showing envelope created, sent, signer notified, portal opened, consent accepted, signature adopted and signed events with IP addresses and hashes

The audit trail. Each event carries who, when, from where, and a chain hash.

Events cover the whole life of the envelope: created, sent, each party notified, each portal opened, consent accepted against a specific disclosure version, each signature adopted and applied, and the final seal. Portal events carry IP, approximate location and user agent. The Integrity panel beside it names the seal level applied (or Not sealed until every party has signed), when the seal was last verified, and the hashes:
Verify now on the Overview tab re-validates the stored executed copy against its seal the way a PDF reader would, and records the verdict under Last verification in the Integrity panel. That is the answer to “is this the file that was signed?”

​
Common problems

That is how routing works. Later steps are notified as the envelope advances. If the first step has not finished, nobody after it has been asked.
Their copy goes out when the envelope is sent, as an email with the document attached. Nothing is emailed to anyone, copied parties included, when Email recipients the signature link was off. Check their address on the envelope, and look for Party notified against their name on the audit trail.
Word files convert to PDF before they can be shown. The portal polls and resolves itself when the conversion lands, so a signer does not need to refresh.
An envelope has been sent from it, so the version is cited in an audit chain. Use Edit as new version; see versioning.

E-signature overview

Envelope statuses, signing settings, and what Coverbase keeps.

Signature templates

Build the paper you send from, with roles and fields placed once.

The signing experience

What the parties on your envelope see, and what to tell one who is stuck.

Contract intake and approval

Sending an approved contract through DocuSign instead.

Bulk send

Send one template to a list of parties, one envelope per row.