Configure your tenant

Use a sandbox to safely make changes to your production tenant:

1. Create a sandbox before making configuration changes to your tenant.

2. Access the sandbox (this topic), and then make configuration changes to your tenant. Run the updated workflow from within the sandbox, run sandbox validations, and verify that your changes are ready for promotion.

3. Promote configuration changes to your production tenant.

This is part two of a series of topics that describes how your brand can use sandboxes to safely make changes to your production tenant.

Note

Users who have been assigned the DataGrid Operator or DataGrid Administrator policies, and then assigned the Allow sandbox administration policy option, are allowed to create sandboxes and promote changes to production from a sandbox.

The following sections describe the steps you’ll follow when working in a sandbox to make configuration state changes to production.

	To access a sandbox, from the list of sandboxes, select the    icon, and then from the list of options select Access sandbox. Important Data is not moved between production and a sandbox. Configuration state is copied from production, and then applied to the sandbox. Updates to configuration state in production are made available to the sandbox as updates. Configuration state changes in the sandbox are copied to production when they are promoted.
	Sandbox configuration works the same way as it does in production with all of the same features and functionality. The main difference is that users in a sandbox are assigned the DataGrid Administrator policy, which gives them full access to the configuration state within the sandbox. When you access a sandbox, it’ll look much the same as production, but with a different color scheme. Amperity recommends to use a sandbox when making any configuration state change to your brand’s production tenant, including: Adding data sources Building custom domain tables Configuring courier groups Adding tables to existing databases Adding new databases Testing out complex queries, and then optimizing those queries Adding destinations or data templates to existing destinations Validating end-to-end workflows Adding new Profile API endpoints or updating existing endpoints
	Sandbox-specific notifications are built into the pages to help you identify the current configuration state of the sandbox as it relates to the configuration state in production. These appear near the top of each page. A notification is shown when action is required to synchronize the configuration states between a sandbox and production. For example: after which you can review the details for each update that may be available. A list of changes will appear under the Added, Changed, or Removed sections. Click the name of the update to learn more about the differences between the configuration states of your sandbox and production.
	A series of validations are run against updates. These validations will notify you within the sandbox when the configuration state of production and a sandbox conflict. Most of the time you should receive a validation report that does not contain a list of conflicts, similar to: Occasionally, you will receive a validation report that shows one (or more) validation errors. For example, a schema mismatch between a custom domain table in production and a custom domain table in the sandbox: If you receive a validation report with errors, investigate each error and work to resolve the underlying issue. It is possible that resolution must be done in production before pulling those updates to the sandbox. It is also possible that the resolution is done in the sandbox. It depends on the validation issue.
	When there are updates that can be pulled to your sandbox from production you will be notified, after which you can review the validations and each of the updates. Click the Pull button in the top-right of the page to pull the updates to your sandbox.