What's New
Get Started
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
- 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
-
Guidance for regulatory requirements
- Accessibility
- HIPAA
- GDPR
- 21 CFR part 11 and EudraLex Annex 11
- Healthcare customers
- IVES support
- "Vaulting" agreements
- EU/UK considerations
- 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
- 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
- Send (Compose) page
- Send an agreement only to yourself
- Send an agreement to others
- Written Signatures
- Recipient signing order
- Send in Bulk
-
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
Advanced Agreement Capabilities and Workflows
- Webforms
- Reusable 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
- Agreement data extraction
- Agreement notifications
- Agreement generation
- Custom Send workflows
- Share users and agreements
Integrate with other products
- 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
Overview
The Group Administrator Permissions is a suite of five controls that grant or limit a group-level administrator's authority over users and group settings (within the Acrobat Sign environment). Because these controls directly enable group admin authority, they exist only at the account level and apply to all groups.
- Group administrators can edit group settings - When enabled, the account-level administrator can designate which tabs in the settings menu the group-level admins have the authority to configure. Remember that group-level settings override the account settings, and the group-level settings define or grant access to users and agreements.
- Group administrators can edit user profile information - When enabled, group-level administrators can edit any user's user profile.
- Group administrators can edit user permissions - When enabled, the group administrator can elevate a non-privileged user to have group administrator authority.
- Group administrators can add or remove users from a group by - This dropdown contains three options that control if the group-level admin can create new users in the account and assign them between groups.
- Group admins can remove users from the account's default group - If enabled, the group-level administrator has the authority to remove users from the account's Default group, even if the admin does not have administrative authority in the Default group.
Best practices
The authority granted to group-level administrators will be highly dependent on the size of the account and the organizational demand for distributing user and group management. It's generally a good rule to disable any functionality you don't expect group admins to do regularly and adjust when needed.
Access to group settings can be handy when initially creating and configuring groups for specific work purposes. However, settings aren't prone to frequent changes, so removing this access after the initial setup should be considered. If some settings demand periodic adjustment, only enable the tabs containing those settings. Tabs referencing more global configurations (e.g., Digital Identity, Security Settings) should probably be locked down for Account level administration in most organizations. Not that is it possible to enable access to configure group-level settings and then lock access to the tab, preserving the edits.
The authority to edit a user's profile information is rarely needed but has relatively little risk. The decision for user profiles typically falls to a preference of having one admin do a task or sending a group email to the users and having them update their profiles.
The authority to elevate a user to group administrator access caries a non-trivial risk, as group-level administrators may have access to a broader range of potentially more sensitive information, such as the data fields from agreements sent by all users in their group which may contain personal identifiable information, credit card information, and so on. For most organizations, constraining the ability to elevate user authority is best left to account-level administrators.
Managing user access to groups aligns with what a group admin would be expected to do in most organizations. Little risk is presented, as the group admin can only add users to their group, and they cannot change the user's primary group (unless the user's primary group is also under the authority of the group admin).
Adding new users to the account is generally reserved for account-level administrators or automated processes (such as automatic provisioning through SSO authentication). There may be circumstances that require a group-level admin to undertake this task, but this level of authority should typically be removed when the job is completed.
Granting the authority to remove users from the Default group will depend on how the Default group is being used. Accounts that use the group as a holding area for new and inactivated users may find enabling this option removes significant friction from their group administrators when new users are onboarded. Accounts that use the Default group as a working group from which users are expected to send agreements will likely want to deny having users removed by group admins.
Configuration
Availability:
Group Administrator Permissions are available for enterprise license plans only.
Configuration scope:
The feature can be enabled at the account level only.
The controls for this feature can be assessed by navigating to Global Settings > Group Administrator Permissions