Environment Configuration

Manage environment-level settings, feature values, regions, runtime limits, secrets references, and deployment defaults. This example brings Production and Staging together so engineering teams can find the next task without losing context.

It includes representative records such as Runtime limits and Regional routing. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Environment Configuration
Use this template in Figr

Template facts

Screen

Settings

Primary action

Save changes

Pattern

Settings

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Engineering and security teams need to save changes while keeping variables, regions and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Production gives users an obvious place to start.
  • Supporting view: Staging keeps the related context close.
  • Primary action: Save changes stays visible when people need it.
  • First signal: Variables shows a useful value (128).
  • Second signal: Regions gives additional context (4).
  • Sample record: Runtime limits.
  • Next record: Regional routing.

States worth designing

  • Default preferences: say what changed, protect progress, and offer a clear next step.
  • Unsaved changes: say what changed, protect progress, and offer a clear next step.
  • Policy blocks edit: say what changed, protect progress, and offer a clear next step.
  • Changes applied: say what changed, protect progress, and offer a clear next step.
  • Restricted settings: say what changed, protect progress, and offer a clear next step.
  • Connectivity interrupted: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Production → Staging → Save changes → Review outcome

Patterns used

Settings, Production, Staging, contextual actions, error recovery

Why these choices work

Separate safe everyday choices from risky changes, show who can edit them, and confirm irreversible actions.

Pay attention to production and staging. People need to distinguish Runtime limits from Regional routing. Keep variables visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Save changes”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Certificate Management, SLO Dashboard, Job Scheduler.

Start from this in Figr

Design a environment configuration screen inside our existing product. Use our current components, tokens and content language. Include Production and Staging views, credible records like Runtime limits, and a clear “Save changes” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr