Once a report leaves Desktop, a different set of concerns takes over: who can see it, which rows they see, how it stays current, and which licence tier makes all of that possible. This covers workspace roles and apps, gateways and scheduled refresh, row-level security, sharing, and the free, Pro and Premium tiers.
In this guide
Workspace roles and apps
A workspace role, Admin, Member, Contributor or Viewer, forms a permission ladder controlling what each person added to a workspace is allowed to do there, from full management down to read-only. A Viewer can only open and read existing content; a Contributor sits further up the ladder, able to publish, edit and replace content in that workspace.
A Power BI app is a different object from the workspace itself: a polished, packaged bundle of reports and dashboards from a workspace, published out for a wider audience to consume. Organisations publish an app rather than adding every end user directly into the workspace specifically to separate the authors, who need to edit content, from the end users, who only need a clean viewing experience without being exposed to the authoring environment and its editing permissions.
Gateways and scheduled refresh
An on-premises data gateway lets the cloud-based Service securely reach a data source sitting inside a private company network, such as an on-premises SQL Server. Without one, an Import-mode dataset connecting to such a source has no secure path to reach it at refresh time, so a scheduled refresh configured for that dataset simply fails.
| Gateway type | Scope |
|---|---|
| Personal gateway | Serves only that one user's own scheduled refreshes, tied to their own machine |
| Standard (on-premises) gateway | Installed centrally, shared and managed across many users and data sources in an organisation |
Scheduling a refresh configures fixed times at which the Service should automatically re-run a dataset’s source queries and reload fresh data, the same underlying action as a manual refresh, just set to repeat on its own.
Row-level security: static versus dynamic
Row-level security (RLS) restricts which rows of data a particular user or group is allowed to see, using roles with filter rules defined inside the model. The role definitions and their DAX filter rules are authored in Desktop as part of the model; specific users or groups are then assigned to those existing roles afterward, inside the Service.
| RLS type | How the filter rule works | Scales to many groups by |
|---|---|---|
| Static | A fixed value is hard-coded into the role, such as Region = "North" | Building a separate static role per group, one by one |
| Dynamic | The rule compares a column against the currently signed-in user's own identity | One single role that adapts automatically to whoever is signed in |
Fifty regions, one role
A dataset needing a different RLS role for each of 50 sales regions is the textbook case for dynamic RLS: one role whose rule filters by comparing a region column to the viewer’s own signed-in identity scales to any number of regions at once, rather than needing 50 separate static roles built and maintained by hand.
Workspace roles and row-level security control two different things, and both apply at once, not instead of each other. A Viewer who also has an RLS role assigned sees the same report everyone else sees, but filtered down to only the rows their specific role permits.
Sharing a report versus publishing an app
| Option | What it grants |
|---|---|
| Share | Direct, lightweight access to one specific report or dashboard for one named person |
| App | A curated bundle of several related reports and dashboards, published to a wider, defined audience at once |
Share is the simplest way to hand one colleague access to one specific item, aimed at one named person. An app, by contrast, bundles several reports and dashboards together and packages them for a wider audience, which is the better fit once more than a single item or a single viewer is involved.
Free, Pro and Premium
| Tier | What it adds |
|---|---|
| Free | Build and view personal reports; does not usually include sharing or collaborating through a workspace |
| Pro | Adds collaboration: sharing workspaces, publishing apps, and consuming content shared by others |
| Premium | Licenses dedicated capacity for the whole organisation, generally allowing wider, often licence-free viewing alongside extra scale and features |
The gap between Free and Pro is mainly about collaboration, not about using Desktop itself: Desktop’s authoring capability, including writing DAX measures, is free regardless of tier. Premium shifts the model entirely, licensing capacity for an organisation rather than person by person, which is why a large organisation with thousands of report viewers often leans toward Premium capacity rather than buying an individual Pro licence for every single viewer.
Governance habits worth keeping
- Keep production content in its own workspace, separate from personal or experimental work, so shared, trusted content stays clearly distinct from work still in progress.
- Review workspace and app access periodically, not only at setup. People’s roles and teams change over time, so access that was once appropriate can quietly become outdated or excessive if nobody checks it again.
Common mistakes
- Adding every viewer directly into the authoring workspace. That exposes editing permissions to people who only ever need to view finished content; an app keeps the two groups separate.
- Building 50 static RLS roles instead of one dynamic role. A dynamic rule tied to the signed-in user’s identity scales to any number of groups without the maintenance burden.
- Forgetting a gateway for an on-premises source. A scheduled refresh against a private-network source fails without one, even if the dataset itself is configured correctly.
- Assuming RLS and workspace roles are redundant. They control different things, access to content versus which rows within it, and both apply together.
- Letting workspace access go stale. Without periodic review, old access tends to outlive the role that originally justified it.
Cheat sheet
| Question | Answer |
|---|---|
| Which workspace role is read-only? | Viewer |
| What packages workspace content for a wider audience? | A Power BI app |
| What lets the Service reach an on-premises source? | A gateway |
| What gateway type is shared across an organisation? | The standard (not personal) gateway |
| Where are RLS roles authored? | In Desktop, as part of the model |
| Where are users assigned to RLS roles? | In the Service |
| What RLS type scales to many groups with one role? | Dynamic RLS |
| What is the lightest way to give one person access to one report? | Share |
| What licence tier adds workspace collaboration? | Pro |
| What licence model licenses capacity, not people? | Premium |
Try it yourself
Quick check
A sales manager should see every region’s numbers, but each regional rep should see only their own region’s rows, in the very same report. What combination of features achieves this with the least ongoing maintenance?
Show answer
Dynamic row-level security with two roles: one unrestricted role (or no RLS applied) for the manager, and one dynamic rep-level role whose filter rule compares the Region column to the signed-in user’s own identity. The dynamic rule means a single role setup serves every rep without a separate static role per region, and workspace/app sharing controls who can open the report at all, which is a separate, complementary layer from RLS.
Frequently asked questions
What is the difference between a Power BI workspace and a Power BI app?
A workspace is where authors build and edit content. An app is a polished, packaged bundle of selected reports and dashboards from a workspace, published for end users who only need to view, not edit.
What is row-level security in Power BI?
Row-level security restricts which rows of data a user or group can see, using roles with filter rules defined in the model. It is authored in Desktop and users are assigned to roles in the Service.
What is the difference between static and dynamic row-level security?
Static RLS hard-codes a fixed filter value into a role, needing a separate role per group. Dynamic RLS compares a column to the signed-in user’s own identity, so one role adapts automatically to every viewer.
What does a Power BI gateway do?
A gateway lets the cloud-based Power BI Service securely reach a data source sitting on a private, on-premises network, which a scheduled refresh against such a source needs in order to work at all.
What is the difference between Power BI Pro and Power BI Premium?
Pro is a per-user licence that adds collaboration: sharing workspaces and publishing or consuming apps. Premium licenses dedicated capacity for the whole organisation, generally allowing much wider, often licence-free viewing alongside extra scale.
Do workspace roles and row-level security do the same job?
No. Workspace roles control what a person can do, such as view or edit. Row-level security separately controls which rows of data they see within content they are already allowed to open, and the two apply together, not as substitutes for each other.
Test yourself
Timed questions on Power BI Service, Security and Sharing, with an explanation for every answer.