FDC Admin Center
Unified administration workspace for Flight Delay Center only.
Backend not connected

One control center for FDC operations.

Manage join requests, FDC permissions, users, and audit findings without touching legacy OAP keys.

FDC scoped Read-only legacy keys No DB writes connected
Pending Requests —
Active FDC Users —
FDC Permission Keys 8
Legacy Warnings 3

FDC Modules

Module Permission Key Status
Dashboard FDC_DASHBOARD Scoped
TRC Coding FDC_TRC_CODING Scoped
Department Response FDC_DEPARTMENT_RESPONSE Scoped
Evidence FDC_EVIDENCE Scoped
AI Review FDC_AI_REVIEW Scoped
Final Allocation FDC_FINAL_ALLOCATION Scoped
Employee Email Status Created Action
Live data not connected
Request Details
Employee ID —
Email —
Status Waiting for live data
Scope FDC_JOINING_ADMIN
Permission Description Scope Status Access
FDC_DASHBOARD Main dashboard access FDC Active
FDC_TRC_CODING TRC coding workflow FDC Active
FDC_DEPARTMENT_RESPONSE Department response workflow FDC Active
FDC_EVIDENCE Evidence management workflow FDC Active
FDC_AI_REVIEW AI review workflow FDC Active
FDC_FINAL_ALLOCATION Final allocation workflow FDC Active
FDC_JOINING_ADMIN Join request administration FDC Preview
FDC_PERMISSIONS_ADMIN FDC permission administration FDC Preview
Save controls are disabled until backend functions are separated safely for FDC.
User Employee ID Email FDC Access Status Action
Future FDC user — — — Ready layout
Live data not connected

Legacy Warnings

JOINING_ADMIN Legacy key detected. Do not edit from FDC unless tied to an FDC path and confirmed.
PERMISSIONS_ADMIN Legacy general admin key. Do not rename globally because older admin functions may depend on it.
admin_panel Inactive legacy page key on permissions path. Review only before cleanup.

Safe Correction Rules

  1. Do not update rows where page_path is NULL.
  2. Do not rename PERMISSIONS_ADMIN globally.
  3. FDC writes must use FDC_ keys only.
  4. Any live action must pass backend validation before commit.