User Guide Cancel

Create Technical Accounts to send agreements via API

 

Adobe Acrobat Sign Guide

What's New

  1. Pre-Release Notes
  2. Release Notes
  3. Important Notifications

Get Started

  1. Quick start guide for administrators
  2. Quick start guide for users
  3. For Developers
  4. Video tutorial library
  5. FAQ

Administer

  1. Admin Console Overview
  2. User Management
    1. Adding users
      1. Add a User
      2. Add Users in Bulk
      3. Add Users from your Directory
      4. Add Users from MS Azure Active Directory
    2. Create function-focused users
      1. Technical accounts - API driven
      2. Service accounts - Manually driven
    3. Check for users with provisioning errors
    4. Change Name/Email Address
    5. Edit a user's group membership
    6. Edit a user's group membership through the group interface
    7. Promote a user to an admin role
    8. User Identity Types and SSO
    9. Switch User Identity
    10. Authenticate Users with MS Azure
    11. Authenticate Users with Google Federation
    12. Product Profiles
    13. Login Experience 
  3. Account/Group Settings
    1. Settings Overview
    2. Global Settings
      1. Account tier and ID
      2. New Recipient Experience
      3. Self Signing Workflows
      4. Send in Bulk
      5. Web Forms
      6. Custom Send Workflows
      7. Power Automate Workflows
      8. Library Documents
      9. Collect form data with agreements
      10. Limited Document Visibility
      11. Attach a PDF copy of the signed agreement 
      12. Include a link in the email
      13. Include an image in the email
      14. Files attached to email will be named as
      15. Attach audit reports to documents
      16. Merge multiple documents into one
      17. Download individual documents
      18. Upload a signed document
      19. Delegation for users in my account
      20. Allow external recipients to delegate
      21. Authority to sign
      22. Authority to send
      23. Power to add Electronic Seals
      24. Set a default time zone
      25. Set a default date format
      26. Users in Multiple Groups (UMG)
        1. Upgrade to use UMG
      27. Group Administrator Permissions
      28. Replace recipient
      29. Audit Report
        1. Overview
        2. Allow unauthenticated access on the transaction verification page
        3. Include reminders
        4. Include view events
        5. Include agreement page/attachment count
      30. Transaction Footer
      31. In Product Messaging and Guidance
      32. Accessible PDFs
      33. New authoring experience
      34. Healthcare customer
    3. Account Setup
      1. Add logo
      2. Customize company Hostname/URL    
      3. Add company name
      4. Post agreement URL redirect
    4. Signature Preferences
      1. Well formatted signatures
      2. Allow recipients to sign by
      3. Signers can change their name
      4. Allow recipients to use their saved signature
      5. Custom Terms of Use and Consumer Disclosure
      6. Navigate recipients through form fields
      7. Restart agreement workflow
      8. Decline to sign
      9. Allow Stamps workflows
      10. Require signers to provide their Title or Company
      11. Allow signers to print and place a written signature
      12. Show messages when e-signing
      13. Require signers to use a mobile device to create their signature
      14. Request IP address from signers
      15. Exclude company name and title from participation stamps
    5. Digital Signatures
      1. Overview
      2. Download and sign with Acrobat
      3. Sign with Cloud Signatures
      4. Include metadata for Identity Providers
      5. Restricted Cloud Signatures Providers
    6. Electronic Seals
    7. Digital Identity
      1. Digital Identity Gateway
      2. Identity Check policy
    8. Report Settings
      1. New report experience
      2. Classic report settings
    9. Security Settings
      1. Single Sign-on settings
      2. Remember-me settings
      3. Login password policy
      4. Login password strength
      5. Web session duration
      6. PDF encryption type
      7. API
      8. User and group info access
      9. Allowed IP Ranges
      10. Account Sharing
      11. Account sharing permissions
      12. Agreement sharing controls
      13. Signer identity verification
      14. Agreement signing password
      15. Document password strength
      16. Block signers by Geolocation
      17. Phone Authentication
      18. Knowledge-Based Authentication (KBA)
      19. Allow page extraction
      20. Document link expiration
      21. Upload a client certificate for webhooks/callbacks
      22. Timestamp
    10. Send settings
      1. Show Send page after login
      2. Require recipient name when sending
      3. Lock name values for known users
      4. Allowed recipient roles
      5. Allow e-Witnesses
      6. Recipient groups
      7. CCs
      8. Recipient Agreement Access
      9. Required fields
      10. Attaching documents
      11. Field flattening
      12. Modify Agreements
      13. Agreement name
      14. Languages
      15. Private messages
      16. Allowed signature types
      17. Reminders
      18. Signed document password protection
      19. Send Agreement Notification through
      20. Signer identification options
        1. Overview
        2. Signing password
        3. One-Time Password via Email
        4. Acrobat Sign authentication
        5. Phone authentication
        6. Cloud-based digital signature
        7. Knowledge-based authentication
        8. Government ID
        9. Signer Identity reports
      21. Content Protection
      22. Enable Notarize transactions
      23. Document Expiration
      24. Preview, position signatures, and add fields
      25. Signing order
      26. Liquid mode
      27. Custom workflow controls
      28. Upload options for the e-sign page
      29. Post-sign confirmation URL redirect
    11. Message Templates
    12. Bio-Pharma Settings
      1. Overview
      2. Enforce identity authentication
      3. Signing reasons
    13. Workflow Integration
    14. Notarization Settings
    15. Payments Integration
    16. Signer Messaging
    17. SAML Settings
      1. SAML Configuration
      2. Install Microsoft Active Directory Federation Service
      3. Install Okta
      4. Install OneLogin
      5. Install Oracle Identity Federation
    18. Data Governance
    19. Time Stamp Settings
    20. External Archive
    21. Account Languages
    22. Email Settings
      1. Email header/footer images
      2. Permit individual user email footers
      3. Customize the Signature Requested email
      4. Customize the To and CC fields
      5. Enable Linkless Notifications
      6. Customize email templates
    23. Migrating from echosign.com to adobesign.com
    24. Configure Options for Recipients
  4. Guidance for regulatory requirements
    1. Accessibility
      1. Accessibility Compliance
      2. Create accessible forms with Acrobat desktop
      3. Create accessible AcroForms
    2. HIPAA
    3. GDPR
      1. GDPR Overview
      2. Redact a user
      3. Redact a user's agreements    
    4. 21 CFR part 11 and EudraLex Annex 11
      1. 21 CRF part 11 validation pack
      2. 21 CFR and EudraLex Annex 11 handbook
      3. Analysis of shared responsibilities
    5. Healthcare customers
    6. IVES support
    7. "Vaulting" agreements
    8. EU/UK considerations
      1. EU/UK Cross-border transactions and eIDAS
      2. HMLR requirements for deeds signed electronically
      3. The impact of Brexit on e-signature laws in the UK
  5. Download Agreements in Bulk
  6. Claim your domain 
  7. Report Abuse links

Send, Sign, and Manage Agreements

  1. Recipient Options
    1. Cancel an email reminder
    2. Options on the e-signing page
      1. Overview of the e-sign page
      2. Open to read the agreement without fields
      3. Decline to sign an agreement
      4. Delegate signing authority
      5. Restart the agreement
      6. Download a PDF of the agreement
      7. View the agreement history
      8. View the agreement messages
      9. Convert from an electronic to a written signature
      10. Convert from a written to an electronic signature 
      11. Navigate the form fields
      12. Clear the data from the form fields
      13. E-sign page magnification and navigation
      14. Change the language used in the agreement tools and information
      15. Review the Legal Notices
      16. Adjust Acrobat Sign Cookie Preferences
  2. Send Agreements  
    1. Send page overview
    2. Send an agreement only to yourself
    3. Send an agreement to others
    4. Written Signatures
    5. Recipient signing order
    6. Send in Bulk
      1. Overview of the Send in Bulk feature
      2. Send in Bulk - Configure a parent template
      3. Send in Bulk - Configure the CSV file
      4. Cancel a Send in Bulk transaction
      5. Add reminders to Send in Bulk
      6. Reporting for Send in Bulk
  3. Authoring fields into documents
    1. In-app authoring environment
      1. Automatic field detection
      2. Drag and drop fields using the authoring environment
      3. Assign form fields to recipients
      4. The Prefill role
      5. Apply fields with a reusable field template
      6. Transfer fields to a new library template
      7. Updated authoring environment when sending agreements
    2. Create forms with text tags
    3. Create forms using Acrobat (AcroForms)
      1. AcroForm creation
      2. Creating accessible PDFs
    4. Fields
      1. Field types
        1. Common field types
        2. In-line Images
        3. Stamp Images
      2. Field content appearance
      3. Field validations
      4. Masked fields values
      5. Setting show/hide conditions
      6. Calculated fields 
    5. Authoring FAQ
  4. Sign Agreements
    1. Sign agreements sent to you
    2. Fill & Sign
    3. Self-signing
  5. Manage Agreements
    1. Manage page overview
    2. Delegate agreements
    3. Replace Recipients
    4. Limit Document Visibility 
    5. Cancel an Agreement 
    6. Create new reminders
    7. Review reminders
    8. Cancel a reminder
    9. Access Power Automate flows
    10. More Actions...
      1. How search works
      2. View an agreement
      3. Create a template from an agreement
      4. Hide/Unhide agreements from view
      5. Upload a signed agreement
      6. Modify a sent agreement's files and fields
      7. Edit a recipient's authentication method
      8. Add or modify an expiration date
      9. Add a Note to the agreement
      10. Share an individual agreement
      11. Unshare an agreement
      12. Download an individual agreement
      13. Download the individual files of an agreement
      14. Download the Audit Report of an agreement
      15. Download the field content of an agreement
  6. Audit Report
  7. Reporting and Data exports
    1. Overview
    2. Grant users access to reporting
    3. Report charts
      1. Create a new report
      2. Agreement Reports
      3. Transaction Reports
      4. Settings Activity Report
      5. Edit a report
    4. Data Exports 
      1. Create a new data export
      2. Web form data export
      3. Edit a data export
      4. Refresh the data export content
      5. Download the data export
    5. Rename a report/export
    6. Duplicate a report/export
    7. Schedule a report/export
    8. Delete a report/export
    9. Check Transaction Usage

Advanced Agreement Capabilities and Workflows

  1. Webforms 
    1. Create a web form
    2. Edit a web form
    3. Disable/Enable a web form
    4. Hide/Unhide a web form
    5. Find the URL or script code 
    6. Prefill web form fields with URL parameters
    7. Save a web form to complete later
    8. Resize a web form
  2. Reusable Templates (Library templates) 
    1. US Government forms in the Acrobat Sign library
    2. Create a library template
    3. Change a library template's name
    4. Change a library template's type
    5. Change a library template's permission level
    6. Copy, edit, and save a shared template
    7. Download the aggregate field data for a library template
  3. Transfer ownership of web forms and library templates
  4. Power Automate Workflows 
    1. Overview of the Power Automate integration and included entitlements
    2. Enable the Power Automate integration
    3. In-Context Actions on the Manage page
    4. Track Power Automate usage
    5. Create a new flow (Examples)
    6. Triggers used for flows
    7. Importing flows from outside Acrobat Sign
    8. Manage flows
    9. Edit flows
    10. Share flows
    11. Disable or Enable flows
    12. Delete flows
    13. Useful Templates
      1. Administrator only
        1. Save all completed documents to SharePoint
        2. Save all completed documents to OneDrive for Business
        3. Save all completed documents to Google Drive
        4. Save all completed documents to DropBox
        5. Save all completed documents to Box
      2. Agreement archival
        1. Save your completed documents to SharePoint
        2. Save your completed documents to One Drive for Business
        3. Save your completed documents to Google Drive
        4. Save your completed documents to DropBox
        5. Save your completed documents to Box
      3. Webform agreement archival
        1. Save completed web form documents to SharePoint Library
        2. Save completed web form documents to OneDrive for Business
        3. Save completed   documents to Google Drive
        4. Save completed web form documents to Box
      4. Agreement data extraction
        1. Extract form field data from your signed document and update Excel sheet
      5. Agreement notifications
        1. Send custom email notifications with your agreement contents and signed agreement
        2. Get your Adobe Acrobat Sign notifications in a Teams Channel
        3. Get your Adobe Acrobat Sign notifications in Slack
        4. Get your Adobe Acrobat Sign notifications in Webex
      6. Agreement generation
        1. Generate document from Power App form and Word template, send for signature
        2. Generate agreement from Word template in OneDrive, and get signature
        3. Generate agreement for selected Excel row, send for review and signature
  5. Custom Send workflows
    1. Custom Send Workflow Overview
    2. Creating a new Send Workflow
    3. Edit a Send Workflow
    4. Activate or Deactivate a Send Workflow
    5. Send an agreement with a Send Workflow
  6. Share users and agreements
    1. Share a user
    2. Share agreements

Integrate with other products

  1.  Acrobat Sign integrations overview 
  2. Acrobat Sign for Salesforce
  3. Acrobat Sign for Microsoft
    1. Acrobat Sign for Microsoft 365
    2. Acrobat Sign for Outlook
    3. Acrobat Sign for Word/PowerPoint
    4. Acrobat Sign for Teams
    5. Acrobat Sign for Microsoft PowerApps and Power Automate
    6. Acrobat Sign Connector for Microsoft Search
    7. Acrobat Sign for Microsoft Dynamics 
    8. Acrobat Sign for Microsoft SharePoint 
  4. Other Integrations
    1. Acrobat Sign for ServiceNow
    2. Acrobat Sign for HR ServiceNow
    3. Acrobat Sign for SAP SuccessFactors
    4. Acrobat Sign for Workday
    5. Acrobat Sign for NetSuite
    6. Acrobat Sign for VeevaVault
    7. Acrobat Sign for Coupa BSM Suite
  5. Partner managed integrations
  6. How to obtain an integration key

Acrobat Sign Developer

  1. REST APIs 
    1. Methods documentation
    2. SDK/Developer Guide
    3. API FAQ    
  2. Webhooks 
    1. Webhook overview
    2. Configure a new webhook
    3. View or edit a webhook
    4. Deactivate or reactivate a webhook
    5. Delete a webhook
    6. Two-way SSL certificates
    7. Webhooks in the API

Support and Troubleshooting

  1. Customer Support Resources 
  2. Enterprise Customer Success Resources 

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):

Tech Account product cards

Note:

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.

Admin Console organization drop down

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.

  1. Select the organization.
  2. Select Products from the top rail of options.
  3. 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.
Tech Account product cards

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.

  1. Select the orgnaization
  2. Select Settings from the top rail of options.
  3. Select Identity from the left rail of options.
  4. 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.
Navigate to Identity

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.

Active domain

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.  

Directory settings - sync tab

Note:

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:

  1. 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.
  2. 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.
  3. 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.
  4. (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.
  5. Privilege the technical account userID in Acrobat Sign as a group-level administrator.
  6. 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.
  7. 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.

Enable users to access the Developers Console

Before being able to add a new technical account, the user must first be added to the Adobe Acrobat Sign Solutions - Enterprise product profile (in your Licensing Admin Console) as an Admin or Developer.

  1. Click on the Adobe Acrobat Sign Solutions - Enterprise link in the left-hand rail or products.

  2. Select the default product profile for the Acrobat Sign service.

    Select product profile

  3. The Add users to this product page opens:

    • Select either the Admin or Developer tab.
  4. Enter the email address of the user you want to grant access.

  5. Click Add Admin/Developer.

    Add Developer

  6. Enter the email address of the user you want to grant access.

  7. Enter the first and last name.

  8. Save when done.

    Enter developer information

Create a new project on the Adobe.io Console

  1. 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.
    Admin Console instances

  2. Select Create new project.

    Create a new project

  3. The new Project is displayed on the Projects tab of the console.

    Take a moment to name your Project by clicking the Edit Project button.

    • Provide a name your coworkers will understand
    • Provide a brief description
    • Save the edits
    Edit the project

  4. Select the new Project (on the Projects tab) to open it for configuration.

    On the Get started page:

    1. Select Add to Project
    2. Select API from the drop-down
    Add API

  5. On the Add an API page:

    1. Select the Document Cloud filter
    2. Select Acrobat Sign
    3. Click Next
    Select Acrobat Sign

Create a new JSON Web Token

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:

  1. Select Generate a key pair.

  2. Click Generate keypair.

    Gnerate key pair

  3. Once the key pair is created, you are prompted to save the private key to your local system.

    The public key is available to copy from the interface:

    Public Key

  4. Select Next.

  1. Select Upload your public key.

  2. Drag your public key certificate to the upload field.

  3. Select Next.

    Upload your public key

    Your uploaded public key is displayed on the Configure API page. You can copy it from here.

    You may upload additional keys, or generate new keys as needed.

  4. Select Next when all of your keys have been added.

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.

  1. Select the check box for your Default Adobe Acrobat Sign Solutions - Enterprise.
  2. Save Configured API when ready.
Save configured API

Generate an access token

Once saved, the technical account is created, and you are returned to the project home page.

In the Generate access token section, there is an input field for your private key. 

  1. Paste the private key you generated/uploaded earlier into the Private key field.

  2. Select Generate Token.

  3. After a moment, the Private key field refreshes to display the Access Token.

  4. Copy and save the access token.

    Generate the access token

  5. Lower on the same page, you have access to the:

    • Client ID
    • Client Secret
    • Technical Account ID
    • Technical Account email
    • Organization ID

    Copy and save the Technical Account email.

    Save the Tech Account email

  1. In the config.properties file, set the technical account information:

    • Apikey
    • Technicalaccountid
    • Orgid
    • Secret
    • expirationTime
    • metascopes
    • key_path
    • imshost
    • imsExchange 
  2. Store the secret.key in DER format inside the target folder. 

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:

  1. Log in to Acrobat Sign as an account-level administrator.

  2. Navigate to the Groups tab in the admin menu.

  3. Click the plus icon to create a new group.

  4. Enter an intuitive name for the group (perhaps the same name as the Project).

  5. Save the group.

  6. (Optional) Open the new group and configure the settings needed for the application.

    Create a group

Note:

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.

Privilege the Technical Account userID as a Group administrator in Acrobat Sign

Allow a few minutes for the newly created techacct.adobe.com user to be generated in the Acrobat Sign system.

  1. Log in to your Acrobat Sign account as an Account level administrator.

  2. Navigate to the Users tab of the admin menu.

  3. Search for the new techacct.adobe.com email address (copied from the project home page).

  4. Click on the user and select Edit User Details.

    Edit user details

  5. Click the plus icon in the  Group Membership section and add the application’s group to the user’s profile.

  6. Select the application’s group and click the Mark as Primary link.

  7. Check the box to flag the userID as a Group Admin.

  8. (Optional) Remove the technical account from the Default group.

  9. Click Save when done.

    Save the user settings

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.

Create a new federated userID

Before creating the new userID, you must identify an email address that can be used for inbound replies/questions from your recipients.

To create the new userId:

  1. Log in to your (Federated Sync) Admin Console as an administrator.

  2. Navigate to:  Settings → Identity

    Select a directory to create the new user.

    Active domain

  3. Select the Sync tab.

  4. Select Go to Settings and click Enable Editing.

    When editing is enabled, your Adobe Admin Console allows edits to the user data within the admin console only. Your IdP is not updated with the edits.

    Directory settings - sync tab

    Note:

    Editing will remain enabled for one hour only, or until manually disabled.

    Tech Account

  5. Log in to your Licensing Admin Console (if you are working with multiple Admin Consoles).

  6. Navigate to: Users → Add user.

  7. 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.

    Tech Account

  8. Log back into the Federated Sync Admin Console to enable the synching of your IdP data.

  9. Navigate back to Settings → Identity → {Directory} → Sync → Go to Settings.

    Click Disable editing to re-enable the syncing of data with your IdP.

  10. Your new userID will automatically be generated in the Acrobat Sign system.

Share the technical account with the new federated userID

To gain access to the content for a userID you can log in to, the 

  1. Log in to Acrobat Sign as an account administrator.

  2. Navigate to the Users tab in the admin menu.

  3. Single click the new user, and Edit User Details.

  4. Select Sharing Status in the left menu.

    Ensure the Users's Account Shared With tab is selected.

  5. Select the Shared With User tab at the top of the Sharing Status page.

  6. Share the new userID's account with the technical account

    1. Click the plus icon in the top right row to open the selector interface.
    2. Click the three lines icon to the right of the search box.
    3. Expand the group where the technical account userID resides.
    4. Click the plus icon next to the technical account userID to select it.
    5. Check the Additional Permission to allow Sending.
    6. Click Save.
    Tech Account

Test your new technical account

To test that your access code is functioning correctly:

  1. Select the GET /users method.

  2. In the Authorization field:

    1. Type in the word Bearer followed by a space
    2. Paste in the Access Code
    3. Click Try it out!
    Try it out!

  3. The response body will return with a listing of the users in the account and a Response Code of 200:

    Response body

  1. Select the POST /users/{userId}/views method.

  2. In the Authorization field:

    1. Type in the word Bearer followed by a space.
    2. Paste in the Access Code.
  3. In the userId field, enter me.

  4. Click on the Complete Model Schema link.

  5. Click into the yellow field to transfer the schema to the UserViewInfo field.

  6. Edit the UserViewInfo field:

    • For the name value, enter ALL.
    • For the autoLoginUser value, change it to true.
  7. Click Try it out!

    Configure API for access token

    The returned Response Body field contains the URL needed to log in as the user:

    Copy the access URL

  8. Copy the URL and paste it into a browser.

  9. You will be challenged to confirm the login.

    Click Yes.

    Confirm login.

Test sending an agreement using the technical account on behalf of the new userID via API

  1. Obtain a transientDocumentId or have another method to attach a file ready.

  2. In the Authorization field:

    1. Type in the word Bearer followed by a space
    2. Paste in the technical account's Access Token
    3. In the x-on-behalf-of-user field, enter the email address of the new userID
    4. Complete the rest of the AgreementInfo with the transientDocumentId, name of the agreement, signature type, and state.
    5. Click Try it out!
    Try it out!

  3. Log in to Acrobat Sign as the new userID and navigate to the Manage tab.

  4. Reviewing the agreement audit log, you will see that the agreement was sent by the technical account on behalf of the new userID.

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.

Agreement sent on behalf of the user

 Adobe

Get help faster and easier

New user?