---
title: About the Configuration Manager
slug: '2572'
canonical_url: https://docs.coveo.com/en/2572/
collection: coveo-for-sitecore-v5
source_format: adoc
---
# About the Configuration Manager
The options in the Command Center **Configuration Manager** let you:

* Change the Coveo organization your Sitecore instance is linked to.

* View and copy the list of URLs you should add to your firewall allowed list.

* Edit your indexing options.

* Enable or disable the Coveo for Sitecore reverse proxy.

![Command center Configuration Manager | Coveo for Sitecore 5](https://docs.coveo.com/en/assets/images/c4sc-v5/command-center-coveo-cloud-manager.png)

## Accessing the Configuration Manager

To access the Configuration Manager as a Sitecore administrator

. Go to the [Coveo Control Panel](https://docs.coveo.com/en/2195/).

. Select **Configuration Manager**.

![Control panel | Coveo for Sitecore 5](https://docs.coveo.com/en/assets/images/c4sc-v5/control-panel-2.png)

> **Note**
>
> You can also access the Command Center **Configuration Manager** using URL `+https://<INSTANCE_HOSTNAME>/coveo/command-center/index.html#cloud-organization+`, where `<INSTANCE_HOSTNAME>` is the name of your Sitecore instance.
> Non-Sitecore administrators can only access the **Command Center** by URL (see [Give access to the Command Center](https://docs.coveo.com/en/2843/)).

## Modifying your Coveo organization

To modify the Coveo organization your instance is linked to

. In the **Coveo Organization** section, click **Log In**.

![Command Center login | Coveo for Sitecore 5](https://docs.coveo.com/en/assets/images/c4sc-v5/change-org-cloud-login.png)

. Follow the instructions shown on screen to log in to the [Coveo Platform](https://docs.coveo.com/en/186/) using your preferred identity provider.

![Command Center change organization section | Coveo for Sitecore 5](https://docs.coveo.com/en/assets/images/c4sc-v5/change-org-cloud-existing.png)

. Select or create your Coveo organization.

** To select an existing organization, under the **Existing** tab, select the desired organization from the dropdown menu.

![Image of Select Organization dropdown menu with region flags | Coveo for Sitecore 5](https://docs.coveo.com/en/assets/images/c4sc-v5/change-organization-with-regions.png)

> **Notes**
>
> [.version.c4sc.c4sc-new.5-0-858-1.December-11&-2020]
> [Coveo for Sitecore 5.0.858.1](https://docs.coveo.com/en/3408#release-notes)
> 
> 
> * Coveo for Sitecore now lets you connect to Coveo organizations in regions other than `us-east-1`.
> For more information on your data residency options, see [Multi-Region Deployments](https://docs.coveo.com/en/2976/).
> 
> * The flag next to the organization name indicates the region the organization data is hosted in.
> The flag tooltip provides further details on the organization data residency location.

** To create a new organization

... Select the **Create New** tab.

![Create New organization section | Coveo for Sitecore 5](https://docs.coveo.com/en/assets/images/c4sc-v5/create-new-organization.png)

... Type the name you want in the **Organization Name** field.

> **Note**
>
> While you can always change your organization display name later in the [Coveo Administration Console](https://platform.cloud.coveo.com/login) ([platform-ca](https://platform-ca.cloud.coveo.com/login) | [platform-eu](https://platform-eu.cloud.coveo.com/login) | [platform-au](https://platform-au.cloud.coveo.com/login)) under **Settings** > **Organization** > **Profile**, be aware that the original name value you specify when creating an organization will forever be part of the unique and permanent ID of that organization.

... Select the **Organization Type** that matches your needs (see [Product entitlements](https://docs.coveo.com/en/l2590456/)).

> **Leading practice**
>
> [.version.c4sc.c4sc-new.5-0-858-1.December-11&-2020]
> [Coveo for Sitecore 5.0.858.1](https://docs.coveo.com/en/3408#release-notes)
> 
> 
> For a local development environment, select the [Test organization](https://docs.coveo.com/en/2959#test-organization) type.

... {empty}

--


[.version.c4sc.c4sc-new.5-0-858-1.December-11&-2020]
[Coveo for Sitecore 5.0.858.1](https://docs.coveo.com/en/3408#release-notes)


--

In the **Organization Region** dropdown menu, select the [data residency](https://docs.coveo.com/en/3141/) region that best suits your needs.

. Click **Apply and Restart**.

Your **Security** and **Indexing Options** section settings are carried over from your previous Coveo organization to the current one.
To make changes to these settings, refer to the [Modifying security settings](https://docs.coveo.com/en/2566#modifying-security-settings) and [Modifying your indexing options](#modifying-your-indexing-options) sections below.

> **Note**
>
> Allow 15 to 30 minutes for a new Coveo organization to be provisioned.
> 
> When a Coveo trial organization has been idle for some time, it's paused automatically.
> If you have selected an existing organization that has been idle for a while, one of the following dialogs is displayed when you reload the page:
> 
> ![Organization pausing dialog](:https://docs.coveo.com/en/assets/images/c4sc-v5/cloud-org-pausing.png)
> 
> ![Organization paused dialog](:https://docs.coveo.com/en/assets/images/c4sc-v5/cloud-org-paused.png)
> 
> If you click **Resume**, the organization status then changes to `Resuming`.
> 
> ![Organization resuming dialog](:https://docs.coveo.com/en/assets/images/c4sc-v5/cloud-org-resuming.png)
> 
> The dialog automatically closes once the organization has finished resuming and is, once again, fully functional.
> 
> You can also reactivate your organization by logging in to the Coveo Administration Console.

## Modifying your indexing options

To modify your indexing options settings

. In the **Indexing Options** section, specify your new settings.

![Command center change configured options | Coveo for Sitecore 5](https://docs.coveo.com/en/assets/images/c4sc-v5/command-center-change-configure-options.png)

Further details for each option are provided below.

** **Body indexing**: Lets you select whether the rendered HTML should be indexed.

** **Farm configuration**: Lets you specify a **Farm name** to set coherent names for your resources (that is, [sources](https://docs.coveo.com/en/246/) and [security identity providers](https://docs.coveo.com/en/242/)).

> **Important**
>
> By default, Coveo for Sitecore sources are named `Coveo_master_index - <FARM_NAME>` and `Coveo_web_index - <FARM_NAME>` in your Coveo organization.
> As a result, if multiple Sitecore instances use the same farm name and are linked to the same Coveo organization, their items are indexed in the same [sources](https://docs.coveo.com/en/246/).
> 
> This is rarely useful in a development scenario, but a leading practice in a scaled production environment.
> 
> Multiple developers shouldn't link their instances to the same Coveo organization and use the same farm name.
> With this setup, a rebuild in one Sitecore instance deletes all items in your Coveo for Sitecore sources that come from the other linked Sitecore instances.
> Instead, [each developer should use their own trial or test Coveo organization](https://docs.coveo.com/en/2154#have-multiple-development-environments).
> 
> In [a scaled production environment](https://docs.coveo.com/en/3156#sitecore-infrastructure-setup), where multiple Content Management (CM) servers share the same databases, [using the same farm name across all CMs and CDs](https://docs.coveo.com/en/2149/) is ideal.
> This ensures all CMs and CDs pull results from the same public website-related Coveo source (for example, a `Coveo_pub_index - <FARM_NAME>` source).

> **Important**
>
> Changing the **Farm name** in the **Command Center** updates the `<farmName>` element text content in `Coveo.SearchProvider.Custom.config`.
> Similarly, when you change the text content of the `<farmName>` element in `Coveo.SearchProvider.Custom.config`, the **Command Center** reflects this change as soon as you refresh the page.
> 
> However, if you overwrite the **Farm name** value using a patch file of your own, the **Command Center** will detect a difference between the `Coveo.SearchProvider.Custom.config` `Farm name` and the one in the Sitecore compiled configuration.
> When both values are different:
> 
> * The **Command Center** displays the **Farm name** field which contains the `Coveo.SearchProvider.Custom.config` `Farm name` value.
> 
> * The **Command Center** displays the **Effective farm name** field which contains the `Farm name` value you set in your custom patch file.
> 
> * The **Effective farm name** is used for indexing.
> 
> * Coveo for Sitecore disables farm name editing in the **Command Center**.
> 
> ![Effective Farm Name Overrides Coveo Farm Name | Coveo for Sitecore 5](:https://docs.coveo.com/en/assets/images/c4sc-v5/effective-farm-name-overrides-coveo-farm-name.png)

. Click **Apply and Restart**.

> **Note**
>
> Since Coveo for Sitecore configuration files are updated, a restart of the Sitecore instance is triggered.

## Enabling or disabling the reverse proxy

To enable or disable the reverse proxy

. In the **Reverse Proxy Options** section, select or clear **Enable Coveo for Sitecore proxy**.

![Command center change proxy option | Coveo for Sitecore 5](https://docs.coveo.com/en/assets/images/c4sc-v5/command-center-change-proxy-option.png)

. Click **Apply and Restart**.

> **Note**
>
> Since Coveo for Sitecore configuration files are updated, a restart of the Sitecore instance is triggered.