Enable auto-provisioning for new users on the Adobe platform

This page provides information for Adobe Acrobat Sign administrators who manage Acrobat Sign users and licenses on Adobe’s enterprise platform, Adobe Admin Console.

If an organization is managing Acrobat Sign on the Adobe Admin Console and integrating Acrobat Sign into partner applications, the administrator can further configure Acrobat Sign so that end users are auto-provisioned into the Acrobat Sign account from within the partner application.

Typically, end-users are provided access to an organization's Acrobat Sign account when an administrator adds the end-user to the Acrobat Sign entitlement in the Admin Console. The end-user can then send agreements from within the Acrobat Sign partner integration OR by utilizing the Acrobat Sign web application or the Acrobat  Sign mobile application.

However, auto-provisioning allows the end-user to be added to the Acrobat Sign account simply by initiating a signing workflow from within the partner application.

This capability is available to all customers who are on the Acrobat Sign enterprise plans.

This capability is available from within the following Acrobat Sign partner applications:

• Salesforce
• Microsoft Dynamics
• Microsoft SharePoint
• Oracle Netsuite

Support for additional Acrobat Sign partner applications is expected over time.

Enable Auto-Provisioning for Acrobat Sign Partner Applications

Enable Auto-Provisioning within the Acrobat Sign web application

Enable Auto-Provisioning within Acrobat Sign Partner Application

The admin must ensure that auto-provisioning is enabled within the Acrobat Sign partner application as well.

Further details can be found within the applicable Acrobat Sign partner integration guide.

Currently, supported applications are:

• Salesforce
• Microsoft Dynamics
• Microsoft SharePoint
• Oracle Netsuite

Result of Auto-Provisioning within Admin Console

The new user is created in the Admin Console

• When a user accesses Acrobat Sign (for the first time) within the Acrobat Sign partner application, they are created as a new user within the Admin Console AND are provisioned with an Acrobat Sign license
  • If the user already exists within the Admin Console, they are only provisioned with an Acrobat Sign license
    • If the user already exists within the Admin Console and is already provisioned with an Acrobat Sign license, no change takes place
    • The Acrobat Sign license may be upgraded to Acrobat Sign enterprise in the case where the user was on a lower Acrobat Sign plan
      
• The user is created with an Adobe identity type based on how the organization is configured within the Admin Console:
  • If the organization has set up Federated ID for a claimed domain/directory and enabled SSO/SAML, AND if the end user's email matches this claimed domain, then the new end-user is added as a Federated ID user
  • If the organization has set up Enterprise ID for a claimed domain/directory (and not enabled SSO/SAML), AND if the end user's email matches this claimed domain, then the new end-user is added as an Enterprise ID user
  • Otherwise, the end-user is added as a Business ID user or an Adobe ID user

The new user is entitled with an Acrobat Sign license

When the user is assigned to the Acrobat Sign product within the Admin Console, the user is granted a license to use the Acrobat Sign service.

• The user is added to the Acrobat Sign product profile which was configured on the Acrobat Sign Integrations Settings page

End User experience within the Acrobat Sign Partner Application

For an Federated ID / Enterprise ID end user

Adobe recommends that organizations enable Federated ID for their end-users, for a variety of reasons. The advantage of Federated and Enterprise ID during this auto-provisioning workflow is that the end-users get immediate access to use Acrobat Sign within the partner application without having to provide any consent or experiencing any delay in using Acrobat Sign.

• Enterprise ID users are prompted to create a password the first time they sign in to the Adobe Acrobat Sign web application (or any Adobe website).
• Federated ID users are never prompted to create a password because Adobe will use the organization's SSO / SAML Identity Provider.

For a Business ID/Adobe ID end user

Business ID and Adobe ID users are not able to immediately use Acrobat Sign within the partner application.

An error message within the Acrobat Sign partner application is triggered (with an accompanying email) to complete the process of joining the Acrobat Sign account (establishing a password if they do not already have one).

Once the end-user completes the process of joining the Acrobat Sign account, they are then able to use Acrobat  Sign within the partner application.

Common Issues and how to resolve