Adobe Acrobat Sign Sandbox environment overview

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

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.

Sending agreements from the Sandbox

Sending an agreement produces a signable document that is watermarked as Adobe Sign Sandbox Test.

Keep in mind that outbound email to recipients is disabled but can be enabled upon request to your success manager.

Common questions