We heard you! Your patch policies work great at the Service Organisation level, but your customers needed more flexibility. We’re excited to introduce Multi-level Policy Management, giving you the power to tailor patch configurations to each customer and site. Moving beyond one-size-fits-all policies—now you can manage patches strategically across your entire infrastructure with targeted overrides for customers or sites with unique needs.

What’s New

Multi-level policy management
Create and manage policies at three levels: Service Organisation, Customer, and Site. Use the Scope Selector at the top of the policies grid to switch between organisations and apply configurations where they’re fit best.

Automatic inheritance with local override.
Policies cascade down your organisational hierarchy automatically. Set baseline policies at any level, and more specific policies lower in the hierarchy override inherited policies on assets where there is conflict. Everything updates seamlessly—no manual intervention, no conflicts.

See effective assets before you deploy.
Policy overrides help you build a comprehensive infrastructure. View exactly which assets each policy is deployed to in the policy summary page of policy details—no more guessing whether you’ve applied the right configuration.

Create tags without leaving the workflow.
Don’t have the right tags? No more switching between screens—build them on the fly using the Add tags button on the Assets targeting step of policy creation.

Best Practices

Establish base policies at Service Organisation level. Create your baseline policies here for org-wide coverage. Reserve Customer and Site-level policies for special rules specific to certain customers or locations.

Keep base policy names generic. Avoid including customer names in policy titles. Since SO-level policies are inherited and visible to lower-level admins managing co-managed customers, keep names descriptive of the rule itself, not the customer.