Franchises can give every location its own Power BI dashboard without licensing each franchisee, by running reporting on a shared Microsoft Fabric capacity instead of per-user Power BI Pro licenses. Row-Level Security (RLS) ensures each franchisee sees only their own location's data, sub-organizations give each one a separately branded portal, and head office keeps a full roll-up across the network — all from one account on one capacity. This turns franchise reporting from a per-seat cost that grows with every location into a flat, predictable one.
A franchise has a reporting problem that ordinary Power BI sharing doesn't solve cleanly. Head office wants one view across every location; each franchisee wants their own numbers and nothing else; and nobody wants to buy a Power BI Pro license for every location manager, or email out 80 PDFs a month. This guide shows how franchises deliver per-location dashboards at scale in 2026 — who sees what, how the licensing actually works, and how to keep it manageable as the network grows.
TL;DR — Power BI reporting for franchises
- The problem: per-location dashboards + head-office oversight, without a Pro license per franchisee.
- Why per-user licensing breaks: Power BI Pro is ~$14/user/month; across dozens or hundreds of locations that scales viciously and is a nightmare to administer.
- The fix: run reporting on a Fabric capacity (fixed fee, unlimited viewers) with Row-Level Security so each location sees only its own data.
- For scale: sub-organizations give each franchisee a separately branded portal from one central account; head office keeps the network roll-up.
- Result: flat, predictable cost that doesn't rise with each new location, and clean data isolation per franchisee.
The franchise reporting problem
Franchise reporting is really three needs at once, and most sharing methods only handle one:
- Each franchisee needs their own view. Location 12 should see location 12's sales, labour, and inventory — never location 13's.
- Head office needs the roll-up. The franchisor wants network-wide performance, league tables, and outliers across all locations in one place.
- It has to be affordable and low-admin at scale. Onboarding a new franchisee shouldn't mean buying and provisioning another licence, or duplicating a report.
Email and PDF exports fail need 1 and 2 (static, no self-service, no security). Buying a Power BI Pro licence per franchisee fails need 3 (cost and admin balloon). Publishing to web fails need 1 badly — it makes data public to anyone with the link. The model that satisfies all three is capacity-based delivery with security and branding on top.
How franchises can give each location its own dashboard
1. Put reporting on a Fabric capacity, not per-user licences
On a Microsoft Fabric capacity, viewers consume reports without an individual Power BI Pro licence — you pay one fixed capacity fee regardless of how many locations log in. An entry-level F2 starts around $263/month and serves unlimited viewers; you scale the SKU to load, not to headcount. This is the single change that turns franchise reporting from a per-seat cost into a flat one. (See share Power BI without per-user licences and the hidden cost of Power BI Pro.)
2. Isolate each location with Row-Level Security
Row-Level Security filters the data so each franchisee only ever sees their own location. One report, one dataset, but every login is scoped to that location's rows — the franchisor maintains a single report, not one copy per site. (See implementing RLS in Power BI and RLS for multi-tenant setups.)
3. Give each franchisee a branded portal with sub-organizations
For a real franchise network you want more than a filtered report — you want each location (or region) to have its own branded space, and you want to administer them all centrally. Sub-organizations do exactly that: hundreds of isolated, separately branded portals from one account on one capacity. Head office manages the network; each franchisee logs into what looks like their own portal. (See it on the DataTako for franchises & multi-location page.)
4. Keep the head-office roll-up
The same capacity serves a franchisor-level workspace with the network roll-up — league tables, regional comparisons, outliers — while franchisees stay scoped to their own data. One platform, two audiences, no data crossover.
How franchises can deliver reporting — compared
What it looks like in practice
A franchisor with 60 locations puts its sales and operations reports on a single Fabric capacity. Each franchisee logs into a branded portal and sees only their own location, scoped by RLS. Head office opens a network dashboard covering all 60. Adding franchisee 61 means adding them to the portal and the RLS role — no new licence, no duplicated report, no change to the monthly capacity bill until actual load requires a bigger SKU. That's the difference between reporting that scales with the network and reporting that fights it.
Frequently asked questions
How do franchises share Power BI dashboards with every location?
The scalable way is to run reports on a Microsoft Fabric capacity rather than per-user licences, apply Row-Level Security so each location sees only its own data, and use sub-organizations to give every franchisee a branded portal. Head office keeps a network roll-up on the same capacity. This delivers per-location dashboards without buying a Power BI Pro licence for each franchisee.
Do franchisees need a Power BI Pro licence to see their dashboard?
No, if you deliver reporting on a capacity-based model. With a Fabric capacity, viewers consume reports without an individual Pro or Premium licence — you pay one fixed capacity fee for unlimited viewers. A Pro licence per franchisee is only required if you build the reporting on the per-user sharing model, which is what makes franchise reporting expensive.
How do you stop one franchisee from seeing another's data?
Row-Level Security. It filters the dataset so each login is scoped to that location's rows only, from a single shared report. Combined with a portal that isolates each franchisee into their own space (sub-organizations), one franchisee can never see another's numbers.
Can head office still see all locations?
Yes. The same capacity serves a franchisor-level workspace with the network roll-up — league tables, regional comparisons, and outliers across every location — while individual franchisees remain scoped to their own data. One platform serves both audiences without data crossover.
What does Power BI reporting for a franchise cost?
The main cost is the Fabric capacity, a fixed fee starting around $263/month for an F2 serving unlimited viewers (scaled to load, not location count). A managed portal such as DataTako adds a subscription on top for the branding, portals, and user management. Crucially, the cost stays flat as you add locations, unlike per-user licensing that rises with every franchisee.
How do you add a new franchisee to the reporting?
Add them to the portal and to the Row-Level Security role for their location. There's no new licence to buy and no report to duplicate — the same shared report simply scopes to their data. This is why capacity-based, RLS-driven reporting scales cleanly across a growing franchise network.
Running reporting across many locations? See how sub-organizations work, run the cost calculator for your location count, or book a walkthrough. Related: DataTako for franchises & multi-location, multi-tenant analytics, and share Power BI with external users without extra Pro licences.
