> For the complete documentation index, see [llms.txt](https://docs.expandrive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expandrive.com/expandrive-website/team-deployment.md).

# Team Deployment

Team Deployment gives an organization one place to define ExpanDrive connections and application settings for multiple users and devices. It is available with a [paid license](/pricing-and-licenses.md) through the [ExpanDrive Website](/expandrive-website.md).

An administrator creates a configuration containing drives, app settings, and license controls, then publishes it. A configuration license key associates an ExpanDrive installation with that configuration. Published changes are applied to devices that use the key.

Connections can defer authentication when each user must complete the provider's sign-in flow. Administrators can also prevent users from adding or removing managed drives or changing managed application settings.

## Configurations

A configuration is a predefined set of drives and options for a group of users. Each configuration has a unique license key that retrieves those drives and settings when activated.

For centrally managed Windows installations, the [MSI installer](/installation-and-system-requirements.md#msi-installer) accepts the configuration key through its `LICENSE` property, including during a silent installation. ExpanDrive uses that key to activate and retrieve the assigned drives and settings when the user does not already have a valid activation.

Each configuration contains drive settings, app settings, and license settings. Create, update, and publish configurations in the ExpanDrive Website. Devices activated with the configuration's license key periodically retrieve the published configuration. Local changes to managed items are temporary and are replaced by the published configuration after a successful check-in.

### Drive Settings

Drive settings are defined the same way as connections within the client program, using the parameters of each connection type.

Enable [Connect Automatically](/connections/connection-creation-and-removal.md#automatic-connections) for drives that should mount when ExpanDrive starts. This lets users access their configured drives after logon without manually connecting each one. Any required sign-in still needs to be completed.

When adding a drive to a configuration, you can enable *Defer Authentication* to mount a drive before the user has authenticated with that storage service. The user is prompted to authenticate the first time they interact with the drive. Defer Authentication is useful for OAuth services where each user must complete their own sign-in flow.

### App Settings

Use the app settings for a configuration to manage application-level options for the end user.

The *Hide Window* setting starts ExpanDrive with its main window hidden, so users can work with their mounted drives without the application window opening at each launch. This setting can be supplied through the desktop app's settings file or a Team Deployment configuration. Enable [Managed settings](#license-settings) to prevent users from changing the settings supplied by the configuration.

For drives to mount at startup, also enable their *Connect Automatically* setting.

OneDrive and SharePoint configurations support a single sign-on option where available. To enable SSO, add the domain of the end user's sign-in email address in the *Domain hint* field.

### License Settings

Two global license settings control what users associated with the configuration can change. Enabling *Managed connections* prevents a user from adding or removing drives. Enabling *Managed settings* prevents a user from changing settings supplied by the configuration.

## Users

The *Users* list shows which users are active, when they last used ExpanDrive, and which configuration they are assigned.

You can create users by email address. Users are also added automatically when they activate a configuration license key. You can change a user's assigned configuration or remove the user.

## Devices and Seat Count

Each user in the Users list has a device count showing the number of distinct devices that have activated a configuration or license key for that user. Activating ExpanDrive on another device adds that device to the count.

The number of license seats used is the higher of the account's total user count or total device count. If one user activates ExpanDrive on multiple devices, each device can count toward the plan's seat limit.

The *Devices* page lists active desktop devices, including their assigned user, configuration, platform, and *Last Seen* date. The Last Seen value is informational; inactive devices do not expire from the list automatically. Disable a stale device from this page when it should no longer count as active. The record remains in account history, but the disabled device is not included in the active device count.