Skip to content
Tutorials Center
My learning

Topics

Lesson 31 of 38 ยท Governance and Performance

Security Roles, Sharing and Row Access

Control who can see and change what in Power Apps: Dataverse security roles, privileges and access levels, business units, teams, column security and app sharing.

An app can be perfect and still leak data if its security is wrong. Power Apps separates who can run the app from what data they can see. The first is sharing; the second is Dataverse security. Understanding both is the core of governance for model-driven apps and for canvas apps that use Dataverse.

Two separate questions

  1. Can this person open the app? Decided by sharing: you share a canvas app with users or groups; for a model-driven app you share through security roles assigned to the app.
  2. Can they see this row or change this column? Decided by Dataverse security roles, business units, teams and column security profiles.

Sharing a canvas app that uses SQL Server or SharePoint does not give people rights to that data source; they need those rights too. Sharing is not data permission.

Security roles

A security role is a set of privileges on tables. For each table a role lists:

  • Create, Read, Write, Delete
  • Append (attach this row to another) and Append To (allow others to attach to this row)
  • Assign (change owner) and Share

Each privilege has an access level, shown as a circle that fills in:

Level Meaning
None No access
User Only rows the user owns
Business unit Rows owned by anyone in the user's business unit
Parent: Child business units The user's unit and the units below it
Organization All rows

A user's effective access is the union of all roles they hold (directly or through a team). Dataverse never lets one role take away another's privilege; to deny, remove the role.

You edit roles in the Power Platform admin center: choose the environment, Settings, Users + permissions, Security roles.

Access levels

User My own rows
Business unit My department
Organization Everything

Choose the smallest level that works.

1 / 2

Row ownership

Rows in user or team owned tables have an owner (a user or a team) and a business unit (taken from the owner). The access level compares the row's owner or business unit with the user's. Organization-owned tables (for example reference lists) have no owner, and access is simply on or off.

So the same role "Sales Rep" with Read: User on Opportunities shows each rep only their own rows, while a "Sales Manager" role with Read: Business unit shows the whole team's.

Evaluating access: a stand-in

The access decision is a small algorithm. This stand-in implements the user/business-unit/organization levels for a read request. The real platform adds teams, hierarchy and sharing, so treat it as a teaching model.

JS Stand-in: can this user read this row?

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Teams and business units

  • A business unit is a department-like node in a tree. Users belong to exactly one. Plan the tree early: moving users between units later changes what they see.
  • A team is a group of users. An owner team can own rows and can hold security roles; an access team gives access to individual rows; a Microsoft Entra ID group team syncs membership from your directory, so HR changes flow automatically.

Assign roles to teams instead of individuals where possible, so offboarding is one membership change.

Column security

Some columns (salary, national ID) need stricter rules than the table. Enable Column security on the column, then create a column security profile with Read, Update and Create permissions for chosen users or teams. Users without the profile see the field masked as ********.

Sharing canvas apps

In the maker portal select the app, then Share. Add users or Microsoft Entra security groups and choose Co-owner only for people who may edit. Add Data permission when the app uses Dataverse: the share dialog asks you to give a security role on the tables. For connectors like SQL with user sign-in, tell the user to be granted access to the database.

Row-level sharing and hierarchy

A user can share a single row with another user and choose which privileges (Read, Write, Delete, Append, Assign, Share) to give. This is useful but hard to audit; prefer roles and teams for the regular rules. A hierarchy security model lets managers read their reports' rows without a wider access level.

Testing security

Always test with an account that has only the target role. In model-driven apps use Run as (impersonation, via the Environments, Users, Run as type options for admins in some tenants) or a test user. Compare what they see with the table of rules you designed.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Does sharing a canvas app give users access to its data?

    Sharing controls who can open the app; data access is governed by the data source.
  2. 2. A user holds two roles: Read at User level and Read at Organization level. What can they read?

    Roles combine as a union, so the broadest level applies.
  3. 3. What protects one sensitive column on top of table security?

    Column security profiles grant read, update and create on secured columns.
  4. 4. Which is the best way to manage role assignment for many users?

    Team-based assignment follows group membership and simplifies offboarding.

Summary

  • Sharing decides who can open the app; Dataverse roles, business units and teams decide which data they see.
  • Roles list privileges per table with access levels from User to Organization; multiple roles combine.
  • Use column security for sensitive fields, teams for assignment and least privilege everywhere.
  • Test with accounts that have only the intended role.

Next: Data Loss Prevention Policies