Operations overview
Operational reporting from the existing PoK Worker and D1 database.
Current best seller
Loading sales health…
Needs sales support
Loading sales health…
Sales history begins when this build is deployed.
Venue performance
Upcoming events only| Venue | Upcoming | Tickets sold | Offers | Venue users | Last portal visit | Status |
|---|
Needs attention
Operational flagsTop upcoming events
Ranked by tickets sold| Event | Venue | Date | Tickets sold | Capacity |
|---|
Venues
Edit operational venue information without touching the D1 console.
| Venue | Status | Tags | Spaces and setup styles | Venue max capacity | Wheelchair access | Upcoming | Tickets sold | Last portal view |
|---|
Venue Offers
Approve venue offers once, then review their automatic eligibility and publishing status.
Safe publishing: Venue offers need PoK approval and an opted-in venue. Actual Ticket Tailor writes remain disabled unless the separate Cloudflare safety switches, admin lock, and event allowlist all permit them. Existing test events stay isolated.
Ticket Tailor test sync health
Single allowlisted Balham test event only. No live PoK Ticket Tailor publishing.
Loading status…
Retrieving the latest recorded test sync state.
Recent Ticket Tailor test sync attempts
| Time | Result | Offer / trigger | Sync ID |
|---|
Phase 3 failure-recovery lab
SIMULATION ONLY: Balham dummy event. No Ticket Tailor calls or changes to real venue offers.
Checking whether the isolated failure test is enabled.
Simulated failure audit history
| When | Admin | Simulation action | Details |
|---|
| Venue | Offer | Type | Scope | Status | Publishing | Sync status | Decision |
|---|
Users & Access
Manage PoK staff accounts and venue access separately.
Platform housekeeping
Review legacy test data, account access and venue onboarding gaps without altering records automatically.
Non-destructive by design. Nothing on this screen deletes accounts, offers, events, spaces or logs. Use the existing individual Edit controls to deactivate or archive records after checking their ownership. Preserve Balham Bowls Club as a real venue.
Review statusLoading…
Checking Ticket Tailor safety settings…
Explicitly labelled test offers
Review or archive individuallyAccounts to review
Test-labelled, inactive or awaiting activationVenues awaiting partner access
Active venues with talks and no active venue loginOperational checklist
Real venue onboarding deferredKeep live Ticket Tailor publishing disabled
Leave the global live-write and rollout-arming switches off until the first genuine approved venue offer is reviewed.
Retire old testing access manually
Deactivate test venue users, review test-only offers, retain named audit history and genuine event records.
Invite one genuine venue later
When a venue partner is available, verify their activation email, assigned venue and one event total before inviting more.
Regional Ticket Tailor connections
Read-only API imports per city. No Ticket Tailor descriptions, prices, orders or tickets will be changed. Import one city at a time; errors do not delete other cities.
Open Publishing to review regional connections.
Publishing
Restricted operational controls for the first genuine venue offer and safe Ticket Tailor publication. Backend safety switches remain independent of this interface.
Approved offer publishing queue
Automatic eligibility is calculated from events and approved offers. A queued job does not mean a live write occurred.
Loading publishing settings…
| Event | Venue | Publishing state | Last change |
|---|
Operational publishing pilot
First opt a venue into automatic approved offers in its venue settings, approve the offer, and stage that event below. The preview is read-only. Exact publishing requires a fresh preview and the typed confirmation.
No publishing preview generated.
DEFAULT SAFETY LOCK: Worker v58 implements a gated live-write path. No live write is possible unless the separate live-write secret, Cloudflare switch, explicit event allowlist, opted-in venue, emergency-stop release, admin arming and verified singleton event-series checks all pass. Balham test integration remains separate.
Live rollout control centre
Checking…Loading safety settings…
Retrieving rollout lock state…
Live offer eligibility and approval
The historical test-account tools are separate. Genuine venue offers still require PoK approval and the live publishing safety gates.
An offer requires two deliberate admin steps: Mark live candidate, then Approve for live with a fresh review of its exact content. Text labelled TEST or DUMMY is blocked. Editing or resubmitting an offer voids its live approval. Live Ticket Tailor writes are supported only through the separately locked Worker v58 pilot path.
Loading live offer eligibility…
Advanced arming rehearsal (normally disabled)
This only rehearses the safety lock. It NEVER enables live publishing in v52. Reset/arming requires POK_LIVE_ROLLOUT_ARMING_ALLOWED=true and typed confirmations.
Safety release checklist: venue opt-in; PoK approval; explicit event allowlist; singleton event series; original content backup; exact post-write readback; no automatic retries after uncertain outcomes; emergency stop available.
Diagnostics
Historical platform testing and troubleshooting tools. Restricted to PoK admins, normally left closed.
These are legacy diagnostic controls, not routine operational tasks. Changes can affect stored safety state. Do not use them during normal venue administration.
Activity & Audit
Recent platform changes, venue activity and account access. Admin-only.
| When | User | Action | Venue | Details |
|---|
Shows the latest 300 platform activity records. This uses the existing lightweight activity log, so no duplicate audit-history storage is created.