Study guide
3.2 Security Roles, Privileges & Depth Levels
Microsoft Power Platform Functional Consultant PL-200
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Dataverse Tables, Relationships & Core Columns
1.1 Dataverse Table Types, Properties & Ownership 1.2 Table Relationships & Cascading Rules 1.3 Column Types, Formats, Primary Keys & Alternate Keys 1.4 Rollup, Calculated & Formula Columns with Power Fx
2 Chapter 2: Dataverse Data Management & Governance
2.1 Dataverse Search, Quick Find & Relevance Indexing 2.2 Auditing Configuration & Log Management 2.3 Duplicate Detection Rules & Settings 2.4 Bulk Record Operations, Data Import, Export & Templates
3 Chapter 3: Dataverse Security Model & Access Control
3.1 Business Units, Ownership Models & Modern BU Matrix 3.2 Security Roles, Privileges & Depth Levels 3.3 Teams Architecture: Owner, Access, and Microsoft Entra (AAD) Group Teams 3.4 Column-Level Security & Hierarchy Security Models
4 Chapter 4: Model-Driven App Fundamentals & Information Architecture
4.1 Model-Driven App Design, Site Map Navigation & Modern App Designer 4.2 Form Types: Main, Quick Create, Quick View & Card Forms 4.3 View Configuration, System Views, Personal Views & Filters
5 Chapter 5: Advanced Model-Driven App Components & Custom Pages
5.1 Custom Pages & Modern Commanding with Power Fx 5.2 Form Component Controls & Specialized UX Elements 5.3 Embedding Canvas Apps in Model-Driven Forms 5.4 Embedding Power BI Reports, Dashboards & Tiles
6 Chapter 6: Canvas Apps Structure, Formulas & Data Operations
6.1 Canvas App Architecture, Screens, Containers & Controls 6.2 Power Fx Formulas, Delegation & Data Source Limits 6.3 Variables (Context, Global), Collections & State Management 6.4 Triggering Power Automate Cloud Flows from Canvas Apps
7 Chapter 7: Power Pages Site Design, Navigation & Content
7.1 Power Pages Design Studio & Site Structure 7.2 Power Pages Templates, Styling & Responsive Layouts 7.3 Web Pages, Navigation Menus & Content Snippets
8 Chapter 8: Power Pages Data Integration, Forms & Web Roles
8.1 Power Pages Lists, Basic Forms & Advanced Forms 8.2 Table Permissions, Web Roles & Page Access Security 8.3 External Identity Providers & Authentication Configuration
9 Chapter 9: Power Automate Cloud Flow Fundamentals & Triggers
9.1 Cloud Flow Types: Automated, Instant, Scheduled & Desktop Overview 9.2 Dataverse Connector Triggers & Operational Filters 9.3 Standard Connectors, Custom Connectors & Connection References
10 Chapter 10: Cloud Flow Actions, Expressions & Logic Controls
10.1 Logic Controls: Conditions, Switches, Apply to Each & Do Until Loops 10.2 Variables, Data Operations & Dynamic Content Manipulation 10.3 Power Automate Expression Language (WDL / Functions) 10.4 Error Handling, Configure Run After & Scope Controls
11 Chapter 11: Business Process Flows & Guided Processes
11.1 Business Process Flow Architecture, Stages, Steps & Data Steps 11.2 Branching Rules & Multi-Entity Business Process Flows 11.3 BPF Action Steps, Workflows & Cloud Flow Execution 11.4 BPF Security Roles, Order & Process Lifecycle
12 Chapter 12: Classic Workflows, Business Rules & Modern Logic Extensibility
12.1 Classic Dataverse Workflows: Real-Time vs. Background (Async) 12.2 Business Rules: Scope & Actions 12.3 Low-Code Plug-ins in Dataverse: Automated vs. Instant 12.4 Troubleshooting Automations, Run History & Analytics
13 Chapter 13: Power Platform Environment Architecture & Security
13.1 Environment Types: Default, Sandbox, Production, Trial, Developer 13.2 Environment Governance, Groups, Routing & Capacity Management 13.3 Data Loss Prevention (DLP) Policies & Connector Classifications
14 Chapter 14: Application Lifecycle Management (ALM) & Solutions
14.1 Unmanaged vs. Managed Solutions & Solution Layering Mechanics 14.2 Solution Components, Dependencies, Publishers & Prefixes 14.3 Exporting, Importing, Upgrading & Patches 14.4 Solution Checker, App Checker & ALM Best Practices
15 Chapter 15: Enterprise Interoperability & Service Integration
15.1 Exchange / Server-Side Synchronization & Email Integration 15.2 SharePoint & OneDrive Document Management Integration 15.3 Microsoft Word & Excel Document Templates
16 Chapter 16: Copilot, AI Capabilities & Exam Strategy
16.1 Copilot Studio & Generative AI across Power Platform 16.2 AI Builder Prebuilt & Custom Models in Apps and Flows 16.3 PL-200 Exam Strategy, Time Management & Question Analysis
3.2 Security Roles, Privileges & Depth Levels
Key Takeaways Explain This Topic AI
Dataverse security roles enforce granular authorization across 8 core record-level privileges: Create, Read, Write, Delete, Append, Append To, Assign, and Share.
Privilege depth defines the organizational scope of an action, categorized into 5 tiers: None, Basic (User), Local (Business Unit), Deep (Parent-Child Business Units), and Global (Organization).
The Append and Append To privileges operate in tandem: 'Append' permits attaching other records to the current entity, whereas 'Append To' permits the current entity to be attached to another record.
Dataverse evaluates security roles cumulatively: when a user holds multiple roles directly or via team memberships, the system grants the least restrictive (most permissive) union of privileges.
Application Lifecycle Management (ALM) best practice dictates creating custom security roles by copying out-of-the-box templates inside an unmanaged solution rather than modifying default system roles directly.
Last updated: August 2026
3.2 Security Roles, Privileges & Depth Levels
Security Roles in Microsoft Dataverse constitute the core mechanism for defining what actions a user or team can perform on specific records, tables, and system components. Rather than managing individual user permissions on an ad-hoc basis, Dataverse groups capabilities into Security Roles composed of granular Privileges configured at distinct Depth Levels .
Mastering privilege depth mechanics, the interaction between relational privileges like Append and Append To , and the cumulative evaluation algorithm is essential for designing robust, least-privilege enterprise architectures.
1. The 8 Core Record-Level Privileges
For every User/Team-owned table in Dataverse, security roles provide eight distinct record-level privileges that govern the complete lifecycle of data entities. +-----------------------------------------------------------------------------------+
- | THE 8 DATAVERSE RECORD-LEVEL PRIVILEGES |
- | |
- | [CREATE] --------> Instantiates a new record row in the table |
- | [READ] --------> Views record data in forms, views, reports, and API queries|
- | [WRITE] --------> Modifies existing column values on an active record |
- | [DELETE] --------> Permanently deletes or deactivates the record |
- | [APPEND] --------> Attaches ANOTHER entity record to THIS record |
- | [APPEND TO] ------> Attaches THIS record to ANOTHER entity record |
- | [ASSIGN] --------> Changes the owner (systemuser/team) of the record |
- | [SHARE] --------> Grants ad-hoc read/write/share rights via POA table |
- +-----------------------------------------------------------------------------------+
- Detailed Privilege Breakdown
Create: Grants permission to instantiate a new record row. The user's depth level for Create dictates in which Business Unit the record can be created.
Read: Grants permission to view record data in model-driven forms, canvas galleries, Power Pages lists, system views, Power BI reports, and Dataverse Web API endpoints.
Write: Grants permission to edit and update existing column values on an existing record row. (Note: Modifying sensitive individual columns can be further restricted by Column-Level Security).
Delete: Grants permission to permanently remove a record from the database.
Append (The "Container" Right): Grants the right to attach other records to this record. Think of this as opening the record's pocket to hold child records.
Append To (The "Passenger" Right): Grants the right for this record to be attached to another record. Think of this as permission for this record to climb into another record's pocket.
Assign: Grants permission to transfer ownership of a record to another user or team. Assigning a record updates the ownerid and owningbusinessunit fields.
Share: Grants permission to delegate specific access rights (such as Read or Write) on an individual record to another user or team without transferring ownership.
The "Append" vs. "Append To" Rule
To link two records together via a 1:N or N:N relationship (such as linking a Contact to a parent Account ):
The user MUST have the Append To privilege on the Parent entity (Account) because the Account is being appended to .
The user MUST have the Append privilege on the Child entity (Contact) because the Contact is being appended into the Account relationship. +-----------------------------------------------------------------------------------+
- | APPEND VS. APPEND TO MECHANICS |
- | |
- | SCENARIO: Link Contact 'Alice' to Parent Account 'Contoso Corp' |
- | |
- | +--------------------------+ +--------------------------+ |
- | | ACCOUNT (Parent) | | CONTACT (Child) | |
- | | 'Contoso' | <================ | 'Alice' | |
- | +--------------------------+ +--------------------------+ |
- | Requires: [APPEND TO] on Account Requires: [APPEND] on Contact |
- | (Permission to be target of link) (Permission to link into target) |
- +-----------------------------------------------------------------------------------+
- 2. Privilege Depth Levels (Visual Circles & Hierarchy Scopes)
Privilege depth determines the organizational scope across the Business Unit hierarchy tree in which a user can exercise a specific privilege. In the modern Power Platform Admin Center and classic role editor, these are represented by concentric circular symbols. +-----------------------------------------------------------------------------------+
- | DATAVERSE PRIVILEGE DEPTH LEVELS MATRIX |
- | |
- | Symbol Depth Tier Organizational Scope |
- | ----------------------------------------------------------------------------- |
- | [ ] Empty None No privilege granted for this action. |
- | (•) 1/4 Basic (User) Records owned by the user or shared with user. |
- | (◐) 1/2 Local (BU) Records owned by ANY user/team in the user's BU|
- | (◕) 3/4 Deep (Parent-Child) Records in user's BU + ALL descendant child BUs|
- | (●) Full Global (Organization)Records across the ENTIRE environment. |
- +-----------------------------------------------------------------------------------+
- Detailed Depth Tier Analysis
Depth Tier UI Visual Scope Boundary Operational Behavior
None Empty Circle None The user has zero access to execute this operation on the table.
Basic 1/4 Filled User / Individual User can only perform the action on records they personally own, records owned by teams they belong to, or records explicitly shared with them.
Local 1/2 Filled Business Unit User can perform the action on records owned by any user or team belonging to the user's own Home Business Unit.
Deep 3/4 Filled Parent-Child BUs User can perform the action on records owned by users/teams in their own BU plus all descendant child BUs under their BU in the hierarchy.
Global Full Filled Organization User can perform the action on any record in the table across the entire Dataverse environment, regardless of BU ownership.
Note
For Organization-owned tables, only None and Global (Organization) depth levels are supported because organization-owned records do not carry an owningbusinessunit or ownerid attribute.
3. Miscellaneous & Administrative Privileges
Beyond table-level CRUD permissions, Dataverse security roles control global features, admin capabilities, and platform tooling via miscellaneous privileges distributed across various functional tabs:
Core Records Tab: Controls global features like Export to Excel , Mail Merge , Bulk Edit , and Print Records .
Business Management Tab: Governs organizational settings, currency management, fiscal year settings, and user administration.
Customization Tab: Controls solution authoring, entity customization, and the critical Publish Customizations ( prvPublishCustomizations ) privilege.
Service Management / Sales Tabs: Controls queues, knowledge base articles, products, and routing rules.
Critical Administrative Privileges:
Act on Behalf of Another User (Impersonation): Required for background integration flows, sync tools, and web services that execute API calls impersonating a target user identity ( prvActOnBehalfOfAnotherUser ).
Execute Workflow Job / Cloud Flows: Allows users to trigger background automations and on-demand cloud flows.
View Audit History / Partition Logs: Allows security officers and compliance leads to inspect historical change tracking data.
4. Cumulative Privilege Evaluation & ALM Governance
When a user logs into a Power Platform app or executes an API call, Dataverse dynamically calculates the user's effective permissions using a cumulative union model. +-----------------------------------------------------------------------------------+
- | CUMULATIVE PRIVILEGE EVALUATION LOGIC |
- | |
- | Direct User Security Role: |
- | - Account Table: Read = Basic (User Depth) |
- | - Contact Table: Write = None |
- | + |
- | Team A (Owner Team) Security Role: |
- | - Account Table: Read = Local (Business Unit Depth) |
- | - Contact Table: Write = Basic (User Depth) |
- | + |
- | Team B (Entra ID Group Team) Security Role: |
- | - Account Table: Read = Global (Organization Depth) |
- | - Contact Table: Write = None |
- | || |
- | v |
- | EFFECTIVE CUMULATIVE PERMISSIONS: |
- | - Account Table: Read = GLOBAL (Organization Depth) [Most Permissive Wins!] |
- | - Contact Table: Write = BASIC (User Depth) [Least Restrictive Union] |
- +-----------------------------------------------------------------------------------+
- Cumulative Privilege Rules
Most Permissive Wins: If Role 1 grants Local (BU) Read on Accounts and Role 2 grants Global (Organization) Read on Accounts, the user's effective Read privilege is Global .
No Subtractive Roles: In Dataverse, security roles are purely additive . You cannot create a "deny" role that subtracts or revokes a privilege granted by another assigned role.
User-Depth Team Privileges: If a user receives a security role with Basic (User) privilege depth through an Entra ID Group Team, the user can act on records owned by the team or records they own personally (if configured for Direct User access).
Application Lifecycle Management (ALM) Best Practices
Never Edit Default Out-of-the-Box Roles: Never modify out-of-the-box system roles like Basic User , Salesperson , or System Customizer directly in the Root BU. Future Microsoft platform updates can overwrite standard role definitions.
Copy and Customize in Solutions: Always use the Copy Role action to duplicate a base role into a custom named role (e.g., contoso_FieldSalesRepresentative ) inside a dedicated Unmanaged Solution .
Include Security Roles in ALM Pipelines: Export custom security roles within your Managed Solution package when deploying across Test, UAT, and Production environments.