Addigy Policies allow you to automate deployments in a custom hierarchy format uniquely structured for your tenant.
If you manage devices for multiple organizations, you may want to create a top-level ("Parent") policy that deploys certain general items to all organizations/locations in your tenant, then multiple Child policies to deploy different assets to each individual organization. Furthermore, you could create Child Policies within those Child Policies to deploy a separate set of assets to each department within an organization (for example, specific software for the Marketing department vs. the Engineering department).
If you are managing devices for education, the hierarchy structure could be used to separate student devices from teacher devices and/or enforce different levels of restrictions by grade or classroom.
In any case, it is important to understand the rules of inheritance when using policies, described below.
Child Policies will inherit the following items when deployed to a parent (top-level) Policy:
- Software (Smart and Public)
- MDM and DDM System Updates
- MS Office Updates
- MDM Profiles
- Monitoring Items
- Maintenance Items
- OS Users
- Apps & Books Apps (Assets)
- Addigy Identity
- MDM Enrollment Profiles
- Malwarebytes OneView
- Home Screen Layout
- Compliance
- Self Service configurations
- Conditional Access
- Software deployment schedules
Child Policies will not inherit:
- Autotask
- BrightGauge
- FreshDesk
- ITGlue
- ZenDesk
- Apps & Books Tokens *
- By default, if a token is not present in a child policy but is present in a parent, it will still inherit the apps from the parent. This behavior can be adjusted and we recommend viewing this article for further details on Apple Apps Policy inheritance.
- Automated Device Enrollment Settings and Tokens
- Splashtop Settings
- The 'Application in Use' setting for MS Office Updates
Special cases:
- LiveTerminal, LiveDesktop, and Splashtop will only inherit disabled settings. For example, if Splashtop is disabled in the parent but enabled in the child, it will not install/enable on devices assigned to the child policy.
- If the parent policy has Splashtop enabled while the child policy has Splashtop disabled, it will not install/enable Splashtop on devices assigned to the child.
- If a device is added to a Flex Policy, it will take the Location (root policy) settings. For example, if the Location has LiveDesktop enabled and the Flex Policy has LiveDesktop disabled, the device will keep LiveDesktop enabled.