# Config

## Editing .env Configuration File

When trying to configure Concord CRM for your requirements, in some cases, you will need to edit the `.env` file which contains some of the configuration for specific features as well for the advanced features discussed below.

You will often find guides that you will need to edit the `.env` file, in this case, you must make sure to clear the application/configuration cache.

Each time the `.env` file is edited, you must clear the cache in order the new config to take effect, you can clear the cache by navigating to Settings -> System -> Tools and run the clear cache tool or delete the `boostrap/cache/config.php` file, note that if the file does not exists, means that the configuration is not cached.

After the cache has been cleared and you are satisfied with the configuration, you can cache again the application by running the optimize tool.

## Editing Application URL

During installation Concord CRM will ask you for an application URL, the application URL you enter will be store in the `.env` file, in cases where you need to change the application URL for example, because you are migrating your installation to a different domain or you mistakenly added the URL during installation you can achieve this by editing the `.env` file.

The `.env` file is located in the root folder of your installation.

To update the application installation URL you will need to adjust the `APP_URL` env option.

Read more about editing the `.env` file.

## Multiple Installations On Single Root Domain

If you need to perform multiple installations on single root domain probably you will encounter an issue while using one of the installations, the most common issue is getting a 419 - CSRF mismatch error.

For example, installations company1.domain.com and company2.domain.com are considered as multiple installations in a single root domain.

The reason for the error encountered is that Concord CRM uses Laravel Sanctum for authentication as well for it's backend API, Sanctum requires properly configured session domain and CORS.

By default Concord CRM is configured to work with 1 installation on a single root domain, technically, via the root domain is determined which domains the cookie is available to in your application.

In order to have a proper configuration, you will need to configure the session domain for your installation.

On each of your installations, edit the `.env` file in the root of your Concord CRM installation folder and add the following configuration keys:

    SESSION_DOMAIN=subdomain.domain.com
    SESSION_COOKIE=subdomain_session

The `SESSION_DOMAIN` configuration value determines which domain the cookie will be available to the specific installation, make sure to replace the subdomain.domain.com is your actual installation subdomain (without the https://).

Based on the example above, for the first installation the value should be company1.domain.com and for the other installation the value should be company2.domain.com (note that these are example values and you will need to replace them with your actual installation subdomain)

The `SESSION_COOKIE` configuration value determines the name of the cookie used to identify a session instance by ID, this value should be unique for each installation for example, company1_session or company2_session.

Read more about editing the `.env` file.