> For the complete documentation index, see [llms.txt](https://docs.frends.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frends.com/reference/administration/environments-and-agent-groups/environments.md). # Environments Logical containers of Agent Groups. Environments provide logical separation for your integration workloads and define the scope for configuration values across your Frends Tenant. ## What are Environments? In the Frends architecture, an Environment is a logical boundary within a Tenant that isolates configuration contexts, deployment targets, and operational state. Environments decouple integration logic from underlying infrastructure, allowing integration Processes to be developed once and promoted through distinct lifecycle stages without altering the underlying process definitions. Within Frends, there is a fundamental separation between the centralized cloud control plane and the distributed execution plane. The Frends Control Panel provides design, versioning, and administrative oversight, whereas execution occurs on the Agents within designated Agent Groups. An Environment serves as the scoping container for these Agent Groups, binding physical or containerized Agents to a specific operational domain such as Development, Test, or Production. In addition to grouping runtime infrastructure, Environments define the scope for environment-specific configurations. Environment Variables, API keys, and deployment parameters are resolved dynamically based on the Environment where a Process is actively deployed. This architecture guarantees that sensitive credentials, connection strings, and endpoints remain strictly segregated between stages while maintaining complete consistency in the Process business logic. ## Environment management The Environment management view in the Frends Control Panel provides administrators with centralized control over the Tenant's environment topology, runtime clusters, and visual identification settings. Through this administrative interface, teams can create and configure Environments, monitor connected Agent and API Gateway capacity at a glance, and navigate directly to child Agent Groups. Each Environment can also be assigned a distinctive color theme to reinforce operational awareness across the platform.

Management view for Environment.

## Usage Managing Environments is performed through the Frends Control Panel under the Administration menu. ### Accessing and navigating Environments To access the view, open the `Administration` dropdown in the top navigation bar and select `Environments`. When navigating to this page, the Control Panel opens the default Agent Group view for the default Environment by default. To view and edit an Environment's settings, click the specific Environment header card in the left panel. This loads that Environment's overview in the main panel, showing its configured Agent Groups and visual color settings. ### Creating and renaming Environments To add a new Environment, select the `+ New Environment` button at the top of the left panel. Enter a descriptive name such as Test or Production and confirm the creation. To rename an existing Environment, select it from the left panel and click the pencil edit icon next to the Environment title in the main panel. ### Reordering Environments The left panel allows administrators to reorganize the sequence of Environments or remove them when no longer needed. Selecting an Environment card exposes up and down reorder arrows alongside a delete trash bin icon. Clicking the arrow controls shifts the Environment up or down, updating the display order used across Environment dropdowns and deployment dialogs.

Reordering and deleting Environments is done from the left-hand panel.

### Deleting Environments An Environment can be deleted by clicking the trash bin icon on its card in the left panel. Deletion is only permitted when the Environment is completely empty. If the Environment still contains any connected Agent Groups, those must be decommissioned and deleted first before Frends allows the Environment container itself to be removed. ### Setting Environment colors Each Environment can be assigned a distinct color theme to help users quickly identify the active working environment across the Frends Control Panel. In the main panel, select a color swatch from the `Pick a color for the environment` section. The chosen color updates the navigation bar highlight and deployment badges throughout the platform. ### Managing Agent Groups From the selected Environment pane, administrators can view existing Agent Groups or add new ones. Clicking an Agent Group card opens the detailed Agent Group configuration view to manage runtime Agents, connection strings, and registration settings. To add a new cluster to the current Environment, select the `+ New Agent group` button beneath the list of existing groups. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.frends.com/reference/administration/environments-and-agent-groups/environments.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.