Set up a sandbox made from production
How to do it in Simple Signature, one step at a time.
Last updated 9 Oct 2026
Paid version only. These steps do not count in the setup progress.
A sandbox made or refreshed from production holds most of the setup of Simple Signature. Do the steps below there. In a sandbox where you install Simple Signature yourself, follow the whole guide instead.
Switch to Salesforce Classic.
Some of these steps can fail in Lightning. See step 9 of Connect the site.
Copy the address of the signature site.
Open Setup. In the Quick Find box, type Sites. Click Sites. Click the Site URL of your signature site. The site opens in a new tab. Copy its address.
Paste it into Site URL for Signature Requests.
Open the Configure page. Click the Configuration tab. Paste the address into Site URL for Signature Requests. End it with a slash.
Decide about Turn Off Emails.
A sandbox can hold the email addresses of real customers, mostly a Full or Partial Copy sandbox. Then keep Turn Off Emails ticked, and put your own test addresses on the Whitelist. Emails then go to those addresses only.
To add an address, click Blacklist and Whitelist Emails/Domains. Type a Name and the address in Entry. Pick Whitelist as the Type. Click Add.
Untick Turn Off Emails only when the sandbox must send all emails, and it holds no real address. Maintenance rules and large tests can send many emails.
Click Save Settings.
Click the Site Configuration tab. Add the remote site it asks for.
The tab can show a message about the remote site settings, with an address under To Enable Site Access. Copy that address. Add it as a new remote site, as in step 5 of Connect the site. Tick Active.
Authorize the site again.
Do it as in Authorize the connection again. Salesforce can ask you to sign in to the sandbox again. If it fails, see Authorize does not work.
Connect Google Docs again, if you use it.
Click the Google Docs Configuration tab. Click Revoke. A window asks you to sign in to Google. Pick the account that owns your template documents. Accept the permissions. Copy the code. Paste it into Authorization Code. Click Submit.
The tab shows no message after this. The Revoke button shows again.
Make the templates again, in a Developer sandbox.
A Developer or Developer Pro sandbox has no data from production, so it has no ß Templates. A Full or Partial Copy sandbox has them. Skip this step there.
Do this step in Lightning Experience. In Classic, New opens a plain form with no Google Docs choice. For each template in production:
- In production, open the template. Copy its Google Doc Id.
- In the sandbox, open ß Templates. Click New. Pick Google Docs. Click Next. Pick Create New Template. Click Next.
- Paste the Google Id. Fill in the other fields the same as in production. Leave Copy Template as it is. Click Save.
- Copy the ID of the new template from the address bar. Put it in place of the production ID in your actions and experiences. See step 10 of Make a PDF template in Google Docs.
Both orgs then use the same Google document. A change that you make from the sandbox also changes the PDF in production.
Set the email Access level to All email.
Open Setup. In the Quick Find box, type Deliverability. Set Access level to All email. Click Save. A new sandbox starts with System email only.
Applies to
Simple Signature 5.8.x, paid version. These steps come from the tested Simple Signature implementation guide, where they sit with the steps before and after them.
Was this helpful?
Thank you. It helps us know which articles work.
Related
Still stuck?
Open a case and paste the exact error text. A person reads every case.