Launch Deal · 50% off 1st month ·

4.5 — Workspace Roles, Item-Level Access and Semantic Model Permissions

PL-300 Domain 4 · Skill 4.5

What You Need to Know

Access in Power BI works at three levels: the workspace (roles), the item (sharing and direct access), and the data (RLS, lesson 4.6).

Workspace roles

Assign people, security groups, Microsoft 365 groups or distribution lists in Manage access.

Capability Admin Member Contributor Viewer
Update and delete the workspace, add or remove Admins ✓
Add Members, Contributors and Viewers ✓ ✓
Publish, update or unpublish the app ✓ ✓ Only if allowed
Share items and give others permissions ✓ ✓
Create, edit, delete and publish content ✓ ✓ ✓
Schedule refresh, manage gateways connections for its models ✓ ✓ ✓
View and interact with content ✓ ✓ ✓ ✓
Subject to RLS ✓

The roles to remember: Contributor edits content but can't share or add people. Viewer only reads, and is the only role RLS restricts. Members can't add Admins.

Use least privilege: give report readers the Viewer role or, better, access through an app. Give security groups roles rather than many individual users.

Item-level access (sharing)

Share (or Manage permissions) on a report, dashboard or semantic model grants access to that item only, without a workspace role.

When sharing a report you choose:

  • Allow recipients to share (Reshare)
  • Allow recipients to build content with the data associated with this report (Build on the semantic model)
  • Send an email notification

Manage permissions shows Direct access (who has which permissions) and lets you remove them.

Semantic model permissions

Permission Allows
Read View reports that use the model (needed to see any report built on it)
Build Create new reports from the model in Desktop or the service, use Analyze in Excel, export underlying data, run DAX queries, use it in a composite model
Reshare Share the model with others
Write Edit the model (granted through workspace roles Contributor and higher)
  • To let analysts in other workspaces create their own reports from a certified model, grant them Build, directly or through an app audience. They don't need a role in the model's workspace.
  • RLS still applies to users with Build permission, unless they also have write access (a Contributor role or higher).
  • Object-level security (OLS) hides tables or columns from users in a role, so they can't query them at all.

Key Concept: Workspace roles control what people can do with everything in a workspace; sharing grants access to a single item; Build permission on a semantic model is what lets someone create their own reports from it. Readers should be Viewers or app users so RLS applies.

Exam Traps

  • Giving report readers the Contributor role (they can change content and bypass RLS)
  • Expecting a Contributor to share a report or add a colleague
  • Granting a workspace role when only Build on one semantic model is needed
  • Expecting RLS to filter data for a workspace Member while testing
  • Expecting hidden columns to be protected (use OLS)

Check your understanding

Practice Scenario

🔒 This practice scenario is part of Skillmarked Pro

The lessons stay free. Pro unlocks the other 22 PL-300 practice scenarios and the 50-question timed mock exam, plus everything for every other exam.

See plans

Launch Deal: first month €9.95, then €19.90/month. Enter code LAUNCH50 at checkout. Ends 1 December.

Cancel anytime. Or €199 a year, which saves 17%.

Not sure yet? Try 10 free mock exam questions.

Already Pro? Log in.