Policies provides a flexible way to control behavior across your environment.

Instead of managing many separate settings, Policies organizes configuration into reusable components that can be applied at different levels (environment, tenant, group, user, etc.).

To find Policies Navigate to Evo Admin → Policies

Hit New+ on the top right to create your new Policy

From here you can name your Policy and then start adding settings

Once you’ve named your Policy and have chose your Policy settings you can then Create your Policy

After Created you can now assign your Policy a scope.

When applying a Policy there are 5 Categories of Scopes available

Policies is built around five key components:

Together, these allow you to create a baseline configuration and apply more specific rules where needed.

A Policy is a collection of configuration settings that define how the platform should behave.

Create policies with a clear purpose, such as:

A Policy Group is a collection of policies that can be assigned together.

This helps keep policies organized and reusable.

Instead of creating one large policy, you can:

Policies inside a group have an evaluation order.

If two policies contain conflicting settings:

Policy Settings are the individual controls inside a policy that determine how the platform behaves.

For example, settings may control things like:

All settings come from a built-in settings catalog within the platform. This ensures every setting:

This helps prevent invalid configurations and ensures consistent behavior across environments.

Scopes define where a policy applies.

Policies can be assigned to different levels of your environment.

Scopes allow you to create:

Policies only take effect when they are assigned to a scope.

Assignments can target:

This allows the same policy to be reused across multiple targets.

Note: A single policy can be assigned to multiple scopes. For example, a policy may be applied to multiple users, or to a combination of scopes such as a user and a group.

The Entity Inspector determines the final effective configuration for a specific user, device, or entity.

It evaluates all policies that apply across different scopes.

Policies are processed from broadest to most specific:

The Entity Inspector evaluates policies from the broadest scope to the most specific.

This means the system first applies policies at the environment level, then continues through more targeted scopes such as tenant, group, user, and endpoint.

At each step, a more specific scope can refine or override settings applied by broader scopes. This allows you to define a global baseline while still supporting targeted exceptions when needed.

The Policy Hierarchy page provides a structured view of how policies and policy groups are assigned across your environment.

The hierarchy displays:

The Policy Hierarchy helps partners:

It is especially useful when used alongside the Entity Inspector, which shows the final effective configuration for a specific entity.

Policies uses role-based access control (RBAC) to determine who can view or manage policies.

These Roles can be assigned under Evo Admin → Permissions → Roles → Your Specific Role Group → Policies

The Administer Global Policies role provides full administrative access to Policies. Users with this role can create, edit, assign, and manage policies and policy groups across the environment.

The Policy View role provides read-only access to Policies. Users can view policies, assignments, and policy details but cannot make changes.

The Administer Global Policy role allows a user to modify the default environment policy, which serves as the global baseline for the environment.

This permission is separate because changes to the default policy can affect the entire environment.

Use the default environment policy to define global behavior.

Use tenant, group, or user policies only when needed.

Smaller, purpose-driven policies are easier to manage.

If multiple policies should always be applied together, create a policy group.

Too many narrow exceptions can make environments harder to manage.