Lesson 9 of 11 · 10 min · Reports and dashboards

Publishing, sharing and row-level security

Covers: Power BI service and Desktop. Updated 13 Nov 2026. Part of the Data Analyst roadmap.

What you will learn

  • Publish a report from Power BI Desktop to the service
  • Set up scheduled refresh and understand gateways
  • Choose how to share: workspace, app, link or embed
  • Understand the licence rules in outline
  • Restrict who sees which rows with row-level security

In simple words

A report that lives only on your laptop helps nobody. Publishing sends it to Microsoft's online service, where it can be opened in a browser or phone, kept up to date automatically, and shared with the right people. Sharing also means deciding who may see which data: a regional manager should see their own region, not everybody's salaries.

Words to know

  • Workspace: a shared area in the service where reports, models and dashboards are kept.
  • App: a packaged set of reports and dashboards published to a wider audience.
  • Gateway: software that lets the service refresh data from sources inside a private network.
  • Row-level security (RLS): rules that show each person only the rows they are allowed to see.

Publish

In Desktop, choose Home > Publish, sign in with your work or school account, and pick a workspace. Power BI uploads two things: the report (pages and visuals) and the semantic model (data, relationships and measures). They appear in the workspace in the service (app.powerbi.com). From there you can open the report in the browser, set refresh, share and pin visuals to a dashboard.

  • Report versus dashboard: a report has pages and filters and is built in Desktop (or the browser editor). A dashboard is a single page of tiles pinned from one or more reports, with no slicers; it is good as a one-screen overview with links to the reports.
  • Use separate workspaces for development, testing and production in teams (deployment pipelines help move content). Keep the .pbix in version control or SharePoint.
  • Edits to a published report mean publishing again, which overwrites the earlier version with the same name.

Refresh in the service

Imported data is a snapshot. In the workspace, open the semantic model's Settings:

  1. Data source credentials: sign in to each source.
  2. Gateway: for on-premises or private-network sources, install and configure a gateway (standard or personal) and map the data source. Cloud sources such as SharePoint, OneDrive and many online services need no gateway.
  3. Scheduled refresh: choose the time zone, frequency and times, and optionally an email on failure.

There are limits on how many refreshes a day each licence allows (a Pro workspace has a lower daily limit than Premium or Fabric capacity; check Microsoft's current limits), and a refresh must finish within a time limit. Refresh history lists successes and failures with the error text. The usual causes of failure are expired credentials, an offline gateway, changed source columns, or timeouts. For huge tables, incremental refresh loads only recent partitions.

Ways to share

Method Who it suits Notes
Workspace access (Viewer, Contributor, Member, Admin) your team who build and maintain content viewers see content; contributors can edit; manage roles carefully
Power BI app a wide internal audience package of reports and dashboards, with an audience list and a clean navigation; the recommended way to deliver content
Share link (direct access) a few specific people recipients need access to the content and the underlying data per licence and RLS
Email subscriptions people who want a regular snapshot a scheduled email with a report image or a link
Embed in Teams, SharePoint or a website where users already work secure embed requires licences; "embed for your customers" uses a different model
Export to PowerPoint, PDF or Excel one-off sharing a snapshot, not live; check what data leaves the tool

Publish to web: a warning

Publish to web creates a public link or embed code that anyone on the internet can open without signing in, and search engines may index it. Use it only for data that is truly public. Never use it for company or personal data. Administrators can disable it in the tenant settings.

Licences, in outline

Licensing changes, so confirm on Microsoft's pages. In broad terms:

  • Power BI Desktop is free.
  • A free account lets you use the service for personal content ("My workspace"), but not share it as a collaborating team.
  • Power BI Pro (per user) lets you publish to shared workspaces and share content with other licensed users.
  • Premium per user (PPU) adds larger models and more refreshes per user.
  • Fabric or Premium capacity (an organisation-level purchase) lets people with free licences view content in capacity workspaces, with much larger limits, depending on the capacity size.

For a student portfolio, common options are a free or trial licence, screenshots and a short video of the report, publishing the .pbix file to GitHub with sample data, or using only public data. Do not post reports containing a real company's data.

Row-level security (RLS)

RLS restricts the rows a person sees using roles with DAX filters, defined in Desktop.

  1. Modeling > Manage roles > Create.
  2. Choose a table and write a filter expression:
// Static role "Hyderabad Managers"
[City] = "Hyderabad"

// Dynamic role using the signed-in user's email
[ManagerEmail] = USERPRINCIPALNAME ()
  1. Use View as to test the role in Desktop.
  2. Publish, then in the service open the semantic model's Security page and add members (people or groups) to each role.

How it works: the filter on the dimension table flows through relationships to the fact table, so a Hyderabad manager's visuals, totals and slicers contain only Hyderabad rows. Dynamic RLS with a mapping table (UserRegion with email and region) scales to many users with one role.

Key points:

  • RLS filters rows only for people with Viewer access (workspace members with edit rights see all data), so give report consumers viewer access or use an app.
  • It works with Import and DirectQuery; apply filters on dimension tables where possible.
  • RLS does not hide column names or protect an exported .pbix file; object-level security hides tables or columns.
  • Test with real users' accounts, including a user who belongs to no role, who sees nothing.

Governance basics

  • Name and describe workspaces and reports; certify or promote trusted models ("endorsement").
  • Document refresh owners and data sources.
  • Use sensitivity labels where your organisation has them.
  • Remove access when people change teams.
  • Think about personal data: show only what is needed, aggregate where possible, and follow your organisation's policy and applicable data protection law.

Common mistakes

  • Using Publish to web for internal data.
  • Sharing the .pbix file instead of publishing, which exposes the underlying data.
  • Scheduled refresh failing silently because credentials expired.
  • Giving viewers edit rights, which bypasses RLS.
  • Assuming a free licence can share content with colleagues.

Try it yourself

  1. Publish a report to your workspace, open it in the browser and pin a visual to a dashboard.
  2. Set the semantic model's credentials and a daily scheduled refresh (use a cloud source or a trial), then read the refresh history.
  3. Create a static RLS role for one city, test it with View as, and then write a dynamic version using USERPRINCIPALNAME.
  4. Write down which sharing method you would use for: your team, a department of 200, and the public.

Check yourself

What does Publish send to the Power BI service?

The report (pages and visuals) and its semantic model (data, relationships, measures).

When do you need a gateway?

When the service must refresh from, or query, data sources that are not directly reachable from the internet, such as on-premises databases.

Why is Publish to web dangerous?

It creates a public link anyone can open without signing in, so it exposes the data to the internet.

What does row-level security do?

It filters the rows a user can see based on roles defined with DAX filters, so people see only their permitted data.

Interview questions

How do you share a report with 200 people securely?

Publish it in a workspace, package an app with an audience, give users the right licences or capacity access, apply row-level security if people should see different data, and review who has access.

Explain static versus dynamic RLS.

Static RLS hard-codes a filter per role (City = "Hyderabad") and needs a role per group. Dynamic RLS filters using the signed-in user (USERPRINCIPALNAME) against a mapping table, so one role covers everybody.

A scheduled refresh stopped working. What do you check?

The refresh history error, whether credentials expired, whether the gateway is online and the data source is mapped, whether source columns changed, and whether the refresh exceeded time or size limits.

Summary

  • Publish from Desktop to a workspace; reports and dashboards are consumed in the service and on mobile.
  • Keep data fresh with credentials, gateways and scheduled refresh, and read the refresh history.
  • Prefer apps for wide audiences; never use Publish to web for non-public data; understand licences in outline.
  • Use row-level security to control which rows each person sees, and test it.

Going deeper

See how much of this you can explain

A free mock interview asks you new questions on Power BI and dashboards for Data Analyst and scores every answer, with what to fix.