Pro and Team guide · Environments

Development and Production

On Pro Team and Business every job lives in two environments: Development, where you build and try things, and Production, where it runs for real. The same process, with each environment's own credentials and values.

Where	The environment row at the foot of the sidebar
Who	Everyone in the organisation
Plans	Pro Team and Business: Development and Production; Enterprise: Development, Test and Production

A Team job's page with the environment menu open at the foot of the sidebar: Development (here) and Production, over the job's spaces and its live process — Choose the environment at the foot of the sidebar: the whole console - jobs, processes, runs - is then in it. Click to open full size.

The console is in one environment

Choosing Development or Production at the foot of the sidebar puts the whole console there: Runs, Logs, schedules, webhooks and forms show that environment's. Building happens in Development; Production changes only when a job is promoted.

Each environment's own credentials and values

A process is designed once. In Settings › Build & release › Environments, each environment binds the credentials its steps use and the values a step reads with =Env("NAME") - a test mailbox in Development, the real one in Production. Mark Production Protected, or Require approval, so nothing reaches it without a person's yes.

Settings, Environments: the Development environment with Protected and Require approval, its credentials, and its variables — Environments: what each environment binds, and how Production is protected. Click to open full size.

Runs per environment

Runs filters by Where: the environment the console is in, or All environments.

The Runs page filtered to Development: no runs yet, choose All environments to see every run — Runs in Development; choose All environments to see Production's too. Click to open full size.

Last updated October 29, 2026