Reports · Reporting setup and access
Why Reporting is not available for a profile
Check the conditions that make Reports or one report available.
On this page
Before you start
- Check the active instance/profile and note whether Reports is missing entirely, the list is empty, or one report fails.
Follow these steps
Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.
- If Reports is missing, ask an instance admin to confirm Reporting is enabled under Admin / Global → Profiles → Assign modules.
- Ask the profile role manager to confirm View reports access. A sidebar layout can also hide/group the Reports link; it does not grant or revoke the underlying report permission.

Enable the modules the profile needs. Members still require the appropriate role and resource access. - If Reports opens but the list is empty, ask the reporting manager to open Settings → Reporting and check active reports and user/profile-role access.
- Ask an instance admin to check the profile’s Fabric workspace binding and the service principal’s ability to read its reports.
- If the whole profile is paused, review its subscription entitlement and eligible workspace placement. This applies to commercially enrolled instances.

If the entire profile is paused, an instance administrator must check its subscription and workspace placement before feature-specific troubleshooting. - If only embedding or data fails, use Troubleshooting reporting access to check semantic-model configuration, RLS and report errors.
What you should see
The administrator can fix the relevant module, permission, report grant or setup condition without granting unrelated access.
If something goes wrong
You already have Fabric workspace access
Fabric membership does not automatically create report grants inside Emplyr.
You are in an RLS role but the report is absent
RLS roles filter model rows. They do not grant report visibility by themselves.