What is a Policy Override and how does it work?
Kaseya has a concept of Policies. These are a set of configuration values that you can apply to Organisations, Groups or machines.
The benefits of using policies are numerous (and outside the scope of this article), but in brief, they allow you to make a change to a single policy and the system will apply that change to all the machines assigned, rather than you having to change the setting on a per machine basis.
Imagine you have a policy that sets the agent menu to "enabled".
You apply this policy to all 1,000 of your machines. However, there are 3 machines where you don't want the agent icon to appear.
You wouldn't want to create a policy just for those 3 machines and another policy for the other 997, so Kaseya has the concept of an override.
You can go to the Agent tab -> Agent Menu page and change the settings for those 3 machines. This creates an override.
Kaseya now knows that you do not want the policy to change those settings. When the policies are next applied, either manually or automatically, the agent menu for those machines will not be altered.
If this was not the case, then each time the policy is re-applied, your 3 machines would have their agent menu re-enabled and you would have to manually change it to disabled - you would be in a constant battle with the policy function
Should you later decide that you do not want this particular setting to be different, you can you the Policy tab -> Machines page -> Clear Override button on those machines to remove the override. the next time that the policy is applied, the agent menu will be brought back in line with the policy.