What is a “sandbox”?
Sandboxes are test environments that some platforms offer. They generally allow teams to set up and test features or configurations without touching their actual production environment.
It is not always the case, but we generally see larger and more well-established companies ask for a sandbox environment. These kinds of teams may have hundreds or thousands of users on a given platform, so any changes that are made will potentially have a major impact on business and need to be thoroughly tested.
For example, let’s say an application that your team uses recently released a new feature. You may opt to set that new feature up in your sandbox environment and run some tests to see how it works and make sure it doesn’t mess anything up before committing to enable it in your production environment.
FAQ
- What is the Gem Sandbox?
- How public do we want the Gem Sandbox to be? On a need-to-know basis or accessible in our public HC?
- What are the requirements to set up the Gem Sandbox?
- What are some general or common scenarios where setting up a Gem Sandbox may be helpful?
- Is there a cost to be paid or tier that we only bring the Sandbox up to? (How do we determine which customers we offer this option to?)
- How is it set up from both the CS and ENG side?
- How does Customer Success speak about the Gem Sandbox?
- How does Gem Support speak about the Gem Sandbox?
- Who or what team is the owner of the Gem Sandbox? (Who do we funnel issues up to?)
- What are the current articles or documentation on the Gem Sandbox?
- What are some known limitations or things anyone here at Gem should be on the lookout for?