Power Platform

Dataverse Hierarchy Security - Manager & Position Clear steps, rules and a Position-hierarchy example-styled with Dataverse theme green. Manager Hierarchy - Setup & Notes When to use Use Manager Hierarchy when you want access to flow from a user to their manager(s) based on the Manager field in Azure AD / Entra ID. Important rule The subordinate must be in the same Business Unit or a child Business Unit of the manager. If not, you will see: This user is not a member of the manager's business organization. Quick checklist Table must be User or Team-owned . Record owner must be a User (not a Team). Manager must be assigned in Azure AD (Manager property). Step-by-step (Manager Hierarchy) Go to Settings > User Permissions > Hierarchy Security . Enable Manag...

Every organization must protect its data while ensuring that the right people have access when they need it. Microsoft Power Platform offers a feature called hierarchy security , which makes controlling access easier and more precise, even in complex environments. In this guide, we'll walk you through the basics in plain language. What Is Hierarchy Security? Hierarchy security is an extension of existing security models in Power Platform (like business units, security roles, sharing, and teams). It helps you define who can see what data by building a logical structure based on a company's management or job roles. Essentially, it lets you assign access rights using a "chain of command" or a "position" setup. This method is not only more granular (or detailed) but also reduces the effort required to manage many business units manually. The Two Key Models There are two common ways to organize hierarchy security: 1. Manager Hierarchy The manager hierarchy is ba...