# Environment Variables

Environment Variables let you reuse the same values across multiple Processes, but they're also essential for CI/CD. By using them to define Environment-specific settings (like source or target systems), you can deploy new or updated Processes with a single click — no manual changes required.

## Environment Variables

Environment Variables are defined centrally in the Environment Variables section of Frends Control Panel, and can hold groups of values for different purposes. Values can be grouped together by their purpose, such as per target system or for specifically global error handling, and the values themselves can be textual, numerical, lists or secrets. 

<figure><img src="/files/8m5K45JCOsQbvgGHigB9" alt="Environment variables are global values for each environment."><figcaption><p>Environment Variables are the global values for each Environment.</p></figcaption></figure>

As the key feature of Environment Variables, each Environment in your Frends Tenant can receive separate values for the same variable. This makes it easy to develop and test the integrations using test values and test environments for the targeted systems. When the Process is ready, it can be deployed to production without any changes to the Process itself, because the Environment-specific values are defined separately and centrally in Environment Variables.

<figure><img src="/files/q1ry7EdrCNLzlJ70CxKU" alt="Using environment variables is recommended for example for connection parameters."><figcaption><p>Using Environment Variables is recommended for example for connection parameters.</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.frends.com/management-and-operations/integration-lifecycle/environment-variables.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.