# Environments ## **Setup Environments** {% embed url="" %} ### **Accessing the Environments Section**
* First, navigate to the **Settings** menu (gear icon) on the left sidebar. * In the **Project** settings section, select **Environments**. This will bring you to the Environment management page, where you can create and manage different environments, such as staging, testing, or production.
*** ### **Creating a New Environment** * On the **Environments** page, click on **+ New environment**. This opens the environment setup popup, where you can configure the details for your new environment.
*** ### **Configuring Environment Details** In the **Edit environment** popup, fill in the following fields: * **Icon & Color**: Choose an icon and color to visually distinguish this environment. * **Name**: Enter a descriptive name, such as "Staging," "Production," or "QA." * **Domains**: Add one or multiple domains associated with this environment. Separate domains by spaces, or press Enter after each domain. Domain rules here follow the same logic as the “[on filtered URL](https://help.usejimo.com/docs/publish/target-specific-urls-domains-where#domain-based-targeting)” in the **Where** field of Target and Publish settings. You can also use regular expressions (e.g., `\.*bar.com$` to match all subdomains ending with bar.com). * **Description**: Optionally, add a description for this environment to clarify its purpose or content.
*Tips on Domain Entry*: * Single Domain Example: `foo.com` * Multiple Domains: `foo.com bar.com` * Regex Matching: `\.bar.com$`
*** ### **Viewing and Managing Created Environments**
Once your environment is created, it will be displayed on the **Environments** dashboard with the chosen icon, name, and associated domains. To view details or make changes, click on the environment tile, and select the **three-dot menu** to either **Edit** or **Delete** the environment.
*** ## Using Environments ### **Target & Publish Settings** After creating environments, they are available within the **Target and Publish** settings of any experience. When you hit **Publish**, the **Env** selection dropdown (defaulted to "All domains") will automatically appear, allowing you to choose the specific environment(s) where the experience will be published. This ensures that your experience is live only on the domains associated with the selected environment(s).
*Example:* If you have "Staging" and "Production" environments set up, you can choose to publish an experience to either or both environments directly from this dropdown. *** ### **Quick Access in Experience Details** If you need to adjust the environment settings for an experience after it’s been published, you can do so from the **experience details page**.
Open any experience in the dashboard to access its details (**A**) and use the **Env** dropdown in the top-right corner to quickly change the environment(s) on which the experience is active without needing to republish. {% hint style="info" %} Additionally, you can filter experiences by environment using the **Environments** filter dropdown (**B**) to display only experiences associated with a selected environment. {% endhint %}
*Example:* If you initially published an experience on "Staging" and now want to move it to "Production," simply select "Production" from this dropdown. *** {% hint style="warning" %} ### **Use Complementary Filters** When using the **Where** settings for specific URL filtering, note that these settings act as additional filters on top of the environment selection. If you apply a domain in the **Where** filter that is not included in the selected environment(s), the experience will not display on that domain. **Environments** and **Where** filters need to be configured to work in harmony to ensure accurate targeting. *Example:* If you target a specific URL under the "Where" filter but select an environment that does not include that URL’s domain, the experience will not be shown. {% endhint %} --- # 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://help.usejimo.com/docs/settings/environments.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.