Policy & rule hierarchy

Policies are applied in the following order:

Example: A policy applied to joe.bloggs@example.com is evaluated before any domain-specific policy or the organization’s default policy.

For more information, see Policy templates.

Rule categories are applied in the following order:

Example: An edge custom rule is evaluated before all other rule categories.

Custom rules are evaluated in the following order. Within each scope, additional ordering applies based on the rule type.

Applied to: 

Rule type: 

Example: An edge custom rule created for the user erich.zann@meshsecurity.io to deliver email from skinner@example.com is evaluated before other custom rules.

Allow and block rules are evaluated in the following order. Within each scope, additional ordering applies based on the rule type.

Applied to: 

Rule type: 

Example: An allow rule created for the user hans.moleman@meshsecurity.io to deliver email from john@example.com is evaluated before other allow or block rules, but after edge and custom rules.

The following tables illustrate the order of execution.

The filter processes the rules in this order: Table 1 > Table 2 > Table 3 > Table 4.

If no matching rule is found, the filter proceeds to the next check.

If a matching rule is found and executed, processing stops and subsequent rules are not evaluated.

For more information, see Rules.