---
title: Environment
description: What an environment is in Prefactor, how it filters activity and
  deployments, and where to see it in the platform.
editUrl: true
head: []
template: doc
sidebar:
  hidden: false
  attrs: {}
pagefind: true
draft: false
---

An environment is a named delivery stage — development, staging, production, or similar — configured at the [account](/platform/concepts/account) level and shared across all agents in that account.

Environments give each [agent](/platform/concepts/agent) a set of stages to track independently. For each agent, a [deployment](/platform/concepts/agent-deployment) records which version is current in each environment; different stages can be on different versions at the same time. Each [instance](/platform/concepts/instance) is attributed to the environment the agent reported when the run started, so activity from different stages is always kept separate.

## In the Admin UI

- [Account › Environments tab](/admin-ui/account/environments) — create and manage environments.
- The deployment snapshot on the [Agent page](/admin-ui/agent#deployment-snapshot) — which version is deployed per environment.

## Related concepts

- [Account](/platform/concepts/account) — environments are configured within an account and are visible across all its agents.
- [Agent](/platform/concepts/agent) — agents belong to the account; environments determine the lens through which you view their activity.
- [Agent deployment](/platform/concepts/agent-deployment) — records which version of an agent is current in a given environment.
- [Instance](/platform/concepts/instance) — instances are attributed to the environment the agent reported when the run started.