Applicable Role: Administrator

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

Pastaba:

Some Adobe Sign accounts instead manage Sign users and licenses within the Sign application itself. This alternate method of managing users and licenses is documented here.

Introduction to Adobe Sign on Admin Console

Admin Console versus Adobe Sign application

When managing a Sign account on the Admin Console, the Sign Admin can access two distinct administrative environments: 1) the Admin Console, and 2) the Sign application. The Sign administrator may have access to one or both of these administrative environments, depending on the choice of the organization. Each of these administrative environments provide different functions.

In the Admin Console, an administrator can manage users and user access to licenses across all Adobe products and services. See here for more information on Admin Console. For a Sign administrator, Admin Console functionality includes:

  • Create initial Sign administrator(s).
  • Give administrators and end users access to Sign.
  • Create / edit Product Profiles for Sign, including adding users to Product Profiles.
  • Create / edit Admin Console user groups (for assigning an Admin Console user group to a Sign Product Profile).
  • Setting up single-sign-on / SAML for end user access to Sign (if applicable).
  • ...and more.

In the Sign application, a Sign administrator can manage the features, functionality, and behavior of Adobe Sign. To be an administrator within the Sign application, a user must first be granted access to Adobe Sign in the Admin Console (see Step 1 of "Setting Up an Adobe Sign Account" below). See here and here for more information on admin functionality in Sign application. For a Sign administrator, functionality in the Sign application includes:

  • Create / edit Sign user groups (for customizing how Sign behaves for different user groups). See "Set up Sign user groups" below for more information.
  • Configure signature preferences
  • Upload custom logo 
  • Configure global settings
  • Configure security settings
  • ...and more

User versus transaction licenses

Sign plans can be purchased as a per user or a per transaction plan. The plan type determines how Sign appears in the Admin Console.

Per-User License Plan
Per-User License Plan
Per-Transaction License Plan
Per-Transaction License Plan

In the Admin Console, an administrator can see some information on the number of users or transactions associated with their Sign plan. However, for a more detailed Sign usage report, a Sign administrator can click "Manage Adobe Sign" in Admin Console. From here, they can run reports within the Sign application. See “Reporting on Sign Usage” below for more information.

Setting up an Adobe Sign account

Below is an outline of the steps to set up an Adobe Sign account on the Admin Console. The first administrator is given access to the Admin Console where the Sign product appears. At this point, the administrator can follow these steps:

  1. Create Sign administrators

    The system administrator should begin by creating an initial Sign administrator. This initial Sign administrator may be themself or someone else in their organization. The initial Sign administrator must be both an Admin Console system administrator and have access to the Sign product in Admin Console. This initial Sign administrator is the individual who manages the overall Sign usage within the organization, including granting access to Sign to end users and configuring the Sign application.

    The detailed steps and options for creating Sign administrators are here.

  2. Set up the Sign account

    Before adding end users to the Sign account, a Sign administrator can configure the Sign account so that it is aligned with how the organization wants their end users to use the Sign application. This could include configuring Sign preferences or behaviors, configuring security settings, customizing emails sent by Sign, and more.

    An overview for the Sign administrator regarding how to set up the Sign account can be found here.

  3. Set up Sign user groups and Sign group admins

    Dividing your Sign users into functional groups is helpful if you have different signature requirements or different reporting structures which need to be observed. As noted above, Sign user groups are distinct from Admin Console user groups. Initially, when an end user or administrator is granted access to Sign in the Admin Console, that user is placed into Sign’s Default user group. However, a Sign administrator can move that user to any Sign user group. Additionally, a Sign user can be designated as a Sign group administrator to customize the functionality for that particular Sign user group.

    An overview of user groups can be found here.

    Sign User Groups
    Sign User Groups
  4. Add Sign users

    Finally, a Sign administrator can add end users to the Sign account within the Admin Console. This works similarly to adding users to other Adobe products and services. See here for instructions on adding users.

    Add Sign users in Admin Console
    Add Sign users in Admin Console

Using the Adobe Sign account

Now that your Sign account has been set up, end users are ready to start using the Sign application. See this page for user guides and tutorials on how to use the Sign application. There is also a video on how to send with Sign, as well as a list of frequent topics.

Additional considerations regarding Adobe Sign on Admin Console

Depending on how the Sign account is being used, these additional considerations regarding Sign on Admin Console may be relevant.

Setting up Adobe Sign partner integrations

Adobe Sign can be managed on Admin Console and can then be integrated within a number of partner applications. See here for a complete list of supported partner applications and detailed instructions on how to complete an integration.

When Sign is managed on the Admin Console, an end user must be given explicit access to the Sign account (via the Admin Console) before they can use Sign within a partner application. See Step 4 of "Setting up an Adobe Sign Account" above for instructions on how to add Sign users to the Sign account in Admin Console. Currently, Sign managed on Admin Console does not support auto-provisioning for users using Sign within a partner application.

Reporting on Adobe Sign usage

To check the Adobe Sign transaction consumption and run detailed reports on usage, follow the steps below. Additional details on Sign reporting can be found here.

  1. Navigate to Reports and click Create a new report.

    Create New Report
  2. To get detailed consumption reports, adjust values for the filters and click Run Report.

    Run Report
  3. A graphical report is shown as per the set filters. You can export the report in CSV format by clicking Export Report Data.

    Pastaba:

    Some graphs are not available for non-English languages.

    Reports

Common Issues

The following are a list of issues which an administrator or end user may encounter when using Adobe Sign.

End user cannot log into Adobe Sign

Issue: After an end user is added to the Sign account within Admin Console, they are still unable to log in successfully to Adobe Sign.

Possible Cause: It is possible that the end user’s email address is already associated with another Sign account which is preventing them from accessing the new Sign account.

Resolution Options:

  • Resolution 1 – Use a different email address when adding the end user to the Sign account within Admin Console
  • Resolution 2 – Determine if the end user is receiving any prompts or instructions when logging into Sign. Sign can often prompt the end user to de-associate their email address with the prior Sign account so it can be re-associated with the new Sign account.
  • Resolution 3 – Contact Adobe Customer Care via the Admin Console “Support” tab. More information on contacting Support is here.

Šis darbas yra licencijuotas pagal licenciją „Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License“  „Twitter™“ ir „Facebook“ skelbimams „Creative Commons“ sąlygos netaikomos.

Teisiniai pranešimai   |   Privatumo internete politika