Admin, Security & Settings · Synthetic Property 1

External Systems & Add-ons

Customer-configurable optional connections and paid add-ons.

Marketplace Connections Setup Guide Credentials Mapping Tests Health Operations Entitlements API Keys & Webhooks Usage

Setup guide · External E-Signature / Trust Service

Agreements; authentication; signatures; notary evidence

What you need first

An e-signature account and permission to let another app send documents for signing.

Find your provider's instructions for the keys (opens a web search). Look for words like API keys, integrations or developer settings in your provider's admin area.

If you don't have a provider yet, the built-in feature keeps working. Your own provider's help is the source of truth.

The steps

Open External Systems & Add-ons, Marketplace and choose External E-Signature / Trust Service.
Get the details above from your provider. Keep them private; never put them in a message or note.
Paste them into the connection form. They are stored separately for Test and Live.
Allow only what this connection needs: Agreements; authentication; signatures; notary evidence.
Match your provider's names to ours on the Mapping tab, then press Test.
It shows Connected only after the test passes. Watch its Health, and use Safe Disable to turn it off at any time.

Technical steps from the build package

Settings > External Systems & Add-ons > Marketplace: activate External E-Signature / Trust Service (paid add-on where applicable).
Enter the credentials your provider gives you (kept separate per environment).
Grant only these permissions: Agreements; authentication; signatures; notary evidence.
Map codes and fields on the Mapping tab.
Run Test; status becomes Connected only after a pass.
Watch Health; use Safe Disable to turn it off.

Without this connection: Internal document workflow remains complete.

Degraded: warnings, partial sync, fallback for impaired functions. Down: Internal document workflow remains complete; queued writes replay safely on recovery.