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.
Coverbase connects to DocuSign so documents that come out of the vendor lifecycle (agreements, attestations, approval sign-offs) go out for signature without leaving the platform, through your organization’s own DocuSign account. There are two places you can send from, and they behave the same once the envelope is out:
  • From a contract. The contract’s Execution section, once the contract has cleared its approval chain. This is the path described in Contract intake and approval.
  • From a vendor document. The document’s actions menu, for anything that is not a contract record.

​
What it does

  • Initiate execution from the document itself. A vendor document in Coverbase is sent for e-signature directly from its actions menu, with the envelope created in your DocuSign account. No download, no re-upload, no separate system to open.
  • Route countersignature. Up to five signer slots are supported, each mapped to a numbered anchor in the document. Each signer carries an order value: signers sharing an order sign in parallel, and increasing order values route sequentially, which is how a counterparty-then-countersignature flow is expressed. Assign the vendor signer order 1 and your own authorized signatory order 2, and the envelope reaches your side only once the counterparty has signed.
  • Track the request on the third-party record. The signature request is stored against the Coverbase document it was raised from, carrying the DocuSign envelope ID, the recipients, and the request status as it moves through sent, signed, completed and declined. The status of an in-flight execution is a field on the record rather than something to go and look up.
  • The executed agreement stays bound to the record. Because the envelope is created from a Coverbase vendor document, the fully executed agreement is attached to that third party’s record by construction, not by someone remembering to file it. From there it flows into the contract family: Contract Guardian runs the clause review, Document Insights extracts dates, values, notice periods and liability caps, and obligations are tracked against it.
  • Your account, your audit trail. Envelopes live in your DocuSign tenant, so your existing DocuSign retention, compliance, and audit posture applies unchanged, including the DocuSign certificate of completion.
  • Multi-account aware. Users who belong to several DocuSign accounts pick which one to send from; Coverbase respects DocuSign’s account membership rather than assuming one.
  • Send on approval, without anybody pressing send. A contract approval policy can carry Send for signature on approval. The requester names who signs while the contract is still in its chain, and the envelope goes out as them as soon as the last approver signs off. See Sending automatically.

​
Preparing a document for signature

Coverbase maps signer slots using numbered anchor tags placed in the document text, so fields land where your paper puts them rather than where a template guesses. Each signer needs a unique signature anchor and a unique email address. Coverbase validates both before sending, and refuses a document whose anchors are missing rather than producing an envelope with nowhere to sign.
Put the anchor set into your standard MSA, DPA and order-form templates once. Every agreement generated from them is then sendable with no preparation step at all.

​
Connecting your account

Connecting is per person, not per organization. Each sender authorizes Coverbase against their own DocuSign login, so envelopes carry the right sender and your DocuSign permissions apply unchanged.
1

Open a send screen

Go to a contract’s Execution section and click Send to DocuSign, or open a vendor document’s actions menu and choose Send for signature. If you are not connected yet, Coverbase says so and offers Connect DocuSign.
2

Authorize in DocuSign

Clicking Connect DocuSign opens DocuSign in a new tab. Sign in with your normal DocuSign credentials and grant Coverbase access. Coverbase never sees your DocuSign password.
3

Come back

DocuSign returns you to the screen you started from. The send dialog now shows your connected account instead of the connect prompt, and stays connected on your other devices too.
4

Pick the account, if you have several

People who belong to more than one DocuSign account get an account selector. Coverbase preselects the account your organization configured, falls back to your DocuSign default, and lets you change it per send.
If you belong to several DocuSign accounts and your organization has configured one you are not a member of, Coverbase warns you and uses your own default instead of failing the send. Ask your DocuSign administrator to add you to the configured account if envelopes should be raised there.

​
Setting the organization account

An administrator sets which DocuSign account the organization sends from under Configuration → External integrations → DocuSign. This is a default, not a restriction: senders may still pick another account they belong to.

​
Disconnecting

The send dialog’s account card has a Disconnect action. It forgets your grant, so nothing can send as you until you authorize again. Envelopes already in flight are unaffected, and reconnecting takes one authorization round trip.
Connect once, not once per device. Your grant is held against your Coverbase user, so connecting on a laptop is also connected on a phone. Clearing site data does not disconnect you; Disconnect does.
You can only ever send as yourself. Coverbase resolves the DocuSign identity from your own grant, never from anything the screen sends, so no colleague’s account is reachable from your session even if you can edit the contract. A person who has not connected sees the connect prompt rather than somebody else’s account.An automatic send on approval is the one case where an envelope goes out with no browser open, and it is still your own grant: the envelope is sent as the person who set up that send, never as the submitter and never as whichever approver clicked last. Disconnecting stops those too.

​
Keeping status in step

Once an envelope is out, three things keep Coverbase’s copy of its status honest: Ask your Coverbase contact to enable DocuSign Connect for your account if envelope statuses only update when you press Sync status.

​
Onboarding checklist

  1. A DocuSign account with API access enabled (standard on business plans).
  2. Each sender authorizes Coverbase from a send screen, as above.
  3. An administrator sets the organization’s DocuSign account under Configuration → External integrations, if you want a shared default.
  4. Anchor tags added to the document templates you intend to send.
  5. DocuSign Connect enabled, so statuses update without anyone pressing a button.
  6. If you want approvals to send on their own, an approval policy with Send for signature on approval under Settings → Organization → Contract Approvals.

Contract Guardian

Clause review before execution, and re-evaluation on amendment.

Contract intake and approval

Raising a request, confirming its values, and the approval chain before a send.

Contracts workspace

Where the executed agreement lands, and what the record then tracks.

Contract dates and reminders

Notice windows and renewal deadlines derived from the executed paper.

Integration directory

The other CLM and e-signature platforms Coverbase connects with.