> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/global-settings/environment/organizations/update-an-organization-environment.md).
# Update an Organization Environment
##  Overview
This article shows you how to update an organization's **Environment** label. The Environment label helps you identify and organize your organizations: when you have many, it lets you filter and quickly find the ones relevant to your current task. The label does not limit the actions an organization can perform or have performed on it, and you can change it at any time.
## Change an Organization's Environment
{% stepper %}
{% step %}
### Access Global Settings
1. From any **Flosum Cloud App**, click the **App Switcher** icon at the top of the left sidebar menu.
2. Click **Global Settings**.
3. The **Global Settings** app will open in a new tab.
{% hint style="info" %}
Global Settings can also be accessed by logging in directly via the Flosum Cloud Apps Login URL. See the following article for login instructions.
* [Log In To Global Settings](/global-settings/getting-started/log-in-to-global-settings.md)
{% endhint %}
{% endstep %}
{% step %}
### Update Environment
1. Click **Organizations** from the sidebar menu.
2. Click the **Three Vertical Dots** menu at the right end of the Organization for which you wish to change the Environment.
3. Click **Update Environment**.
4. Click the **Environment** dropdown menu.
5. Select the environment label you want to assign to the Organization.
6. Click **Update**.
7. The Organization's environment label has now been updated.
{% endstep %}
{% endstepper %}
---
# 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.flosum.com/global-settings/environment/organizations/update-an-organization-environment.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.
