Revenue is the owner's alone

Platform revenue figures are withheld at the source for anyone without the billing capability — not merely hidden by the interface.

What it is

billing.view is a capability held by the owner alone. The endpoint that returns the account list zeroes the revenue field before it leaves the server for any caller who lacks it, so the number never reaches the browser regardless of what the interface chooses to render.

Also called: who sees MRR · billing visibility · staff can't see revenue

See it
Revenue is the owner's alone
Area
Platform & Admin
Group
Vendor access
System
Multi-Tenancy & Identity
Solves
2 named problems
01The capability is deliberately excluded from the admin role's list.
02The account-list endpoint checks the capability and zeroes estimated revenue at the source when it is missing.
03The comment in the route makes the reasoning explicit: hiding a column is not the same as withholding the number.
The account list as an admin sees it, with the revenue column absent and the payload showing zeroes. src/app/api/platform/orgs/route.ts. Sample data — no customer information appears here.
How it works
  1. 1The capability is deliberately excluded from the admin role's list.
  2. 2The account-list endpoint checks the capability and zeroes estimated revenue at the source when it is missing.
  3. 3The comment in the route makes the reasoning explicit: hiding a column is not the same as withholding the number.
  4. 4Capabilities shipped to the browser let the UI hide the column too, but that is presentation only.
Why we built it

The narrowing is dated and quoted: 'NOT billing.view (Keith 08-12): the admins don't need to be able to see the money either.' The reasoning follows: 'Platform revenue — MRR, ARR, ARPU, plan distribution, what any tenant pays — is the owner's alone. An admin can run every operational surface without it, and revenue is the one thing that leaks the shape of the whole business from a single screen.' It is flagged as intentional rather than an oversight: 'This is a deliberate narrowing of an existing role… If an admin ever needs a figure, they ask the owner, and the ask is visible rather than a silent read.'

The problem
  • One screen exposing the shape of the entire business to every operational employee.
  • UI-level hiding leaving the number in the response payload.
Sound familiar?
What you get
What you pay is not visible to the vendor's operational staff.
The restriction is enforced in the response, not the rendering.
Requests for a figure are a visible ask rather than a silent read.

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →