How to set Adobe Sign credentials for your Team (P2/Conversations)

From your left navigation toolbar click on “My Team” and scroll down to “Edit Your Adobe Sign feature configuration” and click Authorize Botdoc. Only the Team OWNER will have access to these credential fields.

Once you click on Authorize Botdoc, this will take you to the Adobe sign-in page where you will enter your email address and password for your Adobe account.

Next, you will be asked to CONFIRM access -Once confirmed then you will have Adobe Access within your P2/Conversations dashboard.

When all credentials are completed you will now see the Adobe Sign button within the P2 container in the Feature selection menu (if credentials are not working correctly the Adobe Sign button will not show)

Note: Consumer side/Customer Signed docs - PDFs will be available to download via the request link immediately. (Pdf’s will not be emailed to any parties including the signers)

Any subscription level will work inside your Botdoc P2 however, here is additional help:

(Developer Level Subscription) - How to enable oAuth in Adobe Sign Account

Tips:

  • Security settings for “uncertified apps” must be disabled

  • (API Only) Sandbox environment will use an Uncertified Adobe Sign application (“allow uncertified apps” must be enabled) - Botdoc provides a sandbox environment, so users can test integration free of charge. In order to write a sandbox integration with Adobe Sign, users must use a Developer Account with Adobe Sign and enable the “Allow Uncertified Apps” setting inside Adobe Sign settings

  • Form Field Templates are reusable layers of fields that can be applied to any document - Available

  • Delegate another to sign is “disabled”

  • Emails are required when sending to mobile (SMS)

  • Recipients can download in real-time onscreen and will not receive a follow-up email for downloading

PRO DC Single/Personal level Subscription -

Tips:

Team level Subscriptions -

Tips:

NEED TO KNOW:

  • Safari server error – when signing via SMS/Mobile

    • An error will randomly happen when sending multiple Adobe Signs on the same day to the same recipient

    • This is a known Adobe error that will not stop the signing process (the browser’s locally cached version is getting stuck)

    • Recipients can X out of the error if the error remains onscreen

FULL VIEW CLICK HERE