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 access

Internal GCCAP surface

Manage alert queues before client teams and future command centre workflows consume them.

The Alerts Lab is an internal operating surface. Use it to sync rule incidents into alerts, review open and breached alerts, acknowledge issues, record corrective actions, close alerts, and inspect the notification outbox.

Return to public platform Open portal access

StatusInternal / restricted surface. Not part of the public client walkthrough.

GCCAP

Sensor

Gateway

Evidence

Watchdog

Journey intelligenceRepresentative demo

ControlsSync / ack / CAPA

EscalationSLA-aware

VisibilityAdmin plus tenant-safe

OutputLocal outbox

Build 8 operational tool

Alerting and incident management lab

Sync cold-chain rule incidents into operational alerts. Review priority, SLA status, routing, local notification outbox, acknowledgements, escalation, corrective actions, closure, and false-positive controls before production notification channels are connected.

Admin access

Use the same GCCAP_ADMIN_TOKEN configured for the intake, pipeline, journey, rules, reporting, and portal admin APIs.

Admin token

Waiting for server response.

Alert controls

Run after Build 5 rules have produced incidents. Sync preserves open alerts and creates new alerts from current rule incidents.

Alert status

Stats load after token is saved.

Policy snapshot

Notification outbox

Alert queue

Selected alert

Select an alert to test acknowledgement, escalation, corrective action, closure, or false-positive workflow.

Decision clarity

How to use this lab

Run this after Build 5 has evaluated rules. For a full pilot flow, intake sample payloads, process pipeline, rebuild journeys, evaluate rules, sync alerts, then approve reports for client portal visibility.

Step 1Save the admin token configured by GCCAP_ADMIN_TOKEN or use GCCAP_UNSAFE_LOCAL_ADMIN=true only for local testing.

Step 2Click Sync from incidents to create or update alert records from current rule-engine incidents.

Step 3Acknowledge, escalate, add corrective action, close, or mark false positive from the selected alert.

Step 4Use the notification outbox as a staging layer until production email, SMS, Teams, webhook, and client routing are built.