> 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/release-notes/global-settings/monthly-releases/global-settings-v1.6.15-monthly-release-notes.md).
# Global Settings (v1.6.15) - Monthly Release Notes
{% hint style="info" %}
#### Release Details - Global Settings - 1.6.15 - April 1, 2026
This article is intended for Salesforce administrators, compliance officers, and IT teams responsible for managing Salesforce backups and data governance.
**Release Type**
* Monthly
* Applies to Flosum-hosted and self-hosted
**Prerequisites**
* A registered and configured Flosum Cloud Apps tenant
* Appropriate Flosum user permissions (SystemAdministrator or equivalent)
{% endhint %}
##  Summary
This article documents the patch release for **Global Settings (1.6.15)**. This monthly release introduces organization environment categorization and a simplified, centralized login entry point to improve tenant access for global teams.
###  Organization Environments
Environments have been introduced to categorize organizations by type: **Dev, QA, Test, and Prod**. This categorization provides clear visibility into each organization's role within your development lifecycle, making it easier to manage multi-org setups at scale.
When creating a new organization, users are now required to select an environment. The selected environment appears in the **Environment** column of the organizations table, enabling administrators to quickly see the organization’s role.
For existing organizations, the assigned environment can be updated at any time using the **Update Environment** button. No data migration or reconfiguration is needed when changing an environment designation.
This feature helps users quickly identify an organization's environment and lays the foundation for upcoming functionality in the Cloud DevOps application.
###  Login Flow Update
We are introducing a new common entry point for all applications and regions:
*
Users no longer need to know which region their tenants are hosted in, improving the experience for multinational teams. There is also no need to bookmark multiple URLs, since access is now centralized through a single link.
After navigating to the entry point, users are taken directly to the login page. Once they enter their email address, they will see a list of all tenants associated with that email.
There are no changes to existing flows:
* The registration process remains the same.
* The SSO flow is still available via the **Use tenant name** option.
{% hint style="info" %}
**Key update:** The region is now determined after the user enters their email address.
{% endhint %}
---
# 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/release-notes/global-settings/monthly-releases/global-settings-v1.6.15-monthly-release-notes.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.
