Workspaces

A workspace is an isolated environment inside your organization. Data in one workspace is invisible from another: separate customers, subscriptions, invoices and settings, under the same company.

Every organization has at least a live workspace. Sandbox is not a mode you toggle; it is a workspace, with its own data and its own settings.

What isolation actually means

Isolation is enforced in the database rather than in application code. Almost every table carries a workspace column and a row-level policy that refuses reads and writes outside the current workspace.

The practical consequences:

• A customer created in sandbox does not exist in live, and never will.
• A subscription cannot span workspaces.
• A setting saved in sandbox applies to that sandbox only. A setting saved from live lands at the organization by default and is inherited by every workspace, unless a workspace overrides it. See Settings.

✕

What sandbox is for

Sandbox is where you try things that would be expensive to get wrong: a new plan shape, a promotion whose budget you are unsure of, or an integration you are wiring for the first time.

It also carries test clocks, which let you move time forward to see what a subscription does at renewal without waiting a month.

Shared, not isolated

The company profile, tax identity, security settings, branding, roles and members, checkout links and job limits are organization-wide. Data and connections (customers, invoices and their numbering series, e-invoicing channels, integrations, mail providers, payment gateways) are per workspace.

That split matters when onboarding: connecting a payment gateway in sandbox does not connect it in live.

Access

Two permissions govern workspaces: one to see them, one to create, rename or delete them. Which of your people hold each is set by their role, in Organization settings.

Reference