The work you do for a customer should show

A separate permission, not a reduced one

A customer holds a role of its own, and only the portal endpoints accept it. No operator endpoint answers to it — which is the only way to be sure one customer never reads another's switch inventory.

It talks about services, not devices

The portal is about “internet banking” and “the payment gateway”, not about core-sw-01.

• Each business service by name and state, with a count of what backs it — never which targets those are
• 30-day uptime per service and overall
• “Not measured” where there is no data: a customer who reads 0% concludes their network was down all month
• Each card is its own call, so an unlicensed module or a restarting service costs one card, not the page

Maintenance, documents and usage

The things a customer normally chases by email are on one page.

• Planned maintenance windows, with alerts silenced for that period
• The monthly report as PDF or Excel
• The documents you sent them
• What they are using against the quotas they agreed to

Requests are a conversation, not a ticket

No assignment, no SLA clock — technical alerts still go to your own ticketing system.

• A capacity request carries the numbers, so an operator need not read them out of prose
• A queue for your team, linking straight to the quotas
• An internal note: a reply only your team sees, which does not notify and does not mark the request answered
• A weekly summary mailed to each customer, at most once per week

Your brand, not ours

Each organisation's logo, name and colour go on the portal, the sign-in page, the public status page and even the letterhead of the documentation reports.