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
- Transaction Footer
- 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
- 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
- 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
- Recipient Agreement Access
- 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
- 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
Overview
The Adobe Acrobat Sign Sandbox is a modified enterprise-tier account in an environment discrete from the production environment.
The purpose of the Sandbox is to allow administrators to test setting configurations, API calls, library templates, custom workflows, and new features that are approaching release. Scheduled releases that contain features are pre-published to the Sandbox 28 days before the public launch date.
The Sandbox is presented as a "blank slate" environment with the standard (default) configuration. The Sandbox does not mirror your existing production account when delivered.
The admin can copy Library Templates, Web Forms, Group names, Custom Workflows, and API Applications from one environment to the other, allowing tweaking and testing in the Sandbox and then moving the vetted object to the production environment for use.
Things to note:
- The Sandbox environment is a separately entitled pay-for-access environment. Contact your success manager or sales representative to inquire if you're interested.
- The Sandbox updates the codebase 28 days before a major release to allow accounts four weeks of testing to review the new content and report any problems they encounter.
- To have the option for entitlement:
- The production account must be an enterprise-level account.
- The account must have a success manager assigned.
- The account must manage its user entitlements through the Adobe Admin Console.
- The production account must be an enterprise-level account.
- Only one Sandbox is possible per account.
- The sandbox environment is built with one account-level admin added to the account. Additional users can be added in the same manner as the production environment.
- Additional admins can not be defined in the Admin Console. To configure a new admin for the Sandbox, the user must be elevated to admin in the Adobe Acrobat Sign environment.
- Additional admins can not be defined in the Admin Console. To configure a new admin for the Sandbox, the user must be elevated to admin in the Adobe Acrobat Sign environment.
- The sandbox environment is persistent and retains assets built over time (users, templates, workflows).
- Customers that add Users to their Sandbox must keep these userIDs in mind if they have to disable or delete (via GDPR tools) a user in production. Given Sandbox is a discrete environment, these users will need to be explicitly addressed.
- Customers that add Users to their Sandbox must keep these userIDs in mind if they have to disable or delete (via GDPR tools) a user in production. Given Sandbox is a discrete environment, these users will need to be explicitly addressed.
- Contact your success manager if any back-end settings need to be adjusted (e.g., Number of pages per agreement, Send in Bulk roll-up value).
- The Sandbox has only one environment and is hosted on the Azure platform.
- Integrations are not available with sandbox accounts.
- Agreements sent from the Sandbox are watermarked as "not for production use."
- Sandbox does not permit configuring the Account Setup tab of the account admin menu (Company Name and Hostname values).
- The Sandbox does not support the Acrobat integration.
- The Sandbox does not support the Acrobat Sign mobile applications.
- The settings for Require signers to use a mobile device are not available in the Sandbox.
- The control to Allow recipients to decline is reduced in scope and listed as an option in the Additional Settings section of the Signature Preferences tab.
- Outbound email notifications are largely suppressed by default. Your success manager can assist if you want to modify the email notification options.
- User/account provisioning emails are disabled.
- Emailed agreement notifications to the agreement sender and participants are disabled, to include:
- Please Sign and Signed and Filed emails to recipients
- The sender of the agreement will still get the Signed and Filed email
- All emails to CC'd parties
- Updates to recipient groups when one member completes the signature
- Sent agreement notifications
- Viewed agreement notifications
- Archiving events
- Cancellations
- Delegation actions
- Expired agreements
- Uploaded agreements
- Signer replacement
- Please Sign and Signed and Filed emails to recipients
Configuring Settings
By and large, the option to configure account or group-level settings matches the setting options that you find in your production environment.
It's worth noting that new and updated features become available in the Sandbox at least weeks before a release to allow customers to investigate them in a safe environment. Therefore, it's likely that some settings or interfaces will be different than the production environment. Please review the pre-release notes if you encounter a discrepancy.
Adding users and admins to the Sandbox
Users are added to the Sandbox through the Adobe Admin Console.
Users are sent an email to establish a password prior to login, just like in the production environment.
Once the user is added to the Sandbox, an account-level admin can promote them to a group-level admin within the Sandbox environment by editing their user profile.
Account-level admins are defined in the Admin Console by promoting the user in the Sandbox product profile.
Common questions
Customers can contact Adobe Support to report issues observed in their Acrobat Sign Sandbox instance. Adobe will execute the same triage and support techniques in Sandbox that it uses in the Acrobat Sign Production instance. Given the time sensitivity between the Sandbox and Production release dates, Adobe will address issues based on their priority and severity. Resolution will be prioritized on a case-by-case basis. Customers who report high-priority issues will be notified of the release version that will address their issues once known.
For regular Support SLAs, please refer to the section named ‘Initiation and Processing of Service Request’ on our Support Services Terms and Conditions page.
No.
Sandbox and production environments exist in a one-to-one relationship.
Yes.
Multiple admins can authenticate to the Sandbox and work on different assets at the same time.
If two or more admins are manipulating the same asset at the same time, then the last one to save their version overwrites any/all previous versions.
Currently, the Sandbox refreshes one day after the production environment updates.
If the production environment updates on March 1st, then the Sandbox will update on March 2nd.
Starting in October 2022, the Sandbox environment will publish new content 30 days before a major launch.
Yes.
All users and assets created in or copied to the Sandbox persist until explicitly removed.