# Automation Rules

> Automation Rules in Applivery orchestrate Device lifecycle management by triggering actions based on Device Audience criteria.

Source: https://docs.applivery.com/en/device-management/general-settings/automation-rules/  •  Last updated: 2026-06-12

**Key topics:** automation rules, device audience, actions, policy enforcement, device configuration, Applivery, iOS, Android, Windows, iPhone, Tablet

---

**TL;DR:** Applivery's Automation Rules automate device management by triggering actions based on defined device audience criteria, simplifying configuration and policy enforcement.

**Applivery’s Automation Rules** are a **device orchestration** mechanism that enables administrators to define automated business logic for the **life cycle management** and configuration of mobile and desktop Devices.

An Automation Rule consists of a **Device Audience** definition that, when met, automatically triggers one or more **actions** on Devices that satisfy the criteria.

This allows you to dynamically apply configurations, security Policies, or app deployments without manual intervention.

## Creating an Automation Rule

Once in the [**Applivery Dashboard**](https://dashboard.applivery.io/), navigate to the **Automation** 1 section. Select **Automation Rules** 2 and click the + **Create Automation Rule** button 3.

The configuration form includes the following sections:

### Configuration

-   **Name**: A unique and descriptive identifier for the rule.
    
-   **Description** (Optional): A brief explanation of the rule’s purpose.
    

### Devices audience

The **Device Audience** defines which Devices will be affected by the rule’s actions. Devices are selected based on:

-   **Device tags**: Metadata associated with Devices, such as location (_Madrid_, _Nursing_), operating system (_iOS_, _Android_, _Windows_), or device type (_iPhone_, _Tablet_).
    
-   **Employee tags**: Metadata associated with the user assigned to the Device.
    
-   **Serial numbers**: Explicit selection of individual Devices by their unique serial numbers.
    
-   **Add device / Add employee**: Manually include specific Devices or users.
    

:::info
The rule applies to all Devices that meet **all** criteria defined in the Device Audience (AND logic between selection types).
:::

You can learn more about [**Device Audiences**](https://docs.applivery.com/en/device-management/general-settings/device-audiences/) by following this link.

### Actions

**Actions** define what the system will execute on Devices that match the defined audience. The most common action is to **Set a Policy** 4, which applies a previously defined configuration policy to the selected Devices.

When configuring this action, you specify the **target platform** 5, such as Apple, Android, or Windows, to determine which Devices the Policy applies to.

You also assign a numeric **priority** 6 value, for example, 100. If multiple rules affect the same device, the system applies the Policy associated with the rule that has the **highest priority** (with lower numbers indicating higher priority). This ensures consistent and predictable behavior across the fleet.

![actions for Automation Rules](https://docs.applivery.com/int/_r2/media/09ac0a4e-3ad8-478f-9f15-3474973eec71/9f1166a0-bdbb-41fe-8079-098a694fdc3b.png)

Automation Rules continuously evaluate Devices to determine if they meet the defined audience criteria. When a Device matches, the specified actions—such as applying a Policy—are automatically executed. If the Device no longer meets the criteria, actions can be reverted or updated according to the rule’s configuration. This ensures Devices always reflect the intended settings and simplifies fleet management by enabling automatic segregation and configuration based on metadata.