# Configuration Priority

> How CapaOne decides which configuration applies when a device is assigned more than one, across Windows, Android, and Apple.

Source: https://docs.capaone.com/capaone/reference/configuration-priority/  
Product: CapaOne — a separate CapaSystems product; do not apply this page to any other.

Priority determines which configuration applies when a device is assigned to more than one
configuration at the same time. This works the same way across Windows, Android, and Apple.

## How priority works

Every configuration has a priority value where **1 is the highest priority** — lower numbers
take precedence over higher ones. Think of it like a ranking: 1st place beats 2nd place.

Priority only comes into play when the same device is covered by multiple configurations — for
example, because it belongs to two groups that each have a different configuration assigned, or
because it has both a direct assignment and a group assignment.

When that happens, the configuration with the **lowest** priority number wins.

If a device is only assigned one configuration, priority is irrelevant — that configuration
always applies.

## Practical example

A device is a member of two groups: **All Devices** and **Developers**.

- The All Devices group has a Standard Privileges configuration assigned (priority 20).
- The Developers group has a Developer Privileges configuration assigned (priority 2).

Because the device is in both groups, it receives both configurations. Priority resolves the
conflict: the Developer Privileges configuration (priority 2) wins because it has the lower
number.

A device that is only in the All Devices group receives only the Standard configuration — there
is no conflict, so priority does not matter for that device.

## Reordering priorities

In Android and Apple Configurations, the **Change priority for configurations** button opens a
view where you can drag and reorder all configurations at once, rather than editing each one
individually. Use this when restructuring your priority scheme.

## Conflict resolution

If two configurations have the **same** priority number and both apply to the same device, the
behaviour is undefined — one of them will apply but the result may not be predictable. Avoid
duplicate priority values for configurations that could overlap on the same device.

## Good to know

- **Lower number = higher priority** — priority 1 always wins over priority 10. Think of it as
  a ranking where 1st place is the winner.
- **Priority is per-platform** — Windows configuration priorities are separate from Android and
  Apple priorities.
- **Unassigned configurations have no effect** — a configuration with any priority value only
  matters if it is assigned to at least one endpoint or group.
- **Check effective configuration** — if a device is not behaving as expected, open its detail
  page and review which configurations are currently applied and their priority values.