Policies explained


A policy is a collection of one or more configurations. Each policy can be applied to one or more devices at the same time. In addition, one or more policies can be associated with each device.


Policies are platform dependent. When creating them, care must be taken to determine which platform a policy is created for. For example, an iOS policy cannot be subsequently changed to an Android or Windows policy. Within the Apple operating systems, a distinction is also made between iOS, macOS or tvOS policies and likewise cannot be subsequently changed over.

In the side menu, under Devices > Policies, you will find the overview of the policies that have already been created. A new policy can be created via the Add button. One must specify the target system and a name at this point.


Then Save has to clicked to create a new policy.


All changes to a policy will only take effect after it has been published. This allows to make all configurations and check for completeness without the changes being directly active on linked devices. If changes have made and they have to become active, the Publish button has to be clicked:


Once the policy is published, the next version to be released will be created automatically, so one can continue working comfortably. The version marked with the small icon is the currently released one:



Directives have priorities. The lower number trumps the higher one. So priority 2 wins against priority 3. Each platform has its own priority list. So there can be policies with priority 1 multiple times - each for iOS, macOS, tvOS, Android Classic/ Legacy, Android Enterprise and Windows.

If a configuration, such as that of the restrictions, is created in different policies with different priorities, they complement each other, provided they are not mutually exclusive. If a function is allowed in the restrictions of a policy with priority 4, but prohibited in one with priority 2, it remains prohibited.

To change the priorities, click on the three small dots in the policy overview and select the corresponding menu item.


Automatic assignment

Policies can be assigned to devices automatically during enrollment if enrollment has been configured to do so. To do this, one has to specify within the policy whether or not it should be used for automatic assignment. In addition, you can specify for which users or groups it should take effect. To do this, click on the icons in the upper right corner of the info box.


Here you can select the appropriate options.


Global policies

Now and then, it can be useful to be able to apply identical configurations in several organizations of Relution. To do this, global policies can be created and shared in the store-orga →. These policies can be edited normally in the store-orga, but are only available read-only in the other organizations. To make a policy globally available, it must be published. This process cannot be undone.


Public policies are marked with a check mark in the overview.