Signal — Summary

Route guard: none. /summary is the only major route with no role wrapper (src/App.tsx:1131) — any user who can sign in to Signal can open it. Sign-in is Google OAuth restricted to the company domain. Every other guard in the app (TeamLeadRoute, AdminRoute, GandalfRoute, SauronRoute, MemberAllowedRoute, the Growth guards) redirects unauthorized users to /summary, making it the universal fallback destination.

Default route: the root path / redirects to the user's saved landing preference or /summary (src/App.tsx:1130). "Summary" is also the default entry in the pinned-views list (browser localStorage key signal-pinned-views).

Member tier (reduced experience): a "Member" is any signed-in user with none of the elevated role flags — not Team Lead, not Admin, not Gandalf, not Sauron, not Growth-allowed, not a Performance Radar viewer, and not a Growth access manager (src/context/AuthContext.tsx:634). Role flags come from Signal's own user records (the app_users table), resolved at sign-in; Growth capabilities are resolved by the backend from the growth-access grant tables. Members see the KPI tile values and the aggregate metric-over-time chart only: the filters bar, tile drill-downs, gross-profit bar and pie charts, the breakdown table, and the Excel export are all hidden (isMember checks throughout src/views/SummaryView.tsx). Members' sidebar is stripped to exactly two links: Summary and Employees (src/App.tsx:513).

Full experience: any non-Member (Team Lead and above, plus users holding any Growth capability) gets filters, click-to-drill tiles, breakdown table, and export.

How elevation is granted: role flags are set by administrators in Signal's General Access screen (/users, Gandalf-gated); Growth capabilities in the Growth Access screen (/growth/access). There is no Summary-specific flag.

MRR — monthly recurring revenue: Vena revenue from retainer contracts only, for accounts with financial activity in the month. Project revenue is excluded because it is one-time (per Rodolfo, code comment in src/context/DataContext.tsx). VABO excluded. Origin: Vena.

Total Revenue / In Contract Revenue — the tile is labeled "Total Revenue" when NetSuite data is available and no filter is active: the sum, over selected months, of NetSuite GL revenue (accounts 42100/43300/43400/43500/43550/43560 — code constant as of Jul 2026, server/netsuite.ts:178) for closed months with a positive figure, plus Vena revenue including VABO for the open month and for any closed month whose NetSuite financials are incomplete (non-positive figure — reversals only; those months get the tooltip "NetSuite excluded as financials are incomplete"). Subtitle states the exact basis: "NetSuite · Total Company", "NetSuite + In-Contract (open mo)", "NetSuite + In-Contract", "In-Contract + VABO (open mo)", or "In-Contract + VABO". A secondary line always shows the Vena "In Contract" figure (retainer + project, VABO excluded) for reconciliation. When a division/department filter is active, or NetSuite data is unavailable, the tile is labeled "In Contract Revenue" and is entirely Vena-based. Origin: NetSuite + Vena.

Gross Profit (MGP) — Monthly Gross Profit: Vena revenue minus third-party outsource cost, summed per row. Origin: Vena.

VABO — a distinct Vena revenue category kept out of every revenue/MGP rollup and surfaced on its own tile. Historical months come from the Vena contracts data; the current calendar month is overridden with Vena's latest VABO value (the contracts table lags the in-flight month). Single-month view shows a "Last Mo" comparison. Hidden whenever a filter is active (VABO cannot be cleanly attributed under a filter). The acronym's business expansion is not defined in the app repo. Origin: Vena.

Outsource Costs — monthly COGS: third-party outsourcing cost per Vena row. Origin: Vena.

Total Seats — unique (employee, role) seat assignments on accounts with Vena financial activity in the month. Seats originate in Nova platform assignment history, overridden by Signal's own team-assignment records where a client's team is managed in Signal. Origin: Nova + Signal's own records.

Active Clients — distinct client names with Vena financial activity (revenue, MGP, or outsource cost > 0) in the selected month(s); VABO-only rows excluded. Origin: Vena (activity) + Nova (client identity).

RPE — revenue per employee. Unfiltered view with NetSuite data: NetSuite total company revenue ÷ full-time headcount (subtitle "Total Co. Rev / FTE"). Unfiltered without NetSuite data: Vena revenue ÷ full-time headcount. Filtered: Vena revenue ÷ delivery employees for the filtered org (VABO stripped). Multi-month selections divide by the month count. Origin: NetSuite/Vena numerator, Nova denominator.

Retention Rate — client-level retention: a client counts as retained for a month if their churn_date (from Nova client records) is null or after that month's end; a client is retained if ANY of their accounts are retained. Rate = retained clients ÷ all clients in the filtered set. Point-in-time: months before a later churn still show the client as retained. The YTD secondary value averages client-level retention across all current-calendar-year months (available only after the background month-history load completes). Origin: Nova.

Full-Time Employees — active full-time headcount from Nova user records (no termination date, full-time flag, real company email domain, name sanity filters). Unfiltered: server count (1-hour cache); filtered: client-side count matching the Employees view. Origin: Nova.

Assigned Leads — employees holding lead seats on accounts with financial activity in the selected month(s) — the "delivery employees" definition shared with the drill-down list. Origin: Nova assignment records + Signal's own team-assignment overrides.

Delivery Employees (shown only when a filter is active) — total org headcount for the selected division/department per each person's Nova org profile, including part-time and contractors. Origin: Nova.

Retention badge colors (Breakdown table): green ≥ 80%, amber ≥ 60%, red below — code constants as of Jul 2026 (src/views/SummaryView.tsx:900).

Flag a data issue (explicit): every row in a tile drill-down has a flag icon that opens the Flag Issue modal (FlagIssueModal); submitting inserts a row into data_corrections in Signal's own records with status pending (submitDataCorrection(), src/services/supabase.ts:1539, direct from the browser). Side effects: admins review the flag in the Corrections view; the submitter can track it in My Submissions. Nothing on the Summary screen changes source data directly. Drill-downs (and therefore flagging) are unavailable to base-tier Members.

Usage telemetry (automatic): opening the view logs a page_view usage event with module summary into Signal's own usage records (signal_usage_events, via src/hooks/useUsageTracking.ts), which feed the Sauron-only Analytics view.

Everything else — division/department filters, Group By, chart metric selector, month selection, pinned views — is view state. Division/department filters are shared app-wide for the session (other views honor them); pinned views persist in browser localStorage.

Dual revenue basis is subtle. The Total Revenue and RPE tiles on the Summary view use NetSuite only on this view, only when no division/department filter is active, and only for closed months whose NetSuite figure is positive. The open calendar month always falls back to Vena revenue including VABO. A closed month whose NetSuite financials are incomplete (non-positive figure — reversal entries only, typical during the close window) is also excluded and falls back to Vena, with an "i" tooltip on the tile: "NetSuite excluded as financials are incomplete" (behavior added 2026-07-06, src/utils/nsRevenueSummary.ts). Which label ("Total Revenue" vs "In Contract Revenue") and subtitle appear depends on NetSuite data availability at view time.

Month-closed classification uses the server's clock, not the browser's: latestClosedMonth ships in the /api/netsuite-revenue payload, and the browser refetches it when the tab regains visibility (at most every 5 minutes), so two open tabs converge on the same figure for a just-closed month.

The trend chart is Vena-based even when the Total Revenue tile is NetSuite-based — the chart's Revenue series and the tile are not the same series and will not match for closed months.

Label/value mismatches in the grouped visuals (code as of staging @ 98df0c4): the Breakdown table column headed "Gross Profit" renders each group's Vena total revenue (metrics.totalRevenue), not MGP; the pie chart titled "Gross Profit Distribution" also plots total revenue; only the horizontal bar chart plots actual MGP. Likewise, in multi-month mode the Breakdown column headed "Avg Monthly" renders each group's average RPE. The Excel export is unaffected — it exports Revenue, Outsource Costs, and Gross Profit (MGP) as separate, correctly-labeled columns.

VABO tile disappears under any filter — by design (VABO cannot be attributed to a division/department), not a bug. RPE also drops VABO from its numerator whenever a filter is active. In multi-month mode the VABO tile shows an accumulated total ("Accum. VABO") while dollar tiles show per-month averages.

Multi-month mode changes tile semantics to per-month averages (subtitles say so, e.g. "Avg Monthly MGP (3 mo)") and removes the VABO "Last Mo" comparison.

Retention is point-in-time from churn_date — historical months never retroactively show later churns. The YTD retention secondary value and the exact tile/chart agreement depend on the background month-history load; numbers can visibly settle a few seconds after page load (the chart uses server aggregates until history finishes).

Retention badge thresholds (80% / 60%) and NetSuite GL account codes (42100/43300/43400/43500/43550/43560) are code constants as of Jul 2026 — changing either requires a deploy. Who owns keeping the GL code list in sync with Finance's chart of accounts is not defined in the app repo.

Division/department filter options are hardcoded in the frontend (ALL_DIVISIONS / ALL_DEPARTMENTS in src/utils/orgStructure.ts); the org structure changes periodically. The server also has a static divisions list (GET /api/divisions).

Freshness: the backend caches most reads 30–60 minutes (NetSuite revenue 30 min; headcount, roster, and client metadata 1 hour; months 30 min). The upstream pipeline cadences (Vena → warehouse, NetSuite → warehouse, Nova app → warehouse) are not defined in the app repo — figures are "as of the last pipeline run," not real-time.

What "VABO" stands for in business terms is not defined in the app repo — the code treats it as a distinct Vena revenue category, allocated per lead, excluded from revenue/MGP rollups.

Member-tier users see a much smaller screen (tiles + trend chart only), so two employees describing "the Summary page" may be describing different feature sets.

Manage Leads (/leads, Team Lead+): team assignments saved there (Signal's own team_assignments records) override the Nova-detected seats, which changes the Summary view's Assigned Leads count, Total Seats, and per-employee attribution.

Corrections (/corrections, Admin+) and My Submissions: flag-issue submissions from Summary drill-downs land in the corrections queue reviewed in Corrections; submitters track theirs in My Submissions.

Employees (/employees): the Delivery Employees tile deep-links there; headcount definitions are deliberately mirrored so the two screens agree. It is the only other view base-tier Members can reach.

Analytics, Client Profitability, KPI Targets, Divisional P&L, ETCR: share the same server-side Vena engine (server/vena-kpi-engine.ts) and/or the same frontend data spine (DataContext), so metric definitions (MGP, VABO handling, retention) are consistent by construction — with the deliberate exception of the NetSuite-based Total Revenue/RPE tiles, which exist only on Summary.

Every gated view redirects unauthorized users to /summary — it is the app-wide fallback.