Skip to main content

Two sidebars, one set of pages

TPAS renders five sidebar groups, and two of them are alternatives to each other rather than additions:

GroupShown to
Operationseveryone
Managementanyone with a dashboard of their own — dashboard:read or dashboard:read-uwa
Registryeveryone else
Insightseveryone
Administrationeveryone

Management and Registry lead to the same pages. Management arranges them into two drop-downs — Vehicles Management and People Management — and adds the Visitors register; Registry lists them flat, which suits a contractor's narrower set. So:

PageUnder Management (TotalEnergies)Under Registry (everyone else)
VehiclesVehicles Management → VehiclesVehicles
OBU InstallationVehicles Management → OBU InstallationOBU → OBU Installation
Installation ReportVehicles Management → Installation ReportOBU → Installation Report
OBU DistributionVehicles Management → OBU DistributionOBU → OBU Distribution
TotalEnergies StaffPeople Management → TotalEnergies Staffnot shown
VisitorsPeople Management → Visitorsnot shown
Master ListPeople Management → Master ListMaster List
Access RequestsPeople Management → Access RequestsAccess Requests
Personnel & BadgesPeople Management → Personnel & BadgesPersonnel & Badges
Stock OverviewStock OverviewStock Overview
note

A path printed in this manual as Management → … and a path printed as Registry → … are the same destination. Where the two differ the chapter says so.

Operations is collapsed by default; the other groups open.

What each permission unlocks​

The authoritative map.

GroupEntryPermission required
OperationsDashboard (contractor view, /)registration:create
Dashboard (/dashboard)dashboard:read
UWA Dashboarddashboard:read-uwa
Gate Activityaccess-record:read
Gate Screenverification:verify
Verify Accessverification:verify
Management / RegistryVehiclesvehicle:read
OBU Installationaccess-device:read
Installation Reportorganisation:read
OBU Distributionaccess-device:read
TotalEnergies Staffpersonnel:read
Visitorsvisitor:read
Master Listmaster-list:read
Access Requestsregistration:read
Personnel & Badgespersonnel:read
⤷ Badges (a contractor's folder)card:read
Stock Overviewdevice-stock:read
InsightsReconciliationreconciliation:read
Tourist Paymentsreport:read
Reportsreport:read
Incidentsincident:read
AdministrationContractorsorganisation:read
Users & Roles → Usersuser:read
Users & Roles → Rolesauthz-role:read
Devices → Gate Devicesgate-device:read
Devices → Device Registryaccess-device:read
Settingssetting:update
note
Settings is gated on setting:update, not setting:read

Almost every role holds setting:read, because the four stock thresholds are printed under the tiles that measure against them. Gating the menu entry on read would put Settings in every contractor's sidebar, so the entry follows the permission that actually lets you change something.

Stock Overview is the whole device-stock module: pick a contractor, then Devices, Dispatches, Returns and Repairs as tabs. The Repairs tab needs device-stock:repair, so a contractor sees the other three and not that one.

Pages that are not in the sidebar​

Three kinds of address exist outside the map above:

AddressWhat it is
/notificationsThe notification history (Notification history). Reached from the bell, never the sidebar. No permission of its own.
/stock/dispatches, /stock/returns, /stock/repairs, /stock/custodyThe device-stock surfaces before they became tabs. Still routed, so older links and notifications keep working. Gated on device-stock:read like the tab.
/stock/dispatch, /stock/returnThe two batch pages, reached from a button (Dispatch, Starting a return).
/visit, /pass/{reference}The public tourist pages — no sign-in, no permission at all (Park pass).

Permissions that gate buttons, not pages​

Seven permissions never appear in the menu map because they unlock actions. Everyone who can open a stock page holds device-stock:read; what they can do there depends on which of these they also hold:

PermissionThe action it unlocksHeld by
device-stock:dispatchSend issued devices to a contractor; renew a held device in placeTotalEnergies stock control
device-stock:receiveConfirm a dispatchThe contractor
device-stock:returnStart a returnThe contractor
device-stock:acknowledgeRecord what came back; take a badge back at the desk; declare a device lostTotalEnergies stock control
device-stock:repairTriage a quarantined device; close a repair, including writing it offA TotalEnergies administrator
device-stock:manageApprove or decline an extension request; run the overdue chase by handA TotalEnergies administrator
setting:updateChange the four SLA thresholdsA TotalEnergies administrator

This is why a contractor and an administrator open the same Dispatches tab and see different buttons on it. The page is one permission; the buttons are several (Device stock).

Read the map backwards to diagnose a complaint: "I can't see Reports" → the account lacks report:read.

The map is the single source of truth for both the route gate and the page header, which is why a refused page never describes the page it is refusing you ("No access to this page").