Workspace · Operations
Admin
Total Users
—
Total Projects
—
Projects This Month
—
New Users (30d)
—
Active (30d)
—
Online Now
0
Admin Users
—
with full access
Equipment (DB)
—
custom entries
Active Announcements
—
currently showing
Live Users
Connecting…
Platform Analytics
Daily Active Users (30d)
Unique users with project updates per day
Platform Signups (12 weeks)
New user registrations per week
Project Status Distribution
All projects by current status
Top Equipment Used (Platform)
Most used HVAC unit types across all users
Recent Activity
Last 20 project updatesLoading…
Build —
—
—
0 selected
All Projects
| Project Name | Owner | Status | Elements | Last Updated | Actions | |
|---|---|---|---|---|---|---|
| Loading… | ||||||
Settings
Database setup required — click to view SQL
Run schema.sql from the project root (covers all tables), or run these individually:
RLS: admin full access; authenticated users can
Business branding column:
create table system_settings (key text primary key, value text not null, description text, updated_at timestamptz default now());RLS: admin full access; authenticated users can
select.Business branding column:
alter table profiles add column if not exists business_profile jsonb default '{}'::jsonb;
Logo storage bucket — click to view SQL
Run once in Supabase → SQL Editor to create the logos bucket and RLS policies (included in schema.sql).
Loading settings…
Testing
Changes your own account only.
My account industry
Switch your own account between the HVAC and NDIS verticals for testing. Independent of the global
feature_industry_ndis flag above, but NDIS surfaces only appear when that flag is also on. Reload after changing.Feature flags
/
Flag
Area
Stage
Changed
Loading flags…
On for 30 days or less is “Rolling out”; longer is “Launched”.
Audit Log
Database setup required — click to view SQL
Run schema.sql from the project root, or create the table manually:
RLS: admin can
create table audit_log (id uuid primary key default gen_random_uuid(), actor_id uuid, actor_name text, action text not null, target_type text, target_id text, detail jsonb, created_at timestamptz default now());RLS: admin can
select and insert.
| When | Actor | Action | Target | Detail |
|---|---|---|---|---|
| Loading… | ||||
Security Events
Database setup required — click to view
Apply db/add-security-events.sql (it is mirrored into db/schema.sql, so
npm run db:push creates it). That file adds the security_events table plus the
soc_summary, soc_auth_events and soc_prune_events functions this tab reads.
Events
—
in window
Failed Sign-ins
—
app, portal & field
Rate Limited
—
429 responses
Forbidden
—
403 responses
CSP Violations
—
sampled reports
Distinct IPs
—
seen in window
These are floors, not totals. The Worker caps how fast it writes this log
(10 rows per minute per event type per IP), so a burst records its shape and drops the rest —
read a number here as “at least this many”.
Busiest IPs
Most events in the window
—
Accounts Being Guessed
Most failed sign-in attempts
—
Most-hit Targets
Endpoints and policy directives
—
| When | Event | Severity | Account | IP | Target | Detail |
|---|---|---|---|---|---|---|
| Loading… | ||||||
Authentication Trail
Supabase Auth · sign-ins, sign-outs, recovery| When | Action | Account | IP |
|---|---|---|---|
| Loading… | |||
Online Now
Live presenceConnecting…
Announcements
Database setup required — click to view SQL
Run schema.sql from the project root, or create the table manually:
RLS: admin full access; authenticated users can
create table announcements (id uuid primary key default gen_random_uuid(), message text not null, type text default 'info', active boolean default true, expires_at timestamptz, created_at timestamptz default now());RLS: admin full access; authenticated users can
select where active = true.
| Message | Type | Status | Expires | Created | Actions |
|---|---|---|---|---|---|
| Loading… | |||||
Software Updates
Database setup required — click to view SQL
Run schema.sql from the project root, or create the table manually:
create table software_updates (id uuid primary key default gen_random_uuid(), version text not null, title text not null, description text, changes jsonb default '[]', is_published boolean default false, published_at timestamptz, created_at timestamptz default now());
| Version | Title | Published | Date | Actions |
|---|---|---|---|---|
| Loading… | ||||
Subscriptions
Paying accounts
—
Past due
—
Organisations
—
On Free
—
| Who | Plan | Status | Period end | Lemon Squeezy | Override tier |
|---|---|---|---|---|---|
| Loading… | |||||
Tier, status, credits and the Lemon Squeezy links for one person live on their record in Users. Business plans bill the organisation, not the member — see Organisations.
Accounts
—
checking…
New this month
—
Credits used this month
—
Pack credits sold
—
this month
User management
Loading users…
Select a user from the list.
Organisations
Loading organisations…
Membership is protected at the database — a business_members row must exist before
profiles.business_account_id may point at an org, so members move by invite, never by editing a profile.
Equipment Library
Database setup required — click to view SQL
Create the
SQL:
equipment_library table in Supabase, or run schema.sql from the project root to create all tables at once.SQL:
create table equipment_library (id uuid primary key default gen_random_uuid(), category text not null, data jsonb not null, active boolean default true, created_at timestamptz default now());
| Brand | Model | Type | Cool kW | Heat kW | L/s | Status | Source | Actions |
|---|---|---|---|---|---|---|---|---|
| Loading… | ||||||||
—
Waitlist
—
Invited
—
Beta Testers
—
Feedback
| Name | Company | Status | Submitted | Actions | |
|---|---|---|---|---|---|
| Loading… | |||||
| Name | Joined Beta | Beta Features | Actions | |
|---|---|---|---|---|
| Loading… | ||||
| User | Type | Rating | Message | Page | Date | |
|---|---|---|---|---|---|---|
| Loading… | ||||||
Manage which beta features are enabled and their rollout percentage.
| Key | Name | Description | Enabled | Rollout % | Actions |
|---|---|---|---|---|---|
| Loading… | |||||
Review submitted testimonials. Approve & publish to feature one on the public landing page — published testimonials are hidden while Beta / Invite-Only mode is on.
| Author | Rating | Testimonial | Status | Live | Date | Actions |
|---|---|---|---|---|---|---|
| Loading… | ||||||
AI flywheel
What the AI is used for across the product, and whether people keep its answers.
How much it is used
AI Runs
—
all apps, all time
Last 30 Days
—
runs across all apps
Accounts Using AI
—
with at least one run
Busiest App
—
most runs in the last 30 days
Whether its answers are kept
Four of the features that record what a person did with the answer. Every one is under Outcomes.
Canvas Layouts Kept
—
saved without a change
Receipts Kept
—
saved as the AI read them
Inbox Accepted
—
suggestions that were decided
Assistant Helpful
—
answers that were rated
AI Runs by App
All time
AI Runs per Month
Last 12 months, split by app
Where a person kept, changed, rated or threw away what the AI produced. A feature that is not listed here is counted under Usage by feature, but leaves nothing to learn from yet.
| Signal | Result | Detail |
|---|---|---|
| Click Refresh to load | ||
Every metered AI run, grouped by app. "Learns from" is what the product records about whether the answer was kept; a feature marked usage only is counted, and nothing more.
| Feature | Runs | Credits | Last 30d | Accounts | Last run | Learns from |
|---|---|---|---|---|---|---|
| Click Refresh to load | ||||||
Canvas layouts
The AI's duct layout compared with the design that was saved.
Total Events
—
AI layouts generated + saved
Accepted Unchanged
—
% users kept AI layout as-is
Avg Edit Distance
—
duct-slot changes per design
AI Violations
—
NCC violations in AI's first pass
Avg Room Count
—
rooms per design event
Events by Climate Zone
Designs captured per NCC zone
Accepted vs Edited (30d)
How often users keep the AI layout
AI Quality Over Time
Monthly: % accepted unchanged (green) vs avg NCC violations in the AI's first pass (red) — is the AI getting better?
Most Common Duct Sizes (Final Designs)
Top duct sizes across all saved designs — shows what users actually use
Fitting Patterns
How often designers add or remove each fitting relative to the layout engine's automatic placement. A high add-rate on the damper suggests making it a default; geometric fittings (elbows/tees) are routing necessities, not preferences.
| Fitting | Designs | Added in | Removed in | Median Δ |
|---|---|---|---|---|
| Click Refresh to load | ||||
| Date | Climate | Rooms | Sqm | L/s | Accepted? | Edit Dist | Top Duct (AI) | Top Duct (Final) |
|---|---|---|---|---|---|---|---|---|
| Click Refresh to load | ||||||||