Skip to main content
A workspace is the top-level container for everything in Courier. It holds brands, providers, templates, API keys, user profiles, and analytics, and shares none of them with other workspaces. Environments inside a workspace separate release stages, so you build and test without touching live traffic.

​
Workspace, environment, or tenant

Courier has three isolation layers, and they stack: a workspace contains environments, and within an environment you send to tenants. Pick the layer whose boundary you need. Choosing a workspace where you needed a tenant means maintaining two of every template. covers when and how to use them.

​
Environments and API keys

Every workspace starts with Production and Test environments, and you can add as many custom ones as you need. Each API key belongs to one environment. covers which key to use and how to move templates between environments.

​
US and EU workspaces

If you use both the US and EU datacenters, you have a separate workspace in each. Each one keeps its own data in its own datacenter, and nothing is shared between them. See . covers what Courier bills for, including how a new workspace joins your plan.

​
FAQ

The Migrate assets flow copies a template and its dependencies to another environment or another workspace in the same datacenter. Provider integrations aren’t copied, so configure them in the destination. has the details.To copy a template between your US and EU workspaces, use the . Read it with a key from one workspace, then create it with a key from the other.