# Fleet management

> How an account groups its drivers, cards and vehicles into fleets and delegates the day-to-day running of each, without handing over account-wide access.

**Fleets** let an account split its drivers, cards and vehicles into groups and hand the running of each group to a fleet manager, without giving that manager control of the whole account. This suits a company that runs charging for its staff and wants each team or site managed on its own. Fleet management is a newer capability, currently in preview and enabled per provider.

## Fleets and accounts

A **fleet** is a grouping inside a single [account](/docs/platform/account-management/providers-accounts-and-users), and an account can hold several. It is an administrative scope, not a billing entity: everything financial, billing plans, [credit limits](/docs/platform/e-mobility-services/credit-limits) and reimbursement, stays at the account and token level. A fleet carries only its identity, its membership, and its own charging rules.

## Members and assets

- **Drivers** belong to one fleet at a time, and their [cards and tokens](/docs/platform/e-mobility-services/cards-tokens-and-access) travel with them: assign a driver to a fleet and their tokens move too; remove them and the tokens leave with them, still assigned.
- **Vehicles** are the fleet's own assets. A vehicle is registered in the fleet and assigned to a driver, one per driver, and when a driver leaves it stays behind with the fleet.

## Managing a fleet

Management rights are granted per fleet, separately from membership, in two roles:

- a **fleet manager**, who runs the fleet: inviting drivers, issuing and assigning cards and tokens (including requesting a batch of new ones), registering and assigning vehicles, setting charging rules and seeing usage,
- and a **fleet observer**, the read-only version.

Grants are given and revoked by the account's or provider's administrators. A manager's reach is limited to the fleets they hold: no account-wide or provider-wide access, and no ability to grant rights to anyone else.

## Charging rules

A fleet sets where and when its drivers may charge through [charging restrictions](/docs/platform/e-mobility-services/cards-tokens-and-access#where-a-card-can-charge). It can carry a **default restriction** for all its members, and gather members into **restriction groups** for tighter rules on some of them, where a driver's group takes precedence over the fleet default.

One thing to watch: a fleet's rules stand on their own. If a fleet sets no default restriction, its members are **unrestricted**; the account's own default does not apply to a driver who is in a fleet. That is deliberate, so a fleet manager can genuinely say "no restriction" for their fleet.

## Usage and sessions

A fleet has its own view of what it has run: its [sessions](/docs/platform/e-mobility-services/sessions) can be searched and exported, and a usage overview breaks spend down over time, by driver and by vehicle, in the account's currency. Each is scoped to the fleet, so a manager sees their fleet and no further.