Manage Environments

Add, edit, and order Site Environments from Settings → Site settings.

Add an Environment

  1. Open Site settings and find Environments.
  2. Click New Environment.
  3. Enter a required name.
  4. In GitHub version-control mode, enter the required branch name.
  5. Optionally enter a unique hostname and newline-separated allowed browser origins.
  6. Click Confirm.
  7. Click Save changes on the Site settings page.

Console inserts a new non-production Environment immediately before Production. The first authoring Environment and final Production Environment are fixed boundaries.

Edit or reorder

Use Edit Environment to change name, branch, hostname, or origins. The Environment key is read-only. Use Move up or Move down for intermediate Environments; they cannot move before rank 0 or after Production.

Remove only an intermediate Environment after reviewing published Workflows, Connections, API Keys, keys/values, logs, Apps, hostnames, and external callers. The fixed first and Production Environments cannot be removed in Console.

Review downstream effects

  • Rank controls save and promotion order.
  • Branch maps source history when GitHub version control is enabled.
  • Hostname selects Environment for HTTP and MCP routing.
  • Allowed origins control cross-origin browser access.
  • Connections, API Keys, Workflow publications and status, keys/values, and logs carry Environment scope.
  • Environment access supplements Site permissions when scoped permissions are enabled.

Hostname DNS is not automatically applied, log a ticket with Flowgear Support to action changes.

See Site Settings, Site Environment, and CORS and Allowed Origins.