> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/saas/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.immuta.com/saas/releases/behavior-change-release-process.md).

# Behavior Change Release Process

Learn about Immuta’s behavior change release process so you can plan feature adoption

The behavior change release process allows you to control whether a product change that affects existing functionality is enabled for your account before the changes are enabled across all accounts. Generally, Immuta allows you to opt in or out of a feature change for two months before the feature is enabled for all accounts. However, Immuta may provide more time for specific changes that require more lead-time, such as API changes.

The stages of this process are described below. If a feature change qualifies for the behavior change release process, specific dates for each stage will be provided in the [deployment notes](/saas/releases/index.md). See a list of all the features on the [Behavior change release features page](/saas/releases/behavior-change-release-process/behavior-change-release-features.md).

{% stepper %}
{% step %}
**Opt-in period**

For the **first month** after a change is released, it is **disabled by default** for all accounts. The feature change will not be released to any customers who have not opted in. If you have a non-prod environment, it is recommended that you take advantage of this opt-in period on that non-prod environment.

Contact your Immuta representative or [submit a support ticket](https://support.immuta.com) to enable the feature change during this period.
{% endstep %}

{% step %}
**On by default period**

During the **second month** after a change is released, it is **on by default** for all accounts. However, the feature change will not be released to any customers who have opted out.

Contact your Immuta representative or [submit a support ticket](https://support.immuta.com) to opt out before this period. A behavior change feature cannot be disabled after it has already been enabled.
{% endstep %}

{% step %}
**Enabled for all accounts**

At the end of the opt-out period, the feature change is **enabled for all accounts**.

Immuta no longer offers the option to opt out of the change.
{% endstep %}
{% endstepper %}

## Qualification for a behavior change

A behavior change is defined as any change to existing behavior that returns different results from before and may impact customer code or workloads. Migrations that impact customer-authored configurations, such as policies or settings, may also fall in this category even if the functional results remain the same post migration.


---

# 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://documentation.immuta.com/saas/releases/behavior-change-release-process.md?ask=<question>&goal=<user_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.