Introduction

Automations are used to streamline certain tasks. This includes automatically applying specific policies to devices based on their tenant, location, or group name. In the future, you will also be able to automate database tasks here.

Policy Assignment

Automatically apply policies based on device attributes like tenant, location, or group

Condition-Based

Define conditions to determine when and where automation rules should apply

Add New Policy Automation

In the navigation panel, click on Automations.

Define the name

Give your automation rule a descriptive name

Select the category Policy

Choose Policy as the automation category

Select the 'if' condition

Determine what kind of data should match to decide whether the policy will be assigned or not

Enter the condition value

For example, select the 'if' condition Tenant and enter the tenant's name your devices are in

Select the policy

Choose the policy you wish to assign automatically

Click Confirm

Save the automation configuration

Now, if a device synchronizes with the backend and the data matches the condition, the defined policy will be automatically synced, including all sensors, jobs, and more.

Automation Matching Priority

When multiple automation rules exist, the system checks them in the following order. The first matching rule is applied, and all remaining conditions are skipped.

Priority	Compared Value	Description	Notes
1	Device Name	Matches the rule if the automation's expected result equals the device's name.	Highest priority. Applied immediately when matched.
2	Tenant Name	Matches if the automation applies to the device's tenant.	Checked only if no device name rule matched.
3	Location Name	Matches if the automation applies to the device's location.	Checked after tenant-level rules.
4	Group Name	Matches if the automation applies to a specific device group.	Useful for organizing devices into logical groups.
5	Internal IP Address	Matches based on the device's internal network IP.	Used for network- or subnet-based automations.
6	External IP Address	Matches based on the device's external (public) IP.	Helps apply rules per site or shared internet connection.
7	Domain	Matches the rule if the device belongs to the specified domain.	Lowest priority; used as a fallback condition.

Matching Logic

The system checks each condition in order from top to bottom.
As soon as a match is found:
- • The corresponding policy is applied.
- • The process stops; no further conditions are evaluated.

Summary

The priority follows this hierarchy:

Device → Tenant → Location → Group → Internal IP → External IP → Domain

This ensures that the most specific rules (e.g., device-level) override more general ones (e.g., domain-level).