Introduction to environments

Environments are isolated deployment spaces in which your triggers and workflows are deployed and executed. They let you separate the development, testing and production phases.

What is an environment?

Each environment carries its own:

• deployments: a workflow is deployed or not in each environment — see Deploy a workflow;
• variable values: the same dictionary key can have a different value per environment — see Values per environment;
• access permissions: a role's scope depends on the environment type (Development, Other environments, Production) — see Roles and permissions.

You create and label your environments yourself — see Manage environments.

Environment types

Label	Typical use
Development	Build and test workflows daily (test nodes use it by default).
Other environments	Staging, UAT: validate before going to production.
Production	Run the workflows delivered to end users.

tip

The Development and Production labels also influence permissions: deploying to Production or viewing Production traces requires dedicated roles — see Roles and permissions.

Next steps

• Manage environments
• Deploy a workflow
• Values per environment

---

See also: Roles and permissions — How it works