How to create a Power BI landing page for multiple reports
A sales manager needs the pipeline report. Finance needs the monthly revenue view. Operations needs the backlog report. Give employees one shared starting point even when those reports live across separate workspaces, data models, and owners.
Good for packaging related reports inside one workspace for specific audiences.
A custom PBIX page with Web URL buttons pointing to separate reports.
A curated, searchable menu that stays beside native Power BI across all workspaces.
1. Start with the report map
Before choosing a tool, list each report's business name, intended audience, owner, and approved viewing link. Keep technical workspace names in your admin inventory so employees never have to guess where a report lives.
Revenue
→ Monthly performance vs. plan
Costs
→ Department budget vs. actual
Pipeline
→ Open opportunities & stage velocity
Customers
→ Account retention & expansion
Delivery
→ Order backlog & fulfillment
Service
→ Ticket SLA & response times
2. Choose the approach that fits your collection
If a single native app already covers your audience, start there. A portal becomes valuable when your reports span multiple workspaces and maintaining custom link pages becomes a recurring burden.
Native Power BI App
Best when: You want a Microsoft-managed package for related content housed inside a single workspace.
Report with Navigation Links
Best when: You have 5–10 stable destinations and want to design a custom visual starting canvas in Power BI Desktop.
LumioBI Portal Sidebar
Best when: You want one curated, searchable menu across many workspaces that stays beside native reports as users work.
3. Use a native Power BI app or Org App
Microsoft offers classic Workspace Apps and newer Fabric Org Apps (see our Workspace vs. App vs. Org Apps guide and Microsoft's Org Apps documentation). Included content comes from the app's workspace:
- 1. Create the app: In a supported workspace, choose New → Org app (or publish the workspace app) and name it.
- 2. Select content: Use Add content to pick the reports you want to bundle.
- 3. Add an Overview & Sections: Arrange the opening overview page as your starting experience.
- 4. Configure audiences: Set audience visibility, save, and share the app link.
4. Build a landing report with button links
A dedicated Power BI report can act as a visual directory where each button opens a different report URL (see Microsoft's button configuration guide):
- 1. Collect viewer URLs: Copy the exact viewing or app-context URL for each destination report.
- 2. Design the starting canvas: In Power BI Desktop, add headings for Finance, Sales, and Operations.
- 3. Insert buttons: Choose Insert → Buttons and give each a clear business title.
- 4. Set Action to Web URL: Enable Action → Web URL (not Page navigation, which only moves inside the same PBIX).
- 5. Publish & verify: Test every button with a standard viewer account.
5. Keep the menu alongside every report with LumioBI
With LumioBI, administrators curate the folder hierarchy once, and employees use the Power BI Chrome extension to keep that portal menu right beside native Power BI. Users can jump between Finance, Sales, and Operations reports without ever returning to a separate directory page.
1. Build the folder tree
Add Finance, Sales, and Operations folders and report links in the Navigation editor.
2. Target by group
Set group visibility and attach metric dictionaries or support links beside reports.
3. Publish in seconds
Review your draft and publish updates immediately without republishing Power BI apps.
4. Search & favorite
Viewers use unified search and Favorites while staying inside native Power BI.
Navigation and report access are separate
LumioBI organizes menu visibility; Microsoft Entra and Power BI continue enforcing actual report permissions and licensing.
6. Test the journey before you share it
Give someone outside the BI team three tasks: find a familiar report, find one from another department, and switch to a third report. Watch where they hesitate.
Business-first naming
Every report title describes a business question or decision, not a database table.
Viewer link verification
Each link opens cleanly for an ordinary viewer account, not only a workspace admin.
Permission enforcement
Users without permission remain blocked from restricted reports, even with a direct URL.
Effortless switching
Viewers know immediately how to return to the directory or switch to another report.
Accountable ownership
A named owner reviews broken links, retired reports, and audience changes.
Browser compatibility
The navigation experience works cleanly in the browsers your audience uses daily.
7. Common questions
Can a landing page point to reports in different workspaces?
Yes. A directory of viewing links or a LumioBI portal can point to destinations across any number of workspaces. Each link still requires the viewer's existing Power BI access.
Does this combine several reports into one dashboard?
No. This organizes entry points to separate reports so each report keeps its own data model, owner, and refresh schedule.
Should I build a link page or use a portal?
A small, static list works well as an app or button-link page. Choose LumioBI when you want persistent navigation alongside reports, cross-workspace search, and audience-targeted menus.
Put your report map to work
Give your team a clearer place to start.
Explore LumioBI's persistent sidebar navigation and unified search, review plans, or create a portal around the reports your organization already uses.
Written by LumioBI, the product described in this guide. Microsoft interfaces and requirements can change; refer to the linked documentation when configuring your environment. For a broader comparison, see Org Apps, embedded analytics, and LumioBI.