Log in to Acrobat Sign as an account-level administrator
- Welcome to Adobe Acrobat Sign for Government
- First steps for new accounts
- Claiming an email domains
- Connecting Okta to a federated identity solution
- Manually create/edit users in Okta
- First steps for new accounts
- Configure Acrobat Sign
- Configuration Overview
- System requirements
- Branding
- User access to features
- User experience within the application
- Recipient experience when interacting with agreements
- Transaction security
- Compliance information
- Configuration Overview
- Administrator processes
- Admin guide overview
- Users
- Groups
- Templates
- Custom workflow designer
- GDPR deletion processes
- Sandbox
- User environment and processes
- Support resources
- Transaction limits
- Page layouts
- Configure your profile
- Send agreements
- Compose an agreement to send for signature
- Recipient signing order
- Written signatures
- Send an agreement to yourself only
- Send in Bulk
- Sending from a template on the Manage page
- Sign agreements
- Fill and Sign a document
- Self Signing
- Signing a document from an email link
- Sign a document from the Manage page
- Compose an agreement to send for signature
- Custom workflow designer
- Manage agreements
- Search for agreements
- View Agreements
- Activity history and Audit Report
- Add a note to an agreement
- Set a reminder
- Cancel a reminder
- Add an expiration date
- Modify/Delete an expiration date
- Modify the files of a sent agreement
- Replace the current recipient
- Upload a signed agreement
- Share an individual agreement
- Download an agreement
- Download the individual files of an agreement
- Download the audit report
- Download the signer identity report
- Download the field data from an agreement
- Cancel an agreement
- Hide an agreement from view
- Reporting
- Create a report with classic reporting
- Report charts and data exports
- Data Exports
- Report Charts
- API
Overview of UMG (Users in Multiple Groups)
Users in Multiple Groups extends the practical use of the Group structure beyond simply containing a list of users and the assets that are available to them.
A Group is essentially a set of permissions that govern the options and defaults presented to the user when they are composing agreements or managing assets (reports, library templates, etc)
By allowing a user to have membership in multiple groups, administrators have the option to build groups with explicit workstreams in mind. Strong defaults can be installed and configuration options can be limited, ensuring a more perscribed document flow and resolution. For example, dedicated groups can be built for:
- Internal documents (Tax documents, automatic deposit forms, vacation requests)
- Legal documents (Non Disclosure Agreement, Memorandum of Understanding)
- Compliance restricted signature flows (CFR 21 part 11, PCI, HIPAA)
A complete list of interface and functional changes can be found here >
It is recommended that you register for a developer account so you can experience the different interface and interactions that UMG introduces in a safe environment.
Customers that have custom API integrations or who leverage 3rd party integrations are strongly recommended to test their code/integrations in a developer account thoroughly before updating.
Actions to review/take before updating
UMG is incompatible with the classic Home, Manage, and Custom Workflows pages.
When you enable UMG, the account will enable the most current versions of the Home, Manage, and Custom Workflow pages (if they are not already), and disable the links to switch back to the classic interface.
The administrator's interface option to revert back to classic pages and will be disabled in the admin menu.
The only way to revert to the classic page layouts is to revert back to Users in Single Group first.
It is recommended that you enable the modern versions of the Home, Manage, and Custom Workflow pages several weeks prior to updating to UMG to allow your user base to get accustomed to the base page layouts.
If the modern versions of the Home and Manage page render as blank pages, you will need to contact your network security team to allow the Adobe Acrobat Sign endpoints.
UMG has been compatibility tested and is expected to work normally with the following Acrobat Sign partner integrations:
- Acrobat Sign Mobile Apps (iOS & Android)
- Box
- Dropbox
- Microsoft Dynamics 365
- Microsoft Office (Word/PowerPoint/Outlook)
- Microsoft Power Automate/ Power Apps
- Microsoft SharePoint Online
- Microsoft SharePoint OnPrem
- Microsoft Teams
- Oracle NetSuite
- Salesforce
- SAP SuccessFactors
- ServiceNow
- Workday
Note that these integrations are not yet “UMG aware”, so the settings used when agreements are sent will be those of the user’s “primary group”.
The ability to recognize and work with new group memberships is planned for future releases of these integrations.
If you have built custom integrations using the Acrobat Sign APIs, we strongly urge you to test them on a separate UMG-enabled developer account before updating your production account.
- Your success manager (or support) can help you set up a UMG-enabled developer account
Any existing REST v6 API call will continue to work, whether UMG is enabled or not.
- Previous API versions (both SOAP and REST) will continue to work, but will only recognize the settings of the user’s "primary group”
- To take full advantage of UMG, you will need to migrate your code to the REST v6 API
If you work with 3rd party partner integrations such as:
- Apttus
- Ariba
- CallidisCloud
- Icertis
- Intesi
- Jaeger
- Nintex
- Zoho CRM
We strongly urge you to test these on a UMG-enabled developer account before enabling UMG on your production account.
Your success manager (or support) can help you set up a UMG-enabled developer account.
If you find an issue, please reach out to the integration partner to report the issue and request a fix.
All accounts are strongly encouraged to update as early as possible to allow time for troubleshooting if problems arise.
Accounts can switch back if problems do occur.
How to update the account to UMG
When you are satisfied that your account is ready to update:
-
-
Navigate to Account > Account Settings > Global Settings > Users in Multiple Groups
-
Click the Enable Now button
-
Evaluate the checklist and check each box to confirm that you have verified that your account is ready to be enabled.
Click OK
-
Click Save
If you have to revert back to users restricted to a single group, some things to be aware of are:
-
All users will be restricted to their primary group
- User will only be able to access templates/workflows associated to their primary group
- Users can only send agreements from their primary group
-
All of a user's group memberships (other than the primary group) are inactivated
- If the user is not moved to a new group while UMG is disabled, the user's groups will be reactivated when UMG is reenabled
- If a user is assigned to a new group while UMG is disabled, the user's group_membership table will be re-written with only one (primary) group (disabling the inactive group records). The user will only retain the primary group membership when UMG is reenabled
-
All UMG enabled pages will revert to the single group interface/functionality
- Sending/Template pages will remove the group selector
- Creating users in bulk will revert to the previous syntax
-
Page version options will be restored to their previous state
- If you did not configure your account to use the most current versions of the Home, Manage, and Custom Workflow pages prior to updating, your account will revert to the exact set of page configurations that existed prior to the update
- If you did not configure your account to use the most current versions of the Home, Manage, and Custom Workflow pages prior to updating, your account will revert to the exact set of page configurations that existed prior to the update
-
Users retain access to any asset they have created (agreements, library templates, web forms)
- The creator of any asset is always associated to it as the owner, regardless as to group association
-
Existing agreements are unaffected and will complete as normal
- Changing the owner's group status has zero impact on agreements in-flight
- The owner of the agreement does not change, and the parameters of the agreement are locked in at the time the agreement is sent
-
Integrations will function as they did prior to updating to UMG
- Acrobat Sign integrations do not currently account for users in multiple groups, so reverting the Acrobat Sign back to single users happens outside the awareness of the integrations
- User activity is unimpacted
- In-flight agreements will complete normally