Requesting a Sandbox
Sandboxes are set up by your CSM or the Vitally Support team, they're not self-service to create. Reach out to either to get one provisioned.
Once set up, you'll receive:
Domain:
[sandbox].vitally.io/[sandbox].vitally-eu.ioUser invite: the email of the invited user
Expiry date: the renewal date of your Prod environment
Invite URL: the URL to first access the sandbox
Once the invited user has access, they can invite other team members themselves, as long as they have the Admin role: Manage Team is an Admin permission, and Leaders cannot invite teammates. In the sandbox, go to Settings > Team Members > Manage Team and select Invite a Teammate. Enter the teammate's name and email address, choose their Role, and submit the invite. Add a +sandbox or +test suffix to the email address here if you want a separate test identity, for example jane+sandbox@yourcompany.com. The invited teammate receives an invite URL by email and should open it in an incognito or private browser window, so that signing in to the sandbox does not interfere with their session in your production environment.
Your sandbox's expiry date matches your live environment's renewal date. After renewal, if you'd like to keep your sandbox, request an extension through your CSM or Support. If the sandbox isn't accessed for 3 months past your renewal date, it will be permanently deleted, and a new, empty sandbox would need to be provisioned and set up again from scratch.
Setting Up Your Sandbox
A new sandbox starts completely empty. Setup typically involves:
Exporting data from production, using the Export function in your live environment.
Uploading that data into your sandbox via CSV upload, mapping to the equivalent traits in your sandbox.
Connecting integrations to their sandbox equivalents (e.g. a Salesforce or HubSpot sandbox/test instance), rather than pointing your Vitally sandbox at live production data.
Resetting the Sandbox
There's no self-service way to reset your sandbox from within the product. Clearing data, integrations, traits, Hubs, and Dashboards is handled by the Vitally Support team.
To request a reset, contact Support with your sandbox's subdomain and what you need cleared: all data, or specific objects (Organizations, Accounts, Users, NPS).
A couple of things worth knowing about how this works, so expectations are set correctly:
All integrations need to be disabled first, this is a prerequisite Support will confirm before proceeding.
Deleting Organizations does not cascade-delete the Accounts underneath them. Those Accounts may briefly disappear from Vitally while the deletion processes, then reappear once it's done, they are not removed. A User under a deleted Organization is only deleted if that Organization was their sole connection.
After a reset, everything deleted needs to be recreated from scratch.
Best Practices for Sandbox and Production Separation
Use distinct email addresses for sandbox accounts, such as adding a
+sandboxor+testsuffix to your email, if you want a deliberately separate test identity.Open sandbox invite and login URLs in an incognito or private browser window. The sandbox runs on its own subdomain, and an active production session in the same browser can interfere with signing in to it.
Single Sign-On is configured separately for each environment. Enforcing SSO in production has no effect on how teammates sign in to your sandbox. SSO is rarely enabled on a sandbox, but if it is, it behaves exactly as it does in production, so teammate provisioning is handled through your identity provider rather than through the in-app invite.