Customer & partner portals

Area: Dashboards & Web Applications · Usual shape: external portal + internal view · The foundation: permissions

Every call asking "where is my order?" is work that did not have to happen. A portal moves the answer to the person asking — but the hard part is not the display, it is the boundary: what each party may see, and what must never appear. That is where we start.

Talk to us about your project See the whole area

Opens WhatsApp. Nothing is sent until you press send there.

What this solves

Customers phone to ask for status you already know.
Partners are served statements by email attachment.
Requests arrive in several inboxes and get lost.
Nobody can prove what a customer was shown, or when.

What we build

An external account, invitation and registration model.
Precise permission boundaries per party.
Display of the customer’s own records, documents and status.
Requests and tickets with status tracking.
Notifications when something changes.
Document and invoice download.
An internal view where your team sees the full picture.
An access log showing who saw what.

Where it is used

Customers calling to check order status.
Partners or distributors who need their statements.
Members, patients or students who need their own records.
Suppliers who need to see purchase orders and their status.

What this does not include

We do not provide identity verification as a regulated service.
We do not give an opinion on compliance with any data-protection regime.
We do not guarantee that a third party’s system will open its data.
Payment inside the portal is agreed separately.

How the work goes

We start from what each party may see, and write it down before designing anything.
We build the permission boundary first and test it with real records.
We launch to a few accounts before all of them.
We watch what people still phone about, because that is what the portal missed.

Web applications
when it is a product in its own right rather than a window.
Custom business systems
when the records it would show are not held anywhere yet.
System & service integrations
to draw the data from the system that holds it.
AI assistants & conversational interfaces
when the questions are open rather than about their own records.

Questions about this service

How do we know one customer cannot see another’s data?

By making that the first thing built and the most heavily tested. Permission boundaries added after the screens exist are where these systems fail.

How do customers get accounts?

Usually by invitation from your side rather than open registration, which keeps the account list matched to your real relationships. We agree the model in scope.

Can it connect to the system we already have?

That is the normal case — a portal is a window onto data you already hold. What matters is whether that system exposes it, which we check first.

Can partners upload documents?

Yes, where the process needs it, with the same permission boundary applied in the other direction.

Does it work on a phone?

Yes, and it usually matters here more than elsewhere: checking a status is exactly the kind of thing someone does from a phone.

Tell us what your customers keep phoning to ask.

Talk to us on WhatsApp Or send the details through the form