Environments

Environments let you test a flag in Development or Staging without ever touching Production.

Every flag has a separate on/off state, rollout percentage, and value for each environment. Flipping a flag in Staging never affects what your production users see.

Creating an environment

1. 1
   Go to Settings → Environments

   You'll see a list of your current environments.
2. 2
   Click "New environment"

   A form slides open.
3. 3
   Fill in the details

   Give it a human-readable name (e.g. Staging) and a slug (e.g. staging). The slug is used by the SDK to target this environment.
4. 4
   Mark as production if applicable

   Production environments get a special badge in the dashboard as a visual reminder to be careful.
5. 5
   Click "Create"

   The environment appears immediately and all existing flags get a new per-environment record, starting disabled.

Environment slugs

Slugs are short, URL-safe identifiers. You pass them to the SDK when evaluating flags to target a specific environment. Examples: production, staging, dev-us-east.

Switching environments in the dashboard

Use the environment switcher in the sidebar to change which environment the dashboard is showing. Flag states, rollout percentages, and experiment data all update to reflect the selected environment.