Role reference
TPAS shows each person a different portal. This chapter is the reference for what each role gets — where it lands, what appears in its sidebar, and what it is refused.
Four rules explain almost everything you will see:
- Every nav entry carries a permission. If your account does not hold it, the entry is not rendered. An entry that is missing is not broken — it is hidden on purpose. A group whose every entry is hidden disappears too.
- Routes are gated as well as menus. Typing the address of a page you cannot open gives you No access to this page, not the page.
- The sidebar is split by audience. TotalEnergies' own staff and contractors are shown the same pages under different groups — see Two sidebars, one set of pages.
- You land on the first page you can open. If your role lacks
dashboard:read, TPAS does not drop you on a refused dashboard — it sends you to the first entry in the menu that you can actually use.
The landing order in full:
| # | Condition | Lands on |
|---|---|---|
| 1 | A kiosk user — holds verification:verify and no shell permission | the full-screen Gate Screen |
| 2 | dashboard:read | the staff Dashboard |
| 3 | dashboard:read-uwa | the UWA Dashboard |
| 4 | registration:create — a contractor, i.e. somebody who submits access requests | the contractor dashboard at / |
| 5 | anyone else | the first nav entry they hold a permission for |
| 6 | no accessible nav entry at all | the empty state — "You don't have access to any dashboards yet" |
Rule 1 is narrower than it looks. A kiosk user is somebody who can verify at
a gate and holds none of the nine shell permissions — access-record:read,
vehicle:read, personnel:read, registration:read, reconciliation:read,
report:read, organisation:read, user:read, authz-role:read. Hold even
one of them and you get the ordinary portal, sidebar and all. Of the roles in
the catalogue only Park auditor qualifies; the gatekeeper does not, because
it holds vehicle:read.
Rule 4 is worth reading twice. The contractor dashboard is reached only by roles
holding registration:create — submitting access requests is what a contractor
uniquely does. Roles that merely read or approve requests, such as the
reconciler and the viewer, are TotalEnergies' own staff and land under rule 5
instead.
Permissions are strings shaped resource:action — user:read,
incident:resolve, master-list:create.