# Sandboxes

> Create private test copies of your workspace to try settings, workflows, and integrations safely.

A sandbox is a private copy of your workspace for trying changes and testing integrations. It has its own records, settings, and API keys, and nothing in it reaches your customers. Use one to build a new workflow, rework a pipeline, or test a developer integration before you touch your live workspace.

Open **Settings → Integrations & Developers → Sandboxes**. You need the **Sandboxes → Manage** permission in the live workspace. Owners and admins have it by default; custom roles can be given it.

## Create a sandbox

1. Click **Create sandbox**.
2. Enter a **Name**, such as `Staging` or `Workflow testing`.
3. Choose a **Starting point**:
   - **Copy my settings** copies pipelines, properties, layouts, roles, workflows, templates, and your product catalog. No customer data is copied.
   - **Start blank** gives you a fresh workspace with the default setup, as if you had just signed up.
4. Choose **Who can enter**:
   - **Sandbox managers**: people with the Sandboxes → Manage permission.
   - **Everyone in the workspace**.
5. Click **Create sandbox**.

A live workspace can have up to 3 sandboxes. The page shows how many you have used.

Connections to outside accounts, API keys, webhooks, and billing are never copied. Connect test accounts inside the sandbox if you need them.

## Enter and leave a sandbox

Click **Open** next to a sandbox, or pick it under **Switch organization** in your avatar menu.

Inside a sandbox, an orange **Sandbox** banner stays at the top of every page. Click **Back to** _your workspace_ in the banner to return.

People join a sandbox with the role they have in the live workspace. Admins can change roles inside the sandbox to test permissions without affecting the live workspace. Removing someone from the live workspace also removes them from its sandboxes.

## Nothing leaves a sandbox

Sandboxes are safe because outside effects are either captured or blocked:

| What happens | Examples |
|---|---|
| **Captured** in the sandbox outbox instead of being sent | Emails, inbox replies, WhatsApp and social messages, push notifications, workflow webhooks, connector syncs |
| **Blocked** with an error | Phone calls, buying numbers, billing changes, ZATCA clearance, connecting outside accounts |
| **Turned off** | AI features |

Click **Outbox** in the banner to see everything that would have been sent. Only sandbox managers see the outbox.

Two things work on purpose so developers can test integrations: the sandbox's own [Developer App](https://workstation.repzo.com/docs/configuration/developer-api) API keys and its own [webhook endpoints](https://workstation.repzo.com/docs/administration/webhooks).

## Billing

A sandbox uses its live workspace's plan, modules, and limits. It has no subscription or seats of its own and does not add to your bill.

## Edit or delete a sandbox

- **Edit sandbox** lets you rename it or change who can enter.
- **Delete sandbox** permanently deletes everything in it, including test records, API keys, and the outbox. Your live workspace is not affected, and the slot frees up immediately.

Deleting a live workspace also deletes its sandboxes.

## Related documentation

- [Settings](https://workstation.repzo.com/docs/administration/settings)
- [Workflows](https://workstation.repzo.com/docs/administration/workflows)
- [Webhooks](https://workstation.repzo.com/docs/administration/webhooks)
- [Developer API and CLI](https://workstation.repzo.com/docs/configuration/developer-api)