You can reorganize your Policy hierarchy at any time by moving a Policy to a different parent Policy or promoting it to the top level. When you move a Policy, all of its child Policies move with it.
Warning: Moving a Policy may cause conflicts if the destination already has overlapping settings for features like Addigy Identity, Automated Device Enrollment, or Compliance. Review your target location carefully before confirming the move.
Supported Moves
Policies can be repositioned in the following ways:
- Promote a child Policy to the top level
- Move a top-level Policy under another Policy as a child
- Move a child Policy under a different parent Policy
How to Move a Policy
- Open the Policy you want to move and navigate to its Overview tab.
- Scroll down to the Move Policy section and click Move Policy.
- In the dialog that appears:
- The left side shows the Policy (and any children) that will be moved.
- The right side shows the available destination Policies.
- Select a new parent Policy from the list, or select Move to top-level to make it a root Policy.
- Click Move, then click Yes, do it to confirm.
The Policy and all of its children will immediately appear under the new location in your Policy hierarchy.
Important Considerations
Inherited settings can affect devices
Child Policies inherit settings from their ancestor Policies. Moving a Policy under a new parent means it will begin inheriting that parent's settings — including Identity, Automated Device Enrollment, Compliance configurations, and more. This can cause unintended changes to the devices assigned to that Policy and its children. Always review the destination Policy's settings before confirming a move.
The entire subtree moves together
When you move a Policy, all of its children and descendants move with it. The internal structure of the subtree is preserved — only its position in the hierarchy changes.
Consider top-level Policies with Auto-Assignment as an alternative
If managing inherited settings across a nested hierarchy is becoming complex, consider using top-level Policies with Auto-Assignment rules to target devices instead. This approach gives you more control over which settings apply to which devices without relying on inheritance.