---
schema_version: "1"
id: 26b5611ae6b45fe92dce8cc930fccbd731e2ecb67d3a989e902ffb25ad2b2497
title: Advanced Release Strategies
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/availability_create_and_use_advanced_release_strategies.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.availability_create_and_use_advanced_release_strategies.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 57d9669c540eaaa6a4d1a1bacde15f0b1aa3160be1bbfcbc5ca630fc2cf6dcaa
description: Consider advanced release strategies to control and revert changes.
products:
  - Cross Cloud
release: "264"
---
# Advanced Release Strategies

Consider advanced release strategies to control and revert changes.

If you have business-critical use cases that can’t afford downtime, consider advanced deployment strategies when introducing changes to your org.

For example, reduce the risk of changes impacting availability by adopting a feature flag, also known as a feature toggle, as part of your development and deployment process. A feature flag allows changes and new features to be deployed silently to production and remain dormant until the flag is turned on in production. Combined with system monitoring, your IT operations team can observe how the change performs and turn off the change if issues are detected.

You can also use this approach to roll out new changes in multiple stages to different subsets of your Salesforce users. With this approach, you can test new features with a closed group of test users in production, or conduct pilot and beta programs with a wider group of early adopters.

- Feature flags in Salesforce use custom metadata and permission sets. You can roll out new features to select users by assigning those users with the appropriate user permission set.
- Remove the feature flag and permanently embed the feature after it’s officially rolled out to all users.