How do you organize your Hexnode policies for different platforms?Solved

Good question! I used to have one big policy per platform. Sounded simpler at first, but it turned into chaos once we added more stuff!

Now I’ve got smaller ones, like one handle device restrictions, another covers network and Wi-Fi settings, and a separate one is just for software updates.

It’s so much easier to make small changes without worrying about breaking something else. Plus, I can reuse policies across teams.

That’s an interesting approach!

For me, keeping one big policy per OS works better. Everything’s in one place, and I don’t have to go policy-hunting whenever I need to tweak something.

If your setup’s small and stable, keeping it simple definitely helps.

Yeah, both make sense depending on your setup.

If you’ve got different roles or departments like IT, Sales, or Design, smaller policies give you way more control.

But if all devices use the same setup, one policy per platform is totally fine. It really comes down to how different your devices are.

We kind of mix both approaches.

There’s a base policy with general stuff like Wi-Fi, passcode, and security settings, and then we’ve got a few smaller add-on policies for specific things like installing apps or setting up VPNs.

It’s flexible and keeps things tidy when new devices join.

Exactly, @ryker ! I’d say both approaches have their place. 

If you’re managing just a few similar devices, a single policy per platform keeps things clean and easy. 

But as the environment grows or when different teams need separate apps or settings, breaking them into smaller, purpose-based policies gives better flexibility. 

We actually follow a hybrid setup; one base policy for common configurations and a few smaller ones stacked for specific needs. It’s been working well so far.