Home / Blog / Websites & UX

Client dashboard or client portal? How to give each client their own numbers

By Philip van den Berge, PL-30012 November 20267 min read
red padlock on black computer keyboard
Photo by FlyD on Unsplash

A client dashboard can reach your clients in two ways: you share a report link with each client, or you give them a login to a client portal where they see only their own numbers. Shared dashboards work for a few clients and data that isn't sensitive. Once you have more clients than you can manage by hand, need to be certain who sees what, or want the reporting under your own brand, a portal is safer and easier to run.

What clients want from a client dashboard

Ask an agency or a consultancy why they want client dashboards and the answer is usually about their own time: someone spends the first morning of every month pulling numbers from four tools and pasting them into slides. Ask their clients and you hear something slightly different. They want the current figures without having to email for them, they want to be sure they are looking at their own account and no one else's, and they want a sentence or two on what changed, because a chart without context leaves them to guess.

Those three needs (current data, only their data, and context) are the test for every option below. A setup that saves your team time but leaves clients unsure whether a figure is theirs hasn't solved the problem. It has moved it to the client.

Option 1: shared dashboards and report links

The quickest route is the tool you already use. You build a report in Looker Studio or Power BI, make one copy per client or filter it per client, and send each client a link or a monthly PDF export. For a small number of clients this is reasonable, and it costs little beyond the licences you already pay for.

The weaknesses grow with the client list. Copies multiply, so a change to one metric means editing every client's version. A filter on a report page is a display setting and does nothing for security; if the client can open the report, they can often clear it. Links get forwarded. And some sharing features are public by design. Microsoft's own documentation on Power BI Publish to web warns that anyone on the internet can view a report published that way, without signing in, including detail-level data in the model that the report itself doesn't display. It is meant for public data, never for client figures.

Licences are the other surprise. In Power BI, sharing a report with people outside your organisation generally means they need a licence too, unless the content sits on a capacity. My guide to Power BI pricing covers the licence options and what each one costs.

Option 2: a custom client portal

A custom client portal is a small web application with one login per user. Each client signs in and lands on their own dashboard, filtered to their company, next to their monthly reports and shared files. Your team gets an admin view where they can add clients and users, switch between client views and see every account in one place.

The portal can carry your logo, colours and domain, so clients see your service and not a third-party tool. It can also hold a short written note per client each month on what changed and why. I would always have that note drafted from the data and approved by someone on your team before a client reads it, because a confident sentence about the wrong number does more damage than no sentence at all. The example automated monthly report shows how numbers, checks and commentary fit together in one pack.

What a portal costs you is a build project and something to look after afterwards. What it gives you is one codebase for every client: a new metric is added once and appears for everyone, and adding a client is a row in a table instead of a new copy of a report.

How each client sees only their own numbers

The worst thing a client dashboard can do is show one client another client's figures. Everything else is a nuisance by comparison, so this is the part I would examine first in any option.

There are two places to enforce who sees what. The weaker one is the screen: the page asks the database for everything and then hides the rows that don't belong to the user. A single mistake in one screen, or a curious user with the browser's developer tools open, is enough to break that. The stronger one is the database itself. With Postgres row-level security, as described in the Supabase documentation, each table carries policies that filter every query, so a request only returns the rows its user is allowed to see, whichever screen made the request. Supabase recommends enabling it on every table in an exposed schema. Power BI has its own row-level security for reports, which does the same job inside a Power BI model.

Whichever tool you use, test it the way a client would break it:

  1. Create two test clients with obviously different data.
  2. Log in as each and confirm every page, export and download shows only that client's rows.
  3. Try opening the other client's page by changing an ID in the address bar.
  4. Remove a user and confirm their access ends immediately, in one place.

If a provider can't explain where access is enforced in one sentence, ask again before any client data goes in.

Customer portal development with Power BI Embedded

If your team already builds everything in Power BI, there is a middle route: embed the Power BI reports inside your own web application. Microsoft calls this embedding for your customers, also known as app owns data. Your clients log in to your application, and according to Microsoft they don't need to sign in to Power BI or hold a Power BI licence. The catch is that production use requires a capacity, which is a monthly cost of its own, and the application around the reports still has to be built, with its own login and its own access rules passed through to the report.

That route makes sense when the reports are complex, your analysts maintain them in Power BI already, and the number of clients justifies the capacity. When the dashboards are fairly standard (a set of KPIs, a trend chart, a table of campaigns or orders), a web dashboard built into the portal is often simpler and needs no per-user licence or capacity at all. I build both, as Power BI dashboards or as web dashboards, and the choice usually follows from the tools your team already maintains.

White label client portal or off-the-shelf portal software

There is a large market of client portal software, and for many firms it is the right answer. If what clients need is file sharing, messages, invoices and e-signatures, a subscription tool does that well and costs less than any build. I would tell a client that before quoting a custom portal.

The off-the-shelf tools run out when the reason clients log in is your data: campaign results, project progress, stock levels, financial figures, anything that comes from your own systems and needs calculating before a client can read it. A portal tool can host a PDF, but it can't join your CRM, your ad accounts and your time tracking into one per-client view, or apply your own definition of a qualified lead. That is the case for a custom build, and it is also where a white label client portal pays off, because the reporting becomes part of the service you sell and carries your brand. For agencies specifically, my page on white label client reporting describes that setup.

How to decide between shared dashboards and a portal

A few questions settle most cases:

Say a twelve-person marketing agency reports to 25 clients from Google Ads, LinkedIn and the CRM, and spends two days each month on slides. Shared Looker Studio copies would work for a while, but every new client means another copy and every metric change means 25 edits. A portal with one data model, one login per client and an approved monthly note fits them better. A consultancy with four long-term clients and one spreadsheet each would be wasting money on a portal; a well-built shared report and a careful sharing setup is enough.

What a custom client portal project looks like

A portal project with me follows four steps. First you and I list what each client or user should see, where that data lives today, and who needs access. Then I connect the sources, build one clean data model and write the access rules, so every user's rows are defined before any screen exists. Next comes the build and a pilot with one friendly client, which catches the confusing labels and missing numbers that no internal review finds. Finally everyone gets access, your team learns the admin side, and you receive the code, the repository and documentation.

If you want to see what a client would look at after logging in, this concept lead generation report is built on sample data for a fictional agency and its client, with a read-only shared view, a campaign table and a reviewed AI summary. It is the kind of page that would sit behind each client's login.

The data can be hosted in EU regions where the provider offers them, NDA and DPA are available on request, and you own the code, the database and the domain. If you are weighing a portal for your own clients, my page on client portal development covers how I scope and price it.

Frequently asked questions

What is a client dashboard?

A client dashboard is a report that shows one client the figures that matter for the work you do for them, such as campaign results, project progress or order volumes, refreshed from your systems. It can be shared as a link or a PDF, or sit behind a login in a client portal where each client sees only their own data.

Is it safe to share Power BI reports with clients?

It is safe when you use secure sharing or embedding with row-level security, and unsafe with Publish to web. Microsoft warns that Publish to web makes a report viewable by anyone on the internet without signing in, including underlying data the report doesn't show. For client figures, use proper sharing, embedding for your customers, or a portal with its own logins.

Do clients need a Power BI licence to see their dashboard?

It depends on how you share it. Sharing reports directly from the Power BI service generally needs a licence per viewer unless the content sits on a capacity. With embedding for your customers, Microsoft says end users don't need a Power BI licence, but you pay for a capacity. A web dashboard inside a custom portal needs no Power BI licence.

When is off-the-shelf client portal software enough?

Off-the-shelf portal software is enough when clients mainly need files, messages, invoices and signatures. It is cheaper than a build and quick to set up. It falls short when clients log in to see figures calculated from several of your own systems, such as ad platforms, a CRM and time tracking joined per client.

How do you stop one client seeing another client's data?

Enforce access in the database, not only on the screen. With row-level security, every query returns only the rows the signed-in user may see, whichever page sent it. Then test it: create two test clients, log in as each, try changing IDs in the address bar, and confirm removed users lose access immediately.

Can a client portal carry my own brand?

Yes, a custom or white label client portal can use your logo, colours and domain, so clients see your service and not the tool behind it. That suits agencies and consultancies whose reporting is part of what clients pay for. Many off-the-shelf portal tools offer branding too, though usually within limits set by the vendor.

Want a second pair of eyes on it?

Send me the link and what it should achieve, and I will tell you what I would change first, with a fixed quote if you want one. Usually within a few hours on working days.

Get a free quote →