Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

download

What to expect with a Conga Contracts Sandbox

What to expect with a Conga Contracts Sandbox

You can expect the following with a Conga Contracts sandbox:

  • Your users will still exist, but they won't be able to log in. You will still have the Admin User available, but any new users created after the creation of the sandbox and the refresh will be erased.
  • Event and scheduled reports emails notifications will be disabled to avoid duplicate emails being sent from the production system.
  • The Conga CloudOps team requires a real working email address (either newly created or belonging to a User who will ignore test emails) in order to change all the current People Profiles (Company Contacts, External People, and Users) from their actual email (contacts and users still retain the email address from the Production environment) to the one provided. Otherwise, these records will be copied over to the sandbox with actual email addresses, and test emails may go out unintentionally. Unfortunately, the CloudOps team is not able to delete the existing Person Profiles in the newly provisioned sandbox.
  • Documents and creation templates are not copied over from your Production account. You will receive an error if you try to view any.
  • If you have any integrations, or anything related to Single Sign-On, it will not be copied over. This includes eSignature integrations, which we can add upon request.
Note:
  • Conga can create a blank sandbox for you upon request.
  • Your sandbox username must be different than your production username. For example, if your production username is firstname@conga.com, your sandbox username is firstname@congasandbox.com.