# Feature Flag Audience Targeting

The *Feature Flag access* audience condition enables coordinated experiences across multiple features during phased rollouts or A/B tests. Run layered or mutually exclusive experiments, chain Feature Flags together, or gate sub-features behind primary ones.

When setting the audience for a Feature Flag's Configuration, use the Feature Flag access condition to include or exclude users who are part of one or more specified flag audiences.

* For **exclusive experiments**, use the Feature Flag access condition to make sure users in one experiment are not also in an experiment running for a different flag.

* To roll out **sub-features** that add to another flagged feature, use the Feature Flag access condition to make sure the sub-features are only made available to users who are part of the initial feature's audience. For a retail app, sub-features for a new checkout flow could be an in-store pickup option or AI-powered product recommendations. 

## Requirements

All Airship customers have one complimentary Feature Flag per project. For more flags, get the Feature Flags add-on for your plan. For AXP Essentials and Essentials Starter plans, see [Changing your Airship plan](https://www.airship.com/docs/guides/getting-started/admin/company-plan/#changing-your-airship-plan). If you have an enterprise plan, [contact Airship Sales](https://www.airship.com/contact-us/). See also [What plan do I have?](https://www.airship.com/docs/reference/feature-packages/#what-plan-do-i-have) in our *Feature packages reference*.

Minimum SDK versions for the Feature Flag access condition: iOS 19.4, Android 19.7, Web 2.7.

## Documentation

Get all the details in the docs:

* [Conditions](https://www.airship.com/docs/guides/experimentation/feature-flags/#conditions) in the *Feature Flags* guide
* [Feature Flags](https://www.airship.com/docs/guides/experimentation/feature-flags/)
* [Feature Flags](https://www.airship.com/docs/developer/sdk-integration/web/feature-flags/) for the Web platform