Tenant login
Client users authenticate through the portal and are bound to one client account.
Internal GCCAP operating surface
This page is retained behind the public client website.
GCCAP does not delete operating records, trial packs, hardware activation surfaces or evidence automation layers. They are preserved for authorised client portal, command-centre and internal operating use while the public website stays clean for airline first impressions.
Open portal accessInternal GCCAP surface
The private client layer that turns GCCAP evidence into client trust.
Internal system phase gives authorised pilot clients a restricted portal view of their own operational evidence. It does not expose internal labs, draft reports, other clients, command-centre data, or public Watchdog staging.
StatusInternal / restricted surface. Not part of the public client walkthrough.
GCCAP
Sensor
Gateway
Evidence
Watchdog
Journey intelligenceRepresentative demo
Portal usersClient admin / ops / auditor / viewer
Data shownTenant-only
Reports shownApproved or issued only
Operational layer
What Build 7 completes
The portal turns GCCAP from internal evidence generation into a controlled client-facing product layer.
Role-based access
Client admin, operations, auditor, and viewer roles are supported for pilot-stage access control.
Client dashboard
Clients see their cart count, journeys, open incidents, high-risk issues, reports, and evidence confidence.
Approved reports only
Draft reports stay internal. The portal exposes only reports approved or issued through Build 6 governance.
Decision clarity
Data boundaries
The portal is deliberately narrower than the internal GCCAP labs and future command centre.
IncludedClient-only carts, journeys, incidents, approved reports, evidence exports, and device health.
ExcludedInternal intake lab, pipeline lab, rules lab, draft reports, all-client command view, Watchdog staging, and other-client data.
Current storagePilot-stage file-backed storage suitable for local/private testing.
Production upgrade neededDatabase-backed tenant isolation, MFA, audit retention, SSO, production secrets, monitoring, backups, and security review.
Data path
Build 7 data path
The portal consumes the evidence chain already built in Builds 2 through 6.
01Sensor captures cart temperature behaviour
02Gateway collects sensor records
03Raw payload is received and preserved
04Payload is mapped to sensor, cart, gateway, site and client
05Temperature event is normalised into the GCCAP event model
06Event is assigned to the correct cart journey stage
07Rules engine flags warning or review conditions
08Recovery and duration are calculated
09Data completeness and hardware health are assessed
10Evidence report is prepared for private client review
11Approved outputs can support client action and future benchmark methodology
Strongest next move
Use the portal to support paid pilots
After Teltonika/CtrlOps sample data arrives, run it through intake, pipeline, journey reconstruction, rules, reports, then expose approved outputs through the restricted portal.
Request a controlled pilot