# Fleet Manager

## Enabling the Fleet Manager

To enable the fleet manager, your `values.yaml` file should contain:

```
global:
  fleetmanager:
    enabled: true
```

If you use our [BYOC](https://docs.groundcover.com/architecture/byoc) service, we will enable the fleet manager for you. However, the above is still needed for groundcover's sensors in your environments to connect to the fleet manager.

If you manage your own backend, for example in [on-premise](https://docs.groundcover.com/customization/customize-deployment/on-premise-deployment) and in [air-gapped](https://docs.groundcover.com/architecture/overview#airgapped) deployments, the above configuration will enable the fleet manager deployment as well as configure the sensors to connect to it.

## Remote Configuration

Remote configuration is a mechanism that allows groundcover's services, including sensors, to be configured dynamically and remotely. The configurations are stored alongside the fleet manager and are passed from the fleet manager to the services.

{% hint style="info" %}
For remote configuration to work, services need to be able to communicate with the fleet manager. For this, they need to be configured with a suitable [ingestion key](https://docs.groundcover.com/use-groundcover/remote-access-and-apis/ingestion-keys).
{% endhint %}