Adobe Sign Integration

Modified on Wed, 15 Jul at 5:39 PM

Adobe Sign can be connected to CLM so your team can send documents for signature directly from the platform. Unlike the previous method (which relied on sharing an Adobe Integration Key / API key), the setup now uses a secure OAuth consent flow — no key to generate or share by email.

The setup happens in two steps: a one-time feature flag activation on the DiliTrust side, then a one-time authorization performed by a single administrator who has access to both the CLM configuration and the Adobe Sign account. Once authorized, the connection applies to the whole tenant — individual senders do not need to authorize anything themselves.


⭐ Prerequisites

  • An active Adobe Sign account 
  • We recommend authorizing the integration with a technical / service account rather than a personal one — this prevents the connection from breaking if the account owner leaves the company
  • One license is enough to authorize the integration

⚙️ Step 1 — Feature flag activation (DiliTrust side)

Before Adobe Sign appears in your CLM environment, a feature flag must be activated on your tenant. This is handled by the DiliTrust team — reach out to your Customer Success manager to request it.

Note: this step is currently done manually by DiliTrust and is not self-service.


⚡ Step 2 — Authorization (performed once by an administrator)

Once the flag is active, a single administrator who has access to both the CLM configuration and the Adobe Sign account grants access from the CLM administration. This is not required from each sender — once done, Adobe Sign is available for the whole tenant:

  • Go to Configuration → Electronic Signature on the left menu
  • Select Adobe Sign from the list of available provider
  • Click Authorize— you'll be redirected to the Adobe Sign login page

  • Log in with the Adobe Sign account and grant the requested permissions

  • Once consent is given, you're redirected back to CLM and Adobe Sign is ready to use


✅ Verifying the setup

After completing the consent step, Adobe Sign should appear as an available provider when you send a document for signature.


ℹ️ Good to know

  • The connection is tied to the account that granted consent — using a technical account keeps it stable over time
  • There is always a default provider defined at the tenant level; assigning Adobe Sign to a specific user is optional. See How to set up your provider — CLM →
  • The authorization must be renewed periodically. Adobe Sign consent relies on a refresh token that expires (roughly every 2 months). When it approaches expiry, an authorized user simply clicks Authorize again. The screen displays the current status ("Authorization granted, no need for further action") along with the token renewal and expiry dates, so you can check at a glance whether action is needed.

Related articles


Need help connecting Adobe Sign? Contact your DiliTrust Customer Success manager.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article