Policy configuration (New)
Policies define configuration rules that apply consistently to groups of devices. Instead of configuring settings individually on each asset, you define rules and associate it with one or more tags. N-sight then applies those settings to all assets with those tags.
Why policies matter
By using policies, you can:
- Centralize configuration management.
- Reduce conflicting settings.
- Ensure consistent configuration across devices.
- See how configurations are defined and applied.
The sections that follow explain how policies work, including policy types, permissions, targeting, and priority.
How policies work
Before you create or deploy policies, review the following information to understand how policies are scoped, applied, and resolved.
Access to policy management requires an N-able user account that is linked to N-able SSO.
Policy types
A policy type defines the service a policy controls, such as Monitoring, Backup, or Patch.
Currently, Patch is the only available policy type. Support for additional policy types will be added in future releases.
Permissions and access
Your ability to manage policies depends on your assigned permissions. For each policy type, you can have one of the following access levels:
- Write: Create, edit, deploy, and delete policies.
- Read: View policies but not modify them.
- No access: Can’t view or manage policies of that type.
Policy permissions are separate from permissions for the underlying service.
Manage access to policies under Settings > Users > Roles and Permissions.
Tags and targeting
Tag targeting determines which devices receive a policy.
When you create a policy, you target one or more tags. After the policy is deployed, its settings apply to all assets that have the targeted tags. To understand tags, and to create tags, see Tag Management (New).
-
Policies target tags. Plan your tagging structure before you create policies. You can create tags in advance or create them directly from the policy creation wizard if you have the required permissions. If you have write permissions for both policies and tags, select Add tags in the policy creation wizard to create the tags you need.
-
A tag can target one policy of each type per OS type, allowing you to reuse policies across different OS types. For example, a Windows Patch policy and a macOS Patch policy can target the same tag because they apply to different OS types.
If a tag includes assets with different OS types, the policy applies only to assets that match the policy's OS type. For example, if a Windows Patch policy targets a tag that includes both Windows and macOS devices, the policy applies only to the Windows devices.
Policy Scope
The organization you select on the Policies page sets the context for managing policies. It determines which policies and tags you can create or manage and which local and inherited policies you can view.
When you select a different organization, the Policies page updates to show the policies for that organization.
A policy and the tags it targets must belong to the same organization.
Policy inheritance
You can create policies at different levels of your organization, such as the Service Organization, Customer, or Site level. Policies created at a higher level are inherited by organizations below that level. This lets you apply common settings across your organization while using local policies when individual customers or sites need different settings.
Policies created for one child organization aren't visible to sibling organizations. For example, a policy created for one customer isn't visible to another customer. However, both customers can see policies inherited from their parent organization.
The Policies page groups policies into:
-
Local policies: Policies created at the organization you are currently viewing. You can modify local policies if you have the required permissions.
-
Global policies: Policies inherited from a parent organization. You can view their configuration and the assets they apply to, but you can't modify them from the lower organization.
- Policies use tags to determine which assets they apply to. Creating a policy at a particular organization doesn't automatically apply the policy to every asset in that organization.
Policy priority and conflict resolution
When more than one policy of the same type applies to an asset, two factors determine which policy takes precedence:
- Organization level: A local policy takes precedence over a global policy inherited from a parent organization.
- Policy order: If multiple policies at the same organization level apply to the asset, the policy with the higher priority in the policy order takes precedence.
Local and global policies have separate policy orders.
For example, if an asset is targeted by both a local policy and an inherited global policy, the local policy takes precedence. If two local policies target the same asset, their policy order determines which policy takes precedence.
An asset can have multiple tags. When more than one tag targets a policy of the same type, the system automatically resolves the conflict.
When you withdraw or delete a policy, the system automatically applies the next highest-priority policy, if one is available.
For information about creating, deploying, editing, and deleting policies, see Work with policies.
