Recent conversations
Each Flight Control user only sees their own Craig sessions.
No Craig conversations yet. Start with a business question.
Access gate for dashboards and internal tools.
Choose a department to browse the tools and dashboards available to you.
Your account is active but no tools are assigned yet. Ask an admin to grant access.
Flight Control concierge combining the daily architecture context, canonical Data Platform, live approved APIs, and access-aware app routing.
Each Flight Control user only sees their own Craig sessions.
No Craig conversations yet. Start with a business question.
Craig is ready. Ask where a number lives, which app to use, or whether a better source already exists.
Choose what Craig should include by default for you.
Craig will summarise the best approved source here.
Checks uptime, pathway freshness, and integrity across the tools currently wired into Flight Control.
The monitor has not stored any health runs yet. Refresh or run the monitor to build the first snapshot.
Operational health across the backend workers and scheduled processes that power Nectar communications.
Active and muted operational alerts across services, processes, and channels.
Aggregate availability checks for communications workers and scheduled services.
Aggregate event volume and freshness by communications channel.
Offline conversion, Google Ads, BigQuery, SMS, and feedback process health.
Sanitized operational metadata only: timestamp, channel, and event type.
Worker health data is unavailable.
BigQuery processing volume, estimated USD cost, cadence, and anomalies attributed to Flight Control apps and background processes.
Apps incurring an MTD cost are shown first. Cost is month to date and the change compares with the same period last month.
BigQuery work that cannot yet be assigned to one governed app remains visible here rather than being guessed into an app.
High-frequency, heavy-scan, and sharply increasing query families are surfaced first. Mark a mitigation for up to 30 days; the alert automatically returns when it expires.
| App / process | Est. cost | Executions | Statements | Avg. billed / execution | Approx. cadence | 7-day change | Status |
|---|
The first bounded BigQuery usage refresh will populate this page. Flight Control checks every 15 minutes, refreshes this rollup every six hours, and permits a manual refresh after a 30-minute cooldown.
Always-on security monitoring for Flight Control. See what is happening, what was blocked, and whether anything needs a person to investigate.
Real-time security monitoring across the Flight Control platform
Activity is grouped and labelled as Normal, Managed, Needs review, or Confirmed incident.
| Time | Priority | What happened | Source | Result |
|---|
Locations are approximate; internal activity is labelled rather than plotted as a country.
Last 24 hours
Grouped and privacy-safe.
Whether the monitor is working.
Checking the current security state...
These settings control warning emails and emergency SMS. Monitoring is always on; changing these settings only changes who is notified and how often routine alerts are grouped.
Only the people listed here receive Threat Monitor alerts. The system will not automatically email every Super Admin.
Routine blocked requests are grouped instead of generating a new email for every event.
SMS is reserved for critical signals such as a successful login after repeated failures.
This prevents an alert storm while keeping every event in the monitor.
Flight Control keeps enough history to explain an incident and verify what happened. These technical retention values do not change whether monitoring is active.
Open risks are plotted below using the fixed likelihood and consequence matrix.
Current risks that still need an acceptance, mitigation, or emergency decision.
| System | Risk | Why It Matters | Likelihood | Consequence | Rating | Current State | Recommended Next Step | Last Updated |
|---|
These are the things we have fixed, retained as a quieter audit and learning history.
| System | Risk | Why It Matters | Likelihood | Consequence | Rating | Current State | Recommended Next Step | Last Updated |
|---|
One email per line. These people receive the summary PDF when the twice-weekly review finishes.
Each automated security run saves a one-page PDF here for later review.
See how the team uses Flight Control and which governed apps are being launched. Destination-app activity is not tracked here.
Sessions, app handoffs, and failed launches by Pacific/Auckland day.
Users with recorded Flight Control activity in the selected range.
No usage has been recorded in this range yet.
Active users with no recorded app launch in the selected range.
Track personal Codex spend against the monthly allowance, keep workspace usage visible, and keep the shared Codex setup pack in a separate home when people need it.
Checking your current spend against your Codex allowance.
Loading your latest available usage trend.
Loading the latest available workspace trend.
Loading shared budget metrics for the current month.
Loading daily workspace model usage.
Admin-only view of user usage against allowance, with estimated cost at $0.085 per credit.
| User | Limit | Used | Est. Cost | Remaining | % Used | Status |
|---|
The Codex usage warehouse tables are not available yet, or the latest refresh has not landed.
No GitHub, PowerShell, or Windows Scheduler setup is required. Flight Control installs the shared rules and keeps only the Nectar-managed parts up to date.
Looking for a registered Nectar Codex installation.
Every new Codex task receives the approved Nectar rules automatically, while existing personal instructions are preserved.
The installer never changes the selected model or Fast Mode itself. It gives a short recommendation only when the current choice is unsuitable.
The updater checks when the employee signs in and each Monday at 9:30am. If the computer was off, Windows runs the missed check when it is next available.
Codex loads its instructions when a task starts. Existing conversations keep the instructions they started with.
If Flight Control shows that an update has just installed, start a new Codex task. Restart Codex only if a newly installed skill does not appear.
Super Admin preview mode lets you test what a specific person would see, and whether it is the internal or partner portal experience.
Please speak to an admin to set you up with an account.
Manage user access or add a new app to Flight Control without republishing the whole frontend.
Internal users can only be assigned internal or shared apps.
Showing internal users only.
| Role | Portal | Status | Expiry | Tools |
|---|
Paste the deployed Pages or Worker URL, choose how it should appear in Flight Control, and decide who should see it.
Choose exactly who should see this app in Flight Control. Super Admins are always included.
Flight Control will save the app name, category, state, version, link, and Flight Control access rules.
You may still need to configure Cloudflare Access on the destination app itself so the right people can actually open it.
If that step is not already done, contact Ed and ask him to apply the matching Cloudflare Access policy for the app URL.
Flight Control will save the app here, but the final Cloudflare Access step still needs Ed to do it manually for now.
Choose an existing Flight Control app, update its details, or delete it entirely.
Choose exactly who should keep access to this app inside Flight Control.
Loading Craig metadata coverage...
You can update the app name, category, status, version, URL, description, and who can see it in Flight Control.
If the app is protected by Cloudflare Access, any matching policy changes on the destination app may still need Ed to adjust separately.
Deleting an app removes it from the Flight Control registry and clears user-specific permissions and favourites for that app.
Review the risk details and choose the next step.