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
- Add, edit, and review active users
- Create function-focused users
- Review users who haven't completed verification
- 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
- Transaction Footer
- In Product Messaging and Guidance
- Accessible PDFs
- New authoring experience
- Healthcare customer
- Account Setup / Branding Settings
- 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
- Restart agreement workflow
- 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
- Apply Adaptive Signature Draw scaling
- Digital Signatures
- Overview
- Download and sign with Acrobat /content/help/en/sign/config/admin-managed-sharing.
- Sign with Cloud Signatures
- Include metadata for Identity Providers
- Restricted Cloud Signatures Providers
- 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
- CCs
- 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
- Restrict access to shared agreements
- 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
- System Requirements and Limitations
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
- Send (Compose) page
- Overview of landmarks and features
- Group selector
- Adding files and templates
- Agreement name
- Global Message
- Completion Deadline
- Reminders
- Password protect the PDF
- Signature type
- Locale for the recipient
- Recipient signature order/flow
- Recipient roles
- Recipient authentication
- Private message for the recipient
- Recipient agreement access
- CC'd parties
- Identity check
- Send an agreement only to yourself
- Send an agreement to others
- Written Signatures
- Recipient signing order
- Send in Bulk
- Send (Compose) page
- Authoring fields into documents
- In-app authoring environment
- Create forms with text tags
- Create forms using Acrobat (AcroForms)
- Fields
- Field types
- Common field types
- E-signature fields
- Initials field
- Recipient name field
- Recipient email field
- Date of signing field
- Text field
- Date field
- Number field
- Checkbox
- Radio button
- Drop-down menu
- Link overlay
- Payment field
- Attachments
- Participation stamp
- Transaction number
- Image
- Company
- Title
- Stamp
- Field content appearance
- Field validations
- Masked fields values
- Setting show/hide conditions
- Calculated fields
- Field types
- 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
- Sandbox
Support and Troubleshooting
Adobe Acrobat Sign release schedule and prerelease documentation
Adobe Acrobat Sign rolls out at least three updates per year, categorized as major or minor releases. Additional minor updates may be introduced as needed to address system or customer issues.
- Major Releases bring significant updates, new features, and multiple enhancements.
- Minor Releases focus on smaller improvements and user experience tweaks. These occur between major updates, typically one to two times per cycle.
To prevent disruptions, new features are disabled by default and must be manually enabled by an account or group admin.
For Health and Life Sciences customers requiring compliance validation, Acrobat Sign partners with a third-party vendor to provide a validation package for every major release containing features to minimize your risk factor.
This Prerelease Notes page is regularly updated as new information becomes available, so its content is relatively dynamic.
While this page is localized, the process takes time, which may result in localized versions differing slightly from the authoritative US English version.
For the most accurate and up-to-date information, we recommend referring only to the US English page.
Adobe Acrobat Sign follows a structured schedule for publishing release notes and documentation updates:
8 Weeks Before Production Release
- The prerelease page publishes a summary of expected features and updates, typically four weeks before the Sandbox launch.
- Any feature changes after this point are noted in the Errata section.
- Resolved issues are not included at this stage.
4 Weeks Before Production Release (Sandbox Launch)
- The prerelease page is updated with detailed documentation on new and updated features.
- Links to prerelease support documentation (available in US English only) are added as needed.
- The initial Resolved issues section is published, with ongoing updates over the next four weeks.
Launch Day
- The official release notes are updated with final feature details and links to production support documentation.
- The prerelease page is refreshed to highlight the next release cycle.
- Documentation is published after release verification in the live system, typically after 7 pm PT, though complex updates may take longer.
- The final Resolved issues list is added to the US English release notes, with localized versions updated later.
Government Cloud Release
- The Government Cloud environment typically updates between two days and several weeks after the production release, as some features may require additional evaluation before deployment.
Sandbox documentation is designed for the production environment. Links found in the prerelease content target production URLs, meaning those links may lead to older existing documentation or 404 results if the target page is new and hasn't been published yet (e.g., when the link is pointing to a new feature in the same release).
The new pages will be published when the release is published, and links will properly resolve to their production URLs.
Sandbox availability
Customers accessing the Acrobat Sign Sandbox environment can typically access the new release functionality four weeks before launch.
- The Sandbox environment must pass all production quality assurance procedures at the same quality level as the regular production environment.
- Adobe strives to have 99.9% availability in the Sandbox environment, but customers should note that the Adobe Unified SLA does not formally cover the Sandbox.
- The Sandbox environment uses the same status page and outage procedures as the regular Production environment.
This article contains prerelease information. Release dates, features, and other information are subject to change without notice.
Sandbox deployment: August 19, 2025
Production deployment: September 16, 2025
GovCloud deployment: September 18, 2025
Improved Functionality
- Custom Email Templates available for Acrobat Sign for Government - Customers on the GovCloud platform can now create custom email templates for their agreement notifications and reminders.
Available environments: Government | Available tiers of service: Acrobat Sign for Government | Configuration scope: Account or Group
- Rebranding of the Notarize integration to Proof - The integration to the online notarization service has been updated to reflect the service's new branding, Proof, for all customer-facing communications.
Updates to the Acrobat Sign UI are expected in the next (v16.2) release in October.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account or Group
Release errata
There are no items that have slipped from this release as of this time.
Resolved Issues
Issue | Description |
---|---|
4511940 | Summary: When a sender creates a text field with Multi-line data entry enabled and the font set to Auto, signers using a mobile browser see text cut off at the bottom of the field. |
Fix: Overrode the base method to get the field size to handle fontSize < 0 (auto) using a modified formula specific to multiline fields. | |
4516038 | Summary: When sending agreements with Send in Bulk, users see an error: "You have exceeded the maximum number of days allowed for document expiration." even though Document Expiration Settings are disabled at both the Group and Account level. |
Fix: Corrected code to properly evaluate the agreement expiration values for the group/account. | |
4522265 | Summary: When a PDF contains both fillable fields and text tags, the text tags are not processed. |
Fix: Created a task in the flattened case regardless of the presence of form field generators. Allows a PDF with form fields to process a formify artifact if needed. | |
4522645 / 4527073 |
Summary: Signed PDF includes a blank third page after the sender uploaded a document on behalf of the final signer. |
Fix: Improved the managing function to properly handle small streams. Written Signature uploads use the repaired document and not the original upload if any issue is detected with the uploaded document. | |
4524437 | Summary: New users are not logged into Adobe Sign after accepting the invite due to a bogus URL. |
Fix: Fixed the URL. | |
4525093 | Summary: The consumer disclosure link is not clickable. The link is present, but clicking it just toggles the checkbox instead of opening the link. |
Fix: Modified the link CSS to allow the link to open a new page. | |
4525099 | Summary: Customers who require SMS delivery but have disabled email notifications cannot send agreements by SMS. |
Fix: SMS /WhatsApp delivery is no longer dependent on the email settings. | |
4525328 | Summary: Using two or more templates that contain hyperlinks with the same name generates a server error when trying to sign |
Fix: If duplicate hyperlink names are found, the link names will be modified to ensure they are uniquely identified. | |
4525510 | Summary: Payment form field fails to retain the USD currency type in New Authoring Experience, leading to an 'Unexpected error' failure. |
Fix: The conversions for payment fields have been updated. | |
4525544 | Summary: Unable to edit the Active or Draft Webforms |
Fix: We now preserve the existing settings and send them to the server, instead of using the UI data. | |
4525901 / 4532254 |
Summary: Agreement is not getting assigned to the remaining signer because of an incorrect workflow role when new participants are added after entering field authoring. |
Fix: Improved the code to better evaluate the participant roles when new participants are added after authoring. | |
4526300 | Summary: Unable to create a custom agreement URL with the workflow ID with new experience |
Fix: When custom URLs are created with only the workflow ID, the agreement creation form reloads and calls the backend to fetch the workflow and draft agreement again during form loading. | |
4526756 | Summary: GovCloud API Swagger Page documentation is incorrect regarding creating new applications |
Fix: Added an additional phrase to avoid any confusion for FedRAMP customers. | |
4527340 | Summary: When users apply Fill & Sign in Acrobat web and then select Invite to e-sign, the values entered during Fill & Sign do not appear when the agreement transitions into the Acrobat Sign authoring page. The authoring view shows blank fields instead of the filled values. |
Fix: The default font size value has been correct, thereby allowing the content to display properly. | |
4528835 | Summary: "MISC_SERVER_ERROR for GET formData Some miscellaneous error has occurred" error when calling GET /formData for a specific Cursor due to a null pointer error. |
Fix: Added an NPE check and log. | |
4528902 | Summary: When an agreement is sent for sequential signing to 2 participants, the "recipient name" field assigned to the first participant is lost during PDF model processing. When setting the role of the "recipient name" field, the participation set role stored in the PDF model fails to convert. |
Fix: Numerous functions have been updated to properly manage this type of conversion. | |
4531278 | Summary: Some email addresses added as CCs are removed automatically after sending the transaction if they were created before Acrobat Sign added automatic lowercasing of email addresses in user creation. |
Fix: Updated the email address lookup/comparison in the CC removal code to be insensitive | |
4531669 | Summary: Agreements cannot be sent using PDF documents when processing form fields with names exceeding PDF specification limits. |
Fix: NPE checks added for the appearance of an annotation. | |
4531998 | Summary: Unable to Access Child Agreements Via API - "Invalid Document ID" Error due to a null bookmark title. |
Fix: Removed debug statement that can fail with an NPE if the bookmark title is null. | |
4532642 | Summary: When attempting to replace one of the counter signers in a web form that includes additional unknown signers and recipient group for counter signers, the update method attempts to read email from unknown participants (additional unknown signers), who have no user/email data, causing a NullPointerException. |
Fix: Added a filter condition to exclude unknown participations from the email collection stream, preventing NPE when processing participations that don't have user/email data yet. |
Adobe Acrobat Sign Release 16.2
Sandbox deployment: September 16, 2025
Production deployment: October 7, 2025
GovCloud deployment: October 14, 2025
Improved Functionality
- Request Signature introduces several UX improvements designed to reduce clicks and improve efficiency - These updates address customer feedback, making the new Request Signature experience faster, more discoverable, and better aligned with the classic workflow.
- All signature types are expanded by default in Authoring
- Prefill role is always visible in Authoring
- Inline add-recipient buttons replace hidden menus
- Automatic new recipient row when adding an address
- Copy/paste support for multiple recipient addresses
- Recipient groups supported in hybrid routing
- Admin control to choose default Compose view (guided vs. all-sections upfront)
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account or Group
- Support for checkbox groups allowing senders to define multi-select options within a form - Checkbox groups let senders specify how many options recipients must select, bringing new flexibility for agreements that require structured multi-choice input.
- Define multi-select checkbox groups
- Configure rules for exact, minimum, maximum, or ranged selections
- Convert single checkboxes into grouped checkboxes (and back)
- Validation is enforced during signing in classic eSign
- Recipient selections are preserved in signed agreements and downloadable form data
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account or Group
- User Invitation to their Acrobat Sign organization - Invite teammates directly from the Sign interface with admin-controlled workflows for faster team adoption. Depending on configuration, invited users may be auto-provisioned, routed through Just-In-Time (JIT) provisioning, or require admin approval. This streamlined flow reduces friction for SMB and mid-market teams, accelerates adoption of shared workflows, and gives admins better visibility into real license demand.
- New Invite button on Home and Post-Send pages for end users
- Invited users receive a welcome email and are added seamlessly to the organization
- Invitations respect existing auto-provisioning rules
- Admins can enable/disable and control who can send invites
- Admins can review pending requests in the Access requests section
- If auto-provisioning is disabled, requests are routed to admins for approval
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account or Group
- Allowed IP ranges for access to Acrobat Sign have been extended to Groups and APIs - More flexibility has been provided for IP restriction controls when securing access to Acrobat Sign. IP restrictions can now be configured at the group level by Group Admins. In addition, restrictions now apply to API access: if an account or group specifies an allowed set of IP addresses, both the Acrobat Sign UI and APIs can only be accessed from those addresses.
- IP restrictions now apply to both UI and API access
- Group Admins can configure IP restrictions for their groups
- Users in multiple groups are evaluated against their default group’s IP policy
- Integrations must use IP addresses added to the allowlist
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account or Group
- Quality of life updates for ETLA-licensed customers - The recent updates released for VIP licensed customers are being extended to ETLA licensed customers:
- Streamlined admin setup from the Home Page - Acrobat Sign introduces a new Account management section to help account admins quickly access key configuration tools. Add users, organize groups, connect integrations, and migrate templates directly from the Home Page—no digging required.
- Add users to the Admin Console from Acrobat Sign – Admins can now add users directly from the Users page in Acrobat Sign, automatically updating the Adobe Admin Console.
- Admin Console Role assignment now available through Acrobat Sign - To streamline setup, Acrobat Sign now allows account admins to assign key Admin Console roles—Product and Support Admin—without leaving the product interface.
- Easier access to the suite of third-party integrations - A new Integrations page has been added to the admin menu, providing direct, intuitive links to the setup files for the individual integrations.
- Easier HIPAA onboarding through in-product guidance - Organizations subject to HIPAA can now begin the enablement process within Acrobat Sign via a new self-service workflow through the Get Started admin menu. The system sends an automated request to Support and tracks progress based on the BAA signature and system configuration.
- Fast-track your template migration to Acrobat Sign with automated template conversion - The new template migration feature helps account admins quickly bring their templates into Acrobat Sign. Upload a template ZIP file, convert it automatically, and review results in the authoring environment—no technical expertise needed.
- Acrobat Sign Smart Assistant Chatbot - The new Smart Assistant gives you in-app answers to common questions like how to add users, check usage, or update settings. Ask your question in plain language and get step-by-step guidance, relevant HelpX articles, or links to support pages.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account or Group
- Remove Certification and Locking Signatures from Digitally Signed Agreements - Organizations that need to pass third-party signature validation services can now request Adobe support to configure their account or group settings to skip the application of Adobe’s Certificate and prevent locking signatures on digitally signed agreements. When enabled, agreements only contain the recipient's digital signatures, reducing rejection rates in strict regional validation tools.
- Account admins can request Adobe support to exclude Adobe Certification and Locking signatures at the account and/or group levels.
- Agreements contain only recipient digital signatures, improving acceptance by third-party validators.
- Audit Report records when certification is skipped, including a SHA-256 document fingerprint
- Applies across all export touchpoints: email attachments, Manage page downloads, API, and webhook payloads
- Resolves compliance gaps raised by customers requiring validation under regional trust schemes- Description
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account or Group
- Access to the modern Send in Bulk features for Acrobat Sign for Government accounts - Send in Bulk has been updated to access the modern functionality for the Acrobat Sign for Government environment.
Available environments: Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account or Group
- PDF/A improved to support PDF/A-3B conformance and convert all uploaded files to the selected PDF/A standard - Admins can now enable conversion and normalization of uploaded files—including PDFs, Microsoft Office formats, and raster images—into PDF/A-2b or PDF/A-3b. Existing PDF/A files are validated, repaired if needed, or normalized to the configured target level.
- Admins can configure PDF/A workflows at the account or group level.
- Supported conformance levels: PDF/A-2b (default) and PDF/A-3b.
- Non-PDF and non-compliant PDF documents are automatically converted to PDF/A.
- Damaged PDF/A files repaired or normalized to the target level.
- Attachments allowed per PDF/A rules: PDF/A-2b (only PDF/A), PDF/A-3b (any file).
- Agreements revalidated for PDF/A compliance at signing completion.
- Audit Reports are optionally generated in PDF/A format and include PDF/A validation/conversion results with conformance level.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account or Group
- Authentication Method Change Events in Audit Reports - Changes to recipient authentication methods can now be included in the Audit Report as discrete events. When a sender (or authorized delegate) updates a recipient’s authentication method—such as switching from SMS OTP to Email OTP—the update is captured and recorded in the agreement’s audit report, activity log, and API events list.
- A new event, Authentication Method Updated, appears in the audit report, showing:
- The recipient impacted
- The user who made the change
- The original authentication method
- The new authentication method
- The timestamp of the change
- Events are also exposed through the GET /agreements/{agreementId}/events API.
- Activity logs display the event with recipient, initiator, and timestamp details.
- A new event, Authentication Method Updated, appears in the audit report, showing:
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account or Group
Experience Changes
- Rebranding the notary service in Acrobat Sign from Notarize to Proof – The internal strings referring to Notarize Inc in the Acrobat Sign interface have been updated to the new branding: Proof
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account or Group
REST API/Webhook Updates
The below updates are presented in the prerelease notes for disclosure purposes. Full documentation for API and Webhook updates can be found in the Acrobat Sign developer documentation when the version update is delivered to the production servers.
- Super Group Admin role for OEM Partners - A new Super Group Admin role is available on the OEM 2.0 platform. This role lets partners grant their customers limited administrative capabilities to create and manage groups without exposing full Account Admin privileges.
- The Partner’s customer can create and manage their own groups.
- The creator of a group automatically becomes its Group Admin.
- Account Admins control which group settings are exposed.
- Group Admins see only relevant settings, such as Message Templates, Email Settings, Send Settings, and Sharing Status.
- The feature requires UMG (Users in Multiple Groups) to be enabled.
- Account Admins remain the only role with access to account-level settings and the ability to assign the Super Group Admin role.
Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group
Release errata
There are no items that have slipped from this release as of this time.