> ## Documentation Index
> Fetch the complete documentation index at: https://openwearables.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Priorities

> Decide which data provider and which device type wins when data overlaps in time, from Settings → Priorities in the Open Wearables developer portal.

**Settings → Priorities** decides which data source is shown when more than one source has data for the same period. This matters as soon as a user connects several providers or wears several devices from the same provider.

## Provider Priorities

Use the arrows to reorder the list, then click **Save Changes**. Higher in the list means higher priority.

The list contains every supported provider from the start, seeded with a default order when the API boots. Providers added in a later release are appended below the ones you have already ordered, so an upgrade never reshuffles your configuration.

How it works:

* When data from multiple providers overlaps in time, the higher-priority provider's data is shown.
* Within the same provider, watch data is preferred over phone data by default. You can change that below.

## Device Type Priorities

The second list orders device types within a single provider: **Watch**, **Band**, **Ring**, **Phone**, **Scale**, **Other**, and **Unknown**. When the same provider delivers data from two devices, the higher-priority device type wins.

Reorder with the arrows and click **Save Changes**. The two lists are saved independently.

See [Multi-account sync](/docs/architecture/multi-account-sync) for how data from several connected accounts is merged.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.