Skip to main content

TPAS User Manual

Total Park Access System — TotalEnergies EP Uganda. Vehicle and passenger access control for the Murchison Falls park gates: Tangi, Bugungu and Kifumbanyobo.

About this manual​

This manual describes the TPAS web portal, and the gate reader app the gatekeepers carry, as they behave today, screen by screen. Every procedure was walked through in a live environment and captured as it appeared — the screenshots are of real sessions, not mock-ups.

Where a screenshot and the text disagree, trust the text

The portal is developed continuously, and a screen occasionally gains a control or changes its styling before the picture beside it is re-taken. The words describe the portal as it behaves today.

TPAS is permission-driven: two people signed in at the same time see different menus, different buttons and different rows. Rather than repeat "if you can see this" on every page, each chapter opens with a Who can do this box naming the exact permission involved, and the role reference maps every role in the system to what it can reach.

Where a screen cannot yet do something you would reasonably expect of it, the manual says so in an Important callout and tells you what to do instead, rather than describing behaviour that does not exist.

Conventions​

Callouts carry a fixed meaning throughout:

CalloutMeaning
Who can do thisThe permission your account needs. Without it the menu item is hidden and the address returns No access to this page.
ImportantA limit of the screen, and what to do about it. Do not rely on the screen doing more than this says it does.
NoteDetail worth knowing about how a screen behaves — what a figure counts, what a check does and does not prove.
TipA shortcut or a habit worth forming.

Screens are named as they appear in the sidebar. A path like Registry → Personnel & Badges → Badges means: expand the Registry group, open Personnel & Badges, then select the Badges tab.

The sidebar is not the same for everyone. TotalEnergies staff are shown a Management group with two drop-downs; contractors are shown a flat Registry group. They lead to the same pages, so one path appears as

  • Management → People Management → Master List for TotalEnergies, and
  • Registry → Master List for a contractor.

Each chapter prints the path for the audience it is written for, and says so where the two differ. The sidebar has the full map, and Two sidebars, one set of pages explains which accounts get which.

Two ways to run TPAS​

The portal runs in one of two modes, and it matters for what you see:

  • Live mode — the portal is pointed at the real identity provider and the real TPAS backend. Sign-in redirects you to the TotalEnergies sign-in page, and your permissions come from your account. This is what this manual documents.
  • Demo mode — with no identity provider configured the portal falls back to a built-in demo session with seeded sample data and all permissions granted. Useful for training and screenshots; nothing you do there reaches the real system.

If you never see a redirect to an external sign-in page, you are in demo mode.

Two things behave differently in demo mode

Every permission is granted, so the sidebar shows every entry and the role reference does not describe what you see. And device stock has no demo data at all — every list is empty and every action fails, because that module talks only to the live backend.