SkieCan different departments have different rules in Skie?
Yes. Make each department a group, and attach its own policy and app list. Sales can have maps and a CRM, accounts can have a finance app, and the warehouse can have a stock scanner. Rules set higher up flow down, and the most specific level applies last, so a department can tighten or add without breaking the baseline.
Companies are not uniform. A rule that suits a delivery team is too strict for managers, and a rule that suits managers is too loose for a shared kiosk.
Skie handles this with its structure: organisation, branch, group, device. Each group has one policy from the policy library and one app list. You can fork a policy to start a variant, and the library tracks ownership. Before you save a change, the impact preview shows which devices it will affect, and the where-used and effective policy views show which rule a particular phone is following.
Precedence is simple. Rules flow down from the organisation. The most specific level applies last, and blocking beats allowing. So a company-wide block on VPN apps cannot be overridden by one department's list. If you want something tighter for one team, set it at the group.
Roles match the structure. A department head sees their own devices and users. Page access can be switched per role, so a team lead need not see location data. Insights show readiness, compliance, devices on the latest policy and open events per device by group, which helps you see which department is lagging.
A practical tip: keep the baseline short and put department-specific apps at group level. That makes later changes quick and keeps one-off exceptions from piling up in the top-level policy.