Study guide

3.4 Column-Level Security & Hierarchy Security Models

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.4 Column-Level Security & Hierarchy Security Models

Key Takeaways Explain This Topic AI

Column-Level Security (Field-Level Security) restricts Read, Create, and Update permissions on specific sensitive attributes, overriding table-level record access.

System Administrators automatically hold full Read, Create, and Update permissions on all secured columns through the default System Administrator Column Security Profile.

Column Security Profiles define the exact permission triad (Read: Yes/No, Create: Yes/No, Update: Yes/No) and can be assigned to individual Users or Microsoft Entra / Owner Teams.

Hierarchy Security extends record visibility up the management chain using either the Manager Hierarchy model (direct reporting chain) or Position Hierarchy model (organizational position tree).

Under Hierarchy Security, managers receive Read, Update, Append, and Append To access to direct reports' records at Depth 1, but only Read-Only access to indirect reports at Depth 2 and deeper (up to the configured maximum depth limit).

Last updated: August 2026

3.4 Column-Level Security & Hierarchy Security Models

While Business Units and Security Roles establish coarse-grained authorization at the table and record tiers, enterprise applications frequently require more granular controls. Organizations must protect highly sensitive individual fields (such as Social Security Numbers, executive compensation, or credit card details) and provide automated management oversight across reporting structures.

Microsoft Dataverse addresses these enterprise requirements through Column-Level Security (Field-Level Security) and Hierarchy Security Models .

1. Column-Level Security (Secured Fields)

Column-Level Security allows system customizers to restrict access to specific columns within a table without altering record-level security roles. Even if a user has full Organization-wide Write access to a Contact record, Column-Level Security can prevent that user from viewing or editing the Contact's Tax Identification Number or Credit Score . +-----------------------------------------------------------------------------------+

  • | COLUMN-LEVEL SECURITY ARCHITECTURE |
  • | |
  • | +---------------------------------------------------------------------------+ |
  • | | CONTACT TABLE (User has Global Read/Write Security Role) | |
  • | | | |
  • | | - First Name: 'Alice' [Standard Column -> Visible & Editable]|
  • | | - Last Name: 'Smith' [Standard Column -> Visible & Editable]|
  • | | - Email: 'alice@contoso.com' [Standard Column -> Visible & Editable]|
  • | | | |
  • | | - SSN: '***-**-****' [SECURED COLUMN] | |
  • | | * User lacking Read Profile sees masked asterisks! | |
  • | | * User lacking Update Profile sees locked field on form! | |
  • | | * API queries return null/masked values! | |
  • | +---------------------------------------------------------------------------+ |
  • +-----------------------------------------------------------------------------------+
  • Enabling Column Security

Column Definition Property: In the Power Apps Maker Portal or Solution Explorer, open the target column properties and enable the "Enable Column Security" checkbox ( IsSecured = true ).

Supported & Unsupported Columns:

Supported: Most standard and custom columns (Single line of text, Multiple lines of text, Whole Number, Decimal, Currency, Date/Time, Lookup, Choice).

Unsupported: Primary Key columns ( entityid ), State/Status columns ( statecode , statuscode ), and system tracking timestamps ( createdon , modifiedon ).

2. Column Security Profiles & The Permission Triad

Once a column is secured, Dataverse blocks all non-administrative access by default until the column is explicitly configured within a Column Security Profile . +-----------------------------------------------------------------------------------+

  • | COLUMN SECURITY PROFILE PERMISSION TRIAD |
  • | |
  • | +-------------------+ +-------------------+ +-------------------+ |
  • | | READ PERMISSION | | CREATE PERMISSION | | UPDATE PERMISSION | |
  • | | (Yes / No) | | (Yes / No) | | (Yes / No) | |
  • | | Controls viewing | | Controls initial | | Controls modifying|
  • | | data in forms, | | population when | | value on existing |
  • | | views, and API. | | creating record. | | saved record. |
  • | +-------------------+ +-------------------+ +-------------------+ |
  • +-----------------------------------------------------------------------------------+
  • Profile Configuration Mechanics

Default System Administrator Profile: Every Dataverse environment includes a built-in System Administrator Profile that automatically grants full Read, Create, and Update permissions on every secured column. This ensures administrators are never locked out of system data.

Custom Profiles: Administrators create custom Column Security Profiles (e.g., "HR Compensation Profile" or "Finance Payroll Profile" ).

Granular Permission Combinations:

Read Only (Read: Yes, Create: No, Update: No): Users can inspect the sensitive value but cannot enter or edit it.

Create Only / Blind Entry (Read: No, Create: Yes, Update: No): Useful for call center agents who collect credit card numbers during onboarding but must never view or edit them afterward.

Read/Update (Read: Yes, Create: Yes, Update: Update): Full operational maintenance.

Assignment to Users and Teams: Column Security Profiles can be assigned to individual users, traditional Owner Teams, or Microsoft Entra ID Group Teams.

Runtime & API Behavior

UI Rendering: In model-driven forms, secured columns display a small key icon. If a user lacks Read permission, the field displays masked characters (e.g., ******** ). If the user lacks Update permission, the field appears read-only.

API / Power Automate / Search: If an unauthorized user or automated cloud flow queries a secured column via the Web API, Dataverse returns null for that attribute without failing the overall query.

3. Hierarchy Security Models: Manager vs. Position Hierarchy

In many organizations, managers require oversight of records owned by or shared with their subordinates without requiring broad Business Unit security roles or cumbersome sharing rules. Hierarchy Security extends record authorization based on organizational reporting structures. +-----------------------------------------------------------------------------------+

  • | HIERARCHY SECURITY: MANAGER VS POSITION |
  • | |
  • | MANAGER HIERARCHY MODEL POSITION HIERARCHY MODEL |
  • | (Based on SystemUser 'Manager' Field) (Based on Position Hierarchy Table|
  • | |
  • | [VP of Sales] [Sales Director Position] |
  • | | | |
  • | v (Depth 1: Read/Write/Append) v (Depth 1) |
  • | [Sales Manager] [Sales Manager Position] |
  • | | | |
  • | v (Depth 2: READ-ONLY!) v (Depth 2) |
  • | [Sales Rep A] [Sales Rep Position] |
  • +-----------------------------------------------------------------------------------+
  • Manager Hierarchy Model

Mechanism: Uses the standard manager lookup field on the SystemUser table ( systemuser.parentsystemuserid ).

Topology: Strictly follows the management reporting chain defined in Dataverse or synchronized from Microsoft Entra ID.

Limitation: A user can only have exactly one direct manager. Matrix reporting structures across different departments cannot be modeled via Manager Hierarchy.

Position Hierarchy Model

Mechanism: Administrators define job positions (e.g., "Senior Account Executive" , "Regional Sales Lead" ) using the Position table, link positions in a parent-child hierarchy, and assign users to positions.

Flexibility: Allows defining reporting structures that span across different Business Units without modifying the user's direct line manager in Active Directory.

4. Hierarchy Depth Rules & Privilege Evaluation

When Hierarchy Security is enabled in Power Platform Admin Center, administrators must configure the Hierarchy Depth parameter (integer value representing levels of hierarchy traversal). +-----------------------------------------------------------------------------------+

  • | HIERARCHY ACCESS RULES BY DEPTH LEVEL |
  • | |
  • | Manager (Root) |
  • | | |
  • | +---> DEPTH 1: Direct Report |
  • | | Access Granted: READ, WRITE, APPEND, APPEND TO |
  • | | (Manager can edit direct report's records!) |
  • | | |
  • | +---> DEPTH 2 to N: Indirect Report (Subordinate's Subordinate) |
  • | Access Granted: READ-ONLY |
  • | (Manager can view, but CANNOT edit indirect report's records!) |
  • +-----------------------------------------------------------------------------------+
  • Hierarchy Access Rules Table
  • Subordinate Level Traversal Depth Permissions Granted to Manager Prohibited Operations
  • Direct Report Depth = 1 Read, Write, Append, Append To Delete, Assign, Share

Indirect Report Depth ≥ 2 (up to max configured depth) Read-Only Write, Delete, Assign, Share, Append, Append To

Beyond Configured Depth Depth > Max Configured Depth None (No hierarchy access) All operations

Warning

Hierarchy Security does not grant Delete , Assign , or Share privileges at any depth level. To delete or assign a subordinate's record, the manager must hold sufficient table-level security role privileges or have the record explicitly shared with them.

Performance & Governance Best Practices

Table Inclusions: Configure Hierarchy Security for "Selected Tables" rather than "All Tables" to avoid unnecessary query overhead on high-volume background transaction tables.

Depth Limits: Keep Hierarchy Depth to 3 or 4 levels . Deep hierarchical trees (e.g., depth ≥ 6) require complex recursive SQL joins during view rendering, impacting user interface responsiveness.

Loading diagram... Hierarchy Security Depth & Permission Cascade