An environment is a set of integration configurations that govern how a flow interacts with other services, mostly involving sending answers and events.
Environments are defined per flow, and are shared across all variants of that flow, to ensure data integrity between variants.
By default, each flow comes with two environments: production and staging.
Production should be used for the "live" version of a flow.
Staging can be used to integrate with mock or test versions of your integrations, to create a production-like version of a flow that only talks to non-production systems and does not contaminate production data. It is optional to use staging, but for complex forms it is useful to have.
You can create new environments if you need them.
From the flow index page, the Environments tab will show the environments editor.
Here it is possible to edit all aspects of integrations.
When changes have been made to any of the integrations, you will be prompted to save them.
Updating an environment does not update flows that were deployed to that environment in the past. You must re-deploy flows once the environment is saved.
Clicking Edit... on the top right of the environment editor shows a list of the current environments and allows the addition of new environments.