Reports · Reporting setup and access

How to configure Reporting for a profile

Configure report visibility and semantic-model row security for a profile.

On this page

Before you start

  • Reporting must be enabled and the profile bound to the intended workspace. You need Edit reporting setup and/or Edit reporting security roles for the part you manage; instance admins can configure their instance’s profiles. Coordinate model role names with the Power BI owner.

Follow these steps

Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.

  1. Select the profile in Context and open Settings → Reporting. Check the profile/workspace before assigning access.
  2. On Reports, find each report you intend to expose. Edit its description/status where needed and use Assign access to select the allowed profile Roles and/or Users. Apply the access selection.
  3. On Semantic models, choose Configure RLS for the model used by the report. Confirm the Fabric semantic model ID and configuration health.
    Assign access dialog for Operations Overview with Roles and Users selectors.View full size ↗
    Grant the report to the intended roles or users. Report access and data security must both be configured.
  4. Choose No RLS, Profile roles or RLS roles. Profile roles sends the viewer’s profile-role names to Power BI. RLS roles uses the explicit RLS roles and membership configured here.
    Semantic model RLS dialog showing No RLS, Profile roles and RLS roles.View full size ↗
    Select the policy that matches the semantic model. When using Profile roles, the role names must match the model’s RLS roles.
  5. If using RLS roles, open that tab, select Add role, use the exact role name defined in Power BI and select its users. Save the role and the model configuration.
    Reporting folders list with New Report Folder and ordering controls.View full size ↗
    Use folders to organise the profile’s reports. Folder placement does not grant report access.
  6. Test with an intended viewer: confirm the report appears and that the permitted rows are correct. Use Folders to organise reports separately from their access grants.

What you should see

The right members can discover the report, and the model uses the selected identity/RLS policy. RLS membership alone does not grant report visibility.

If something goes wrong

Controls are read-only

Check the specific reporting setup/security permissions. A delegated manager may be authorised for one area but not the other.

The model is unresolved or unhealthy

Ask the report/model owner to repair the workspace/model binding before testing embedding.

The viewer sees too many or too few rows

Review the model’s policy, exact Power BI role names and memberships. Instance Admin access is not a guarantee of unrestricted report rows.

Need a hand?

Contact your organisation’s Emplyr administrator using your usual internal support channel.

How to ask for help