--- title: "How to configure environments and map stages?" slug: "how-to-configure-environments-and-map-stages" updated: 2026-10-16T09:59:01Z published: 2026-10-16T09:59:01Z canonical: "support.whatfix.com/how-to-configure-environments-and-map-stages" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.whatfix.com/llms.txt > Use this file to discover all available pages before exploring further. # How to configure environments and map stages? If you have multiple application instances, Whatfix Content might overlap or the desired content might not appear due to conflicting configurations. Whatfix offers an enhanced environment configuration setup that enables you to define application environments using various application attributes such as URLs, CSS Selectors, Window variables, and more. It also offers the capability to map content stages to the environments that dictate the content display rules for those environments. This configuration ensures content appears on your application instance for your end-users and can also be used to test content changes. The mapping conditions you set are similar to Visibility Rules. They determine which content needs to be shown in each application instance. Note: The enhanced environment application configuration is a **Beta** feature and available for both [Browser extension and JS embed](/studio/docs/choosing-a-delivery-method) mode of deployment. To enable this feature, contact [support@whatfix.com](http://mailto:support@whatfix.com?subject=Enable%20New%20Application%20Environement%20and%20Unified%20Play%20Extension&body=Hi%2C%0A%0APlease%20help%20setup%20the%20enhanced%20environment%20configuration%20and%20Unified%20Play%20Extension%20for%3A%0A%0ARegards%2C%0A). Use the following steps to configure the environment and map the stages: 1. On the Whatfix Guidance dashboard, click **Settings**. ![ia_settings_without_auto_testing](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/ia_settings_without_auto_testing.png?sv=2026-02-06&spr=https&st=2026-11-12T07%3A26%3A26Z&se=2026-11-12T08%3A26%3A26Z&sr=c&sp=r&sig=Hjq86a7m%2BSut7PI0rAesFK0acrky4s%2FYTR8eYoagY44%3D) 1. Click **Content deployment**. ![click_settings_content_deployment](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/click_settings_content_deployment.jpg?sv=2026-02-06&spr=https&st=2026-11-12T07%3A26%3A26Z&se=2026-11-12T08%3A26%3A26Z&sr=c&sp=r&sig=Hjq86a7m%2BSut7PI0rAesFK0acrky4s%2FYTR8eYoagY44%3D) 2. In the **Configure environment** tab, click **Add configuration**. ![cd_env_add_config](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/cd_env_add_config.jpg?sv=2026-02-06&spr=https&st=2026-11-12T07%3A26%3A26Z&se=2026-11-12T08%3A26%3A26Z&sr=c&sp=r&sig=Hjq86a7m%2BSut7PI0rAesFK0acrky4s%2FYTR8eYoagY44%3D) 3. Enter a **Name** for the application environment. For example, **Salesforce Opportunities**. ![Name_environment.png](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Name_environment.png?sv=2026-02-06&spr=https&st=2026-11-12T07%3A26%3A26Z&se=2026-11-12T08%3A26%3A26Z&sr=c&sp=r&sig=Hjq86a7m%2BSut7PI0rAesFK0acrky4s%2FYTR8eYoagY44%3D) 4. Under **Condition 1**, click the **Open** icon to expand the dropdown. ![environment_condition_1.png](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/environment_condition_1.png?sv=2026-02-06&spr=https&st=2026-11-12T07%3A26%3A26Z&se=2026-11-12T08%3A26%3A26Z&sr=c&sp=r&sig=Hjq86a7m%2BSut7PI0rAesFK0acrky4s%2FYTR8eYoagY44%3D) 5. Select a condition. For example, select **Domain**. > [!NOTE] > Info: > > For more information about adding conditions, see [Visibility and Display Rule Conditions](/studio/docs/visibility-and-display-rule-conditions-1). ![Select_environment_vr.png](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Select_environment_vr.png?sv=2026-02-06&spr=https&st=2026-11-12T07%3A26%3A26Z&se=2026-11-12T08%3A26%3A26Z&sr=c&sp=r&sig=Hjq86a7m%2BSut7PI0rAesFK0acrky4s%2FYTR8eYoagY44%3D) > [!WARNING] > Note: > > **Window Variable** is only available in JS Embed mode of deployment. 6. Select an operator, such as **Equals** or **Not Equals**, and then type in the URL value. ![Environment_value.png](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Environment_value.png?sv=2026-02-06&spr=https&st=2026-11-12T07%3A26%3A26Z&se=2026-11-12T08%3A26%3A26Z&sr=c&sp=r&sig=Hjq86a7m%2BSut7PI0rAesFK0acrky4s%2FYTR8eYoagY44%3D) > [!NOTE] > Info: > > Whatfix enables you to use Regular Expressions (Regex) as a condition. Regular Expressions are used when certain application URL components vary. For example, in `://.wikipedia.org/`, the special characters represent hash value and parameters of the URL and `wikipedia.org` is the application domain that you want to display content on. > > 1. In the dropdown, select **Regex equals**. ![Regex_equals.png](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Regex_equals.png?sv=2026-02-06&spr=https&st=2026-11-12T07%3A26%3A26Z&se=2026-11-12T08%3A26%3A26Z&sr=c&sp=r&sig=Hjq86a7m%2BSut7PI0rAesFK0acrky4s%2FYTR8eYoagY44%3D) > > b. Enter a value for the expression. ![enter_regex_value.png](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/enter_regex_value.png?sv=2026-02-06&spr=https&st=2026-11-12T07%3A26%3A26Z&se=2026-11-12T08%3A26%3A26Z&sr=c&sp=r&sig=Hjq86a7m%2BSut7PI0rAesFK0acrky4s%2FYTR8eYoagY44%3D) 7. Enter the value. ![environment_operator.png](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/environment_operator.png?sv=2026-02-06&spr=https&st=2026-11-12T07%3A26%3A26Z&se=2026-11-12T08%3A26%3A26Z&sr=c&sp=r&sig=Hjq86a7m%2BSut7PI0rAesFK0acrky4s%2FYTR8eYoagY44%3D) > [!NOTE] > Info: > > Use the **+ Add condition** button to add multiple conditions: ![cd_env_config_add_conditions](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/cd_env_config_add_conditions.jpg?sv=2026-02-06&spr=https&st=2026-11-12T07%3A26%3A26Z&se=2026-11-12T08%3A26%3A26Z&sr=c&sp=r&sig=Hjq86a7m%2BSut7PI0rAesFK0acrky4s%2FYTR8eYoagY44%3D) 8. Under **Map content stages**, select the content stage to preview or display content based on the conditions you have set. For example, select **Ready And Production** to preview or display content from the **Ready** and **Production** stages. ![cd_env_config_select_map_content_stages](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/cd_env_config_select_map_content_stages.jpg?sv=2026-02-06&spr=https&st=2026-11-12T07%3A26%3A26Z&se=2026-11-12T08%3A26%3A26Z&sr=c&sp=r&sig=Hjq86a7m%2BSut7PI0rAesFK0acrky4s%2FYTR8eYoagY44%3D) 9. Click **Configure**. ![cd_env_config_configure](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/cd_env_config_configure.jpg?sv=2026-02-06&spr=https&st=2026-11-12T07%3A26%3A26Z&se=2026-11-12T08%3A26%3A26Z&sr=c&sp=r&sig=Hjq86a7m%2BSut7PI0rAesFK0acrky4s%2FYTR8eYoagY44%3D) > [!WARNING] > Note: > > If you deploy Whatfix using the JS embed mode of deployment, click **Copy Deployment Script**, and then paste the script into your application’s code. The script ensures Whatfix content is available on every page of your application. ![Copy_deployment_script.png](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Copy_deployment_script.png?sv=2026-02-06&spr=https&st=2026-11-12T07%3A26%3A26Z&se=2026-11-12T08%3A26%3A26Z&sr=c&sp=r&sig=Hjq86a7m%2BSut7PI0rAesFK0acrky4s%2FYTR8eYoagY44%3D) > [!NOTE] > Info: > > - The environment details appear in the **Configure environment** tab. Use the **Edit** or **Delete** options to manage the configuration. ![cd_configured_env](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/cd_configured_env.jpg?sv=2026-02-06&spr=https&st=2026-11-12T07%3A26%3A26Z&se=2026-11-12T08%3A26%3A26Z&sr=c&sp=r&sig=Hjq86a7m%2BSut7PI0rAesFK0acrky4s%2FYTR8eYoagY44%3D) Whatfix Content includes Flows, Images, Videos, PDFs, Articles and Links. The feature release stage in which functionality is made available to a limited group of users for testing and feedback. Beta features are generally stable but may still undergo changes before becoming Generally Available (GA). ## Related - [Understand Advanced Customization ](/advanced-configuration.md)