Policy Conditions

In the context of remote management and monitoring (RMM), policy conditions refer to the rules and criteria established by managed service providers (MSPs) or IT departments to manage and monitor endpoints remotely. Normally, when these conditions are met, decisions are made to trigger actions related to the provision of the agreed service. 

In simpler words, policy conditions refer to some parameters associated with the monitored endpoints that, when met, actions are taken, such actions can be, for example, opening a ticket to the IT department, running an automation, or sending a text message. Typically, conditions reflect problematic situations or issues that require some solution. 

Do Policies in NinjaOne Have Conditions?  

Yes, policies in NinjaOne allow you to enable some predefined conditions and allow the creation of new custom policies, from scratch and from a template. Each policy may have multiple conditions and each condition may have multiple associated automations. Additionally, for each condition, there is a set of parameters that can be set: 

  • Severity: Extent of affectation or impact from this condition (Critical, Major, Moderate, Minor). 
  • Priority: Order or urgency to resolve this issue (High, Medium, or low). 
  • Auto-reset: Indicates whether the condition automatically shuts off after a specified period. This period can be customized. When this option is enabled, and the defined time has passed, if the condition is met again, all associated automations and parameters will be re-triggered. 
  • Channels: This parameter sets the communication channels used to notify when the condition is met, for example, email, SMS, etc. Multiple channels can be selected. 
  • Notify Technicians: this field selects whether to send notifications to technicians. 
  • Ticketing Rule: This field defines if and how a ticket will be created from this issue. Options are: 
  • Off 
  • Create with Default 
  • Create with Server Disk Issue 
  • Create with Server Needs Reboot 
  • Create with Server is Down 
  • Create with Critical Service Down 

Automation refer to some code that is executed as a result when the condition is met. A good example of automation is a PowerShell command to restart a server. 

Where Can I See Examples of NinjaOne Policy Conditions? 

Here are some links to documents containing examples of NinjaOne policies with conditions and automation. 

FAQ

Policy conditions are rules and criteria for managing and monitoring endpoints remotely. These criteria are specified by MSPs or IT departments, and typically when these conditions are met, action is taken to deliver the agreed service. 

Policy conditions specify the rules, guidelines and standards that govern how services are provided, managed, and maintained. These terms are typically outlined in a Service Level Agreement (SLA) and cover various aspects of the service relationship. 

Next Steps

Watch Demo×
×

See NinjaOne in action!

By submitting this form, I accept NinjaOne's privacy policy.