# Flagship October Release Notes ๐
## Flagship October Release Notes ๐
## **Flagship New Releases**
## ๐Multiple Environnements :
To optimize the product life cycle, the development team must be able to work not only on a pre-prod or prod environment but also on Staging, RC, or any other environment where they may need to minimize bugs, facilitate testing and accelerate the team's development capacity. The ability to quickly create a local environment gives the developer the flexibility to work safely on a feature without impacting the work of the rest of the team.
This is why we are excited to introduce the Multi-environment manager, allowing you to create any environment you need in just 3 clicks.
#### **Want to know more about it?**
๐ Consult the [Multiple-environments documentation](https://flagship.zendesk.com/hc/en-us/articles/4403192348434)
## โ๏ธ User Consent SDK
To be GDPR compliant or simply to meet your users' preferences, you may need to get their consent to collect data before exposing them to an experiment, personalization or for feature management. To that end, we have released the User Consent parameter for SDKs to disable data collection if your users have not consented to the experiment/personalization/data collection.
This method will not prevent you from displaying changes to your users, it will simply block data collection. This means that you will still be able to use Flagship, even if visitors have not consented to data collection, to manage KillSwitches, Release Toggles, and Permission Toggles.
The user consent parameter is available for the following SDKs:
* Android
* iOS
* Java
* Flutter
---
# 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.abtasty.com/flagship-deprecated/release-notes/flagship-october-release-notes.md?ask=
```
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.