Click on the Adobe Acrobat Sign Solutions - Enterprise link in the left-hand rail or products.
What's New
Get Started
- Quick start guide for administrators
- Quick start guide for users
- For Developers
- Video tutorial library
- FAQ
Administer
- Admin Console Overview
- User Management
- Adding users
- Create function-focused users
- Check for users with provisioning errors
- Change Name/Email Address
- Edit a user's group membership
- Edit a user's group membership through the group interface
- Promote a user to an admin role
- User Identity Types and SSO
- Switch User Identity
- Authenticate Users with MS Azure
- Authenticate Users with Google Federation
- Product Profiles
- Login Experience
- Account/Group Settings
- Settings Overview
- Global Settings
- Account tier and ID
- New Recipient Experience
- Self Signing Workflows
- Send in Bulk
- Web Forms
- Custom Send Workflows
- Power Automate Workflows
- Library Documents
- Collect form data with agreements
- Limited Document Visibility
- Attach a PDF copy of the signed agreement
- Include a link in the email
- Include an image in the email
- Files attached to email will be named as
- Attach audit reports to documents
- Merge multiple documents into one
- Download individual documents
- Upload a signed document
- Delegation for users in my account
- Allow external recipients to delegate
- Authority to sign
- Authority to send
- Power to add Electronic Seals
- Set a default time zone
- Set a default date format
- Users in Multiple Groups (UMG)
- Group Administrator Permissions
- Replace recipient
- Audit Report
- In Product Messaging and Guidance
- Accessible PDFs
- New authoring experience
- Healthcare customer
- Account Setup
- Add logo
- Customize company Hostname/URL
- Add company name
- Post agreement URL redirect
- Signature Preferences
- Well formatted signatures
- Allow recipients to sign by
- Signers can change their name
- Allow recipients to use their saved signature
- Custom Terms of Use and Consumer Disclosure
- Navigate recipients through form fields
- Decline to sign
- Allow Stamps workflows
- Require signers to provide their Title or Company
- Allow signers to print and place a written signature
- Show messages when e-signing
- Require signers to use a mobile device to create their signature
- Request IP address from signers
- Exclude company name and title from participation stamps
- Digital Signatures
- Electronic Seals
- Digital Identity
- Report Settings
- New report experience
- Classic report settings
- Security Settings
- Single Sign-on settings
- Remember-me settings
- Login password policy
- Login password strength
- Web session duration
- PDF encryption type
- API
- User and group info access
- Allowed IP Ranges
- Account Sharing
- Account sharing permissions
- Agreement sharing controls
- Signer identity verification
- Agreement signing password
- Document password strength
- Block signers by Geolocation
- Phone Authentication
- Knowledge-Based Authentication (KBA)
- Allow page extraction
- Document link expiration
- Upload a client certificate for webhooks/callbacks
- Timestamp
- Send settings
- Show Send page after login
- Require recipient name when sending
- Lock name values for known users
- Allowed recipient roles
- Allow e-Witnesses
- Recipient groups
- Required fields
- Attaching documents
- Field flattening
- Modify Agreements
- Agreement name
- Languages
- Private messages
- Allowed signature types
- Reminders
- Signed document password protection
- Send Agreement Notification through
- Signer identification options
- Content Protection
- Enable Notarize transactions
- Document Expiration
- Preview, position signatures, and add fields
- Signing order
- Liquid mode
- Custom workflow controls
- Upload options for the e-sign page
- Post-sign confirmation URL redirect
- Message Templates
- Bio-Pharma Settings
- Workflow Integration
- Notarization Settings
- Payments Integration
- Signer Messaging
- SAML Settings
- SAML Configuration
- Install Microsoft Active Directory Federation Service
- Install Okta
- Install OneLogin
- Install Oracle Identity Federation
- SAML Configuration
- Data Governance
- Time Stamp Settings
- External Archive
- Account Languages
- Email Settings
- Migrating from echosign.com to adobesign.com
- Configure Options for Recipients
- Guidance for regulatory requirements
- Accessibility
- HIPAA
- GDPR
- 21 CFR part 11 and EudraLex Annex 11
- Healthcare customers
- IVES support
- "Vaulting" agreements
- EU/UK considerations
- Download Agreements in Bulk
- Claim your domain
- Report Abuse links
Send, Sign, and Manage Agreements
- Recipient Options
- Cancel an email reminder
- Options on the e-signing page
- Overview of the e-sign page
- Open to read the agreement without fields
- Decline to sign an agreement
- Delegate signing authority
- Restart the agreement
- Download a PDF of the agreement
- View the agreement history
- View the agreement messages
- Convert from an electronic to a written signature
- Convert from a written to an electronic signature
- Navigate the form fields
- Clear the data from the form fields
- E-sign page magnification and navigation
- Change the language used in the agreement tools and information
- Review the Legal Notices
- Adjust Acrobat Sign Cookie Preferences
- Send Agreements
- Authoring fields into documents
- In-app authoring environment
- Create forms with text tags
- Create forms using Acrobat (AcroForms)
- Fields
- Authoring FAQ
- Sign Agreements
- Manage Agreements
- Manage page overview
- Delegate agreements
- Replace Recipients
- Limit Document Visibility
- Cancel an Agreement
- Create new reminders
- Review reminders
- Cancel a reminder
- Access Power Automate flows
- More Actions...
- How search works
- View an agreement
- Create a template from an agreement
- Hide/Unhide agreements from view
- Upload a signed agreement
- Modify a sent agreement's files and fields
- Edit a recipient's authentication method
- Add or modify an expiration date
- Add a Note to the agreement
- Share an individual agreement
- Unshare an agreement
- Download an individual agreement
- Download the individual files of an agreement
- Download the Audit Report of an agreement
- Download the field content of an agreement
- Audit Report
- Reporting and Data exports
- Overview
- Grant users access to reporting
- Report charts
- Data Exports
- Rename a report/export
- Duplicate a report/export
- Schedule a report/export
- Delete a report/export
- Check Transaction Usage
Advanced Agreement Capabilities and Workflows
- Webforms
- Reusable Templates (Library templates)
- Transfer ownership of web forms and library templates
- Power Automate Workflows
- Overview of the Power Automate integration and included entitlements
- Enable the Power Automate integration
- In-Context Actions on the Manage page
- Track Power Automate usage
- Create a new flow (Examples)
- Triggers used for flows
- Importing flows from outside Acrobat Sign
- Manage flows
- Edit flows
- Share flows
- Disable or Enable flows
- Delete flows
- Useful Templates
- Administrator only
- Agreement archival
- Webform agreement archival
- Save completed web form documents to SharePoint Library
- Save completed web form documents to OneDrive for Business
- Save completed documents to Google Drive
- Save completed web form documents to Box
- Agreement data extraction
- Agreement notifications
- Send custom email notifications with your agreement contents and signed agreement
- Get your Adobe Acrobat Sign notifications in a Teams Channel
- Get your Adobe Acrobat Sign notifications in Slack
- Get your Adobe Acrobat Sign notifications in Webex
- Agreement generation
- Generate document from Power App form and Word template, send for signature
- Generate agreement from Word template in OneDrive, and get signature
- Generate agreement for selected Excel row, send for review and signature
- Custom Send workflows
- Share users and agreements
Integrate with other products
- Acrobat Sign integrations overview
- Acrobat Sign for Salesforce
- Acrobat Sign for Microsoft
- Other Integrations
- Partner managed integrations
- How to obtain an integration key
Acrobat Sign Developer
- REST APIs
- Webhooks
Support and Troubleshooting
Adobe Acrobat Sign Technical Accounts
Acrobat Sign Technical Accounts are a vehicle to enable enterprise-level accounts with the ability to run their applications under the authority of a userID explicitly generated for that purpose (vs. using the admin’s personal userID).
Technical Accounts are available to enterprise customers (via the Adobe Developers Console) on the ETLA buying plan that manages their account through the Adobe Admin Console.
The product card for technical account access can be found on the Products tab of the Admin Console under the offer name Adobe Acrobat Sign Solutions - Enterprise (Look for the API Available flag):
The below process describes the use of Technical Accounts through an API solution. Organizations that want to enable users to manually send agreements on behalf of a centralized party refer to the document for setting up technical accounts through manual connection.
Prerequisites
To enable a technical account, your Acrobat Sign account must:
- Have enterprise tier ETLA service
- Manage users on the Adobe Admin Console*
- Have Advanced Account Sharing enabled
* A note on the Adobe Admin Console
The Adobe Admin Console provides a framework for user management and license allocation. Most customers have only one Admin Console.
However, some customers with complex user/licensing requirements can have multiple Admin Consoles, which may become confusing in a process like Technical Account creation, where one Admin Console may govern the federated user management, and another manages the Acrobat Sign licensing.
If you know you have multiple accounts or aren't sure, please read the below:
The difficulty with multiple Admin Consoles is ensuring that you are in the correct console for the actions you are trying to perform.
To determine if you have multiple Admin Consoles:
1. Log in to the Admin Console.
2. In the upper-right corner of the console, click on the organization name.
If you have a drop-down menu with multiple organizations, you have multiple Admin Consoles.
If you only have one Admin Console, user creation and licensing operations occur in the same organization, and you don't need to worry about switching between consoles.
If you have multiple Admin Consoles, take a moment to determine which organization manages federated user creation and which governs the Acrobat Sign license provisioning.
Companies with multiple Admin Consoles may deploy Acrobat Sign from more than one. You must identify the correct Admin Console where you want to establish the API connection and Technical Account user.
You should inspect each organization to determine which should contain the technical account.
- Select the organization.
- Select Products from the top rail of options.
- Look for the Adobe Sign - Enterprise product card with the API available flag.
For the purpose of this document, we will call this your Licensing Admin Console. This is the organization where:
- You define the admin or developer user that will connect the API.
- Your technical account user is created and managed.
Organizations that use federated user management must de-sync the federated solution to create a user outside of the federated environment.
To do this, you must inspect each organization to find which one controls the domains that enable the federated trust relationship. Multiple Admin Consoles can Trust a domain, but only one actively controls it.
- Select the orgnaization
- Select Settings from the top rail of options.
- Select Identity from the left rail of options.
- If there are directories listed with the Type being Federated ID and the Status is Trusted, click the row the directory is on to expose the Owning Organization.
The Owning Organization is the correct Admin Console to manipulate your federated ID synchronization controls.
- An email is provided for the console admin if you do not currently have access.
If the Type is Federated ID and the Status is Active, click the Name of the directory to open the directory settings.
On the settings page, select the Sync tab, which opens the IDP sync information.
For the purpose of this document, we will call this your Federated Sync Admin Console.
If you do not see a Sync tab, your account may have a Global Admin Console that you do not have access to.
You will need to contact your internal Adobe administrators to gain access.
Organizations that
- utilize the User Sync Tool (UST) to automatically sync users between Adobe and their Active Directory
- do not allow users to be manually added or created in Acrobat Sign
must create an "exception" group for all Technical Account userIDs. All Technical Account userIDs must have their primary group defined as the exempt group to ensure they are not deactivated and do not have their license removed by the automatic user sync.
The exception group must be configured as exempt from the sync within the UST configuration.
In cases where Adobe hosts the UST on behalf of the customer's organization, the customer admin must communicate the Group Name to their Success Manager, Technical Account Manager, or account representative so they can work with the Adobe Customer Solutions team to ensure this group is exempt from the sync.
Overview
Creating a technical account is a multi-step process that requires administrator-level access to the Adobe Acrobat Console and account-level administrator authority in Acrobat Sign.
The process requires the admin:
- Enable admin or developer access for the user creating the technical account.
- The user must be an admin or developer to configure the settings that create the technical account.
- Create a new Project on the Adobe Developer Console (Adobe.io).
- The project is the required environment to hold the public/private key pair and access token that enables the functionality of the technical account.
- Create or Upload a public/private key pair and generate an access token.
- Generating the access token creates the technical account userID in the Adobe Admin Console and populates it into the Acrobat Sign system.
- Generating the access token creates the technical account userID in the Adobe Admin Console and populates it into the Acrobat Sign system.
- (Optional) Create a new Group in the Acrobat Sign system.
- Creating a dedicated group for the technical account userID allows a very tight configuration of the agreement properties that may be too strict or different from other group configurations.
- Privilege the technical account userID in Acrobat Sign as a group-level administrator.
- Create a new Federated user in the Adobe Admin Console.
- This creates a user email with your domain to proxy for the technical account useID when sending, providing an email address that is properly attributed to your company.
- This creates a user email with your domain to proxy for the technical account useID when sending, providing an email address that is properly attributed to your company.
- Share the Federated user's account with the technical account.
- The technical account userID is generated in the Licensing Admin Console with an adobe.com email address. By sharing the Federated user's account, you grant access to the technical account userID to send on behalf of the Federated userID, thereby providing a more human-friendly name/email address for the recipients.
When completed, the API can be configured to use the technical account (via access code) to create and send agreements on behalf of a centralized user.
-
Navigate to https://console.adobe.io
- If you belong to multiple Admin Console instances, make sure you are connected to the instance that aligns with your Licensing Admin Console by clicking the down arrow in the top-right corner of the window.
- If you belong to multiple Admin Console instances, make sure you are connected to the instance that aligns with your Licensing Admin Console by clicking the down arrow in the top-right corner of the window.
You have the option to generate a new public/private key pair or to upload your public key. Choose the option that best suits your needs:
Select the product profile
The Configure API page refreshes to show the product profile(s) available for your account. You may have one or more depending on the profiles available to your account.
- Select the check box for your Default Adobe Acrobat Sign Solutions - Enterprise.
- Save Configured API when ready.
-
Clone the following repo: https://github.com/AdobeDocs/adobeio-auth/tree/stage/JWT/samples/adobe-jwt-java
Consider generating a unique group in Acrobat Sign for the application
Acrobat Sign groups allow for granular configuration of the security and experience settings for the recipient (as well as workflows, templates, reporting, etc.)
If you want to isolate the technical account userID in their own group:
If your organization is
- using the User Sync Tool (UST) to automatically sync users between Adobe and your Active Directory
- not permitting users to be manually added or created in Acrobat Sign
you must create an exception group to be the primary group for all Technical Account userIDs.
The name of the group is added to your UST configuration to ensure the sync process does not impact the userIDs, causing them to be deactivated or to have their entitlement removed.
-
Search for the new techacct.adobe.com email address (copied from the project home page).
Create a Reply-To user/email
Sending agreements using the userID/email tied to the technical account is problematic due to the email not being within your company domain.
To solve this issue:
- A new federated userID has to be created in the Licensing Admin Console.
- The technical account userID has to be shared with the new federated userID (via advance account sharing).
Once configured, the API calls must be configured to use the technical account token as the Authorization value, and the userId or email of the shared userID as the x-on-behalf-of-user value.
-
Log in to your (Federated Sync) Admin Console as an administrator.
-
Log in to your Licensing Admin Console (if you are working with multiple Admin Consoles).
-
Configure your new userID with:
- Email or username: Use the email address that you want to capture any reply-to eamils from your recipients.
- ID Type: Federated ID
- First/Last name: this value is used in the Acrobat Sign system and is reflected in the audit report. USe a value that provides context. e.g.: Human Resources
- SSO username: Use the same email value.
- Country/Region: Select the appropriate country or region for your company.
- Select the Acrobat Sign product/profile that the technical userID is associated with.
- Set the users role to User.
Click Save when done.
-
Share the new userID's account with the technical account
- Click the plus icon in the top right row to open the selector interface.
- Click the three lines icon to the right of the search box.
- Expand the group where the technical account userID resides.
- Click the plus icon next to the technical account userID to select it.
- Check the Additional Permission to allow Sending.
- Click Save.
Test your new technical account
To test that your access code is functioning correctly:
-
Navigate to the API methods: https://secure.na1.adobesign.com/public/docs/restapi/v6
-
Navigate to the API methods: https://secure.na1.adobesign.com/public/docs/restapi/v6
Test sending an agreement using the technical account on behalf of the new userID via API
-
Navigate to the API methods: https://secure.na1.adobesign.com/public/docs/restapi/v6#!/agreements/createAgreement
-
In the Authorization field:
- Type in the word Bearer followed by a space
- Paste in the technical account's Access Token
- In the x-on-behalf-of-user field, enter the email address of the new userID
- Complete the rest of the AgreementInfo with the transientDocumentId, name of the agreement, signature type, and state.
- Click Try it out!
Review the content generated on behalf of the new userID via the Acrobat Sign interface
When the technical account creates an agreement on behalf of the Federated userID, the agreement is published to the Federated userID's Manage page.
It is on the Federated UserIDs Manage page that you can view and manage the agreement.