Star ratings and optional comments submitted from the chat assistant (most recent first).

How well hybrid search is finding relevant documents — retrieval calls are logged automatically and this data feeds future knowledge-gap detection.

Filterable by advice category and advisor cohort/team — never by named individual advisor (that breakdown doesn't exist on this dashboard).

Weekly-ish snapshot of retrieval quality gaps: low-relevance queries, recurring low-feedback topics, stale KB pages, and sessions escalated to a human advisor. Generated on demand here, or by an external scheduled job hitting the same endpoint.

% of finalized cases tagged with more than one advice category, and the most common category pairings.

% of cases marked "Resolved" that have a new case for the same client within the window below. Client matching is by exact client reference text (the same convention Client History already uses) — typo or casing variants of the same client won't merge.

Casebook access and Team controls are temporarily removed from this view. Nothing about them changed server-side — existing per-advisor Casebook overrides and Team labels are untouched and still in effect, they're just not editable here for now. Case Note Access (6.8) controls View Saved Case Notes visibility: "Own cases only" (default) restricts an advisor to cases they created; "All cases" grants full visibility, same as admin/manager. Read-only — it never grants edit or delete rights on another advisor's case. Every change here is logged (who changed it, for whom, when), and so is every time an "All cases" advisor actually opens a case they didn't create. This has no effect on Client History, which stays open to every advisor regardless. Role (7.4) promotes/demotes between "user" (no admin-portal access) and "admin"/"manager" (both grant full access to this entire panel, including these controls). Changing it asks for confirmation first, is enforced server-side regardless of what the UI shows, and is logged the same way as everything else here. The system always blocks removing the last remaining active admin/manager account, so this panel can never lock everyone out of itself.

Every account is in one of three states. Active (default) — can log in normally. Deactivated (7.4/7.6, via the Status column) — login is revoked but fully reversible with Activate at any time; nothing the account created is touched, and its email stays reserved (nobody else can register it while the account merely sits deactivated). Deleted (7.6, via the separate red Delete Account button) — permanent. The account can never be reactivated, but its case notes, transcripts, and audit history are not erased: they remain exactly as they are, still showing the real advisor's email in Client History and View Saved Cases, because that email is recorded on each case record independently of the account itself. What Delete Account actually removes is narrower than it sounds — only the login credential and the email address on the account row, which is what frees that email for someone to register a new account with it. It requires typing the account's exact email to confirm, is admin-only, blocked for your own account and for the last remaining active admin/manager, and is logged the same way as everything else here — that log entry is never itself removable, so there's always a record an account existed and was deleted.

When an advisor rates a response poorly and provides a correction, it lands here as a candidate. Approving one adds it to that domain's system prompt as a "learn from this" example — no code change or deploy needed. Nothing here is used until you approve it.

Manually-curated local organisations (food banks, legal aid, mental health, housing charities, etc.) that advisors can be shown as referral suggestions after generating case notes. Higher priority shows first within a domain. Deactivated services are kept (never deleted) so past referral records stay meaningful.

AI response latency, LLM token cost, and knowledge base freshness. Latency/cost figures only reflect activity since this tracking shipped — they'll look sparse until enough data accumulates.

Proxy metric: a session left "active" for several hours is presumed abandoned/failed — an advisor who simply forgot to click "stop" would also count here.

Configure the sitemaps that will be discovered and scraped when knowledge base sync runs.

Refresh the knowledge base by re-scraping all configured URLs and updating the vector database. This process runs in the background and may take several minutes to complete.

Quickly scrape and index a single specific URL without running the full knowledge base sync.

Read-only reference — no new controls here, just what the other sections' controls do.

Refresh Knowledge Base re-scrapes every configured sitemap URL and updates the vector database incrementally. Reset & Resync Everything clears the existing index first — use only when the knowledge base needs a genuine full rebuild. Scrape Specific URL indexes a single page without running the full sync, useful right after a single source page changes.

The global CASEBOOK_INTEGRATION_ENABLED setting is the default for every advisor; per-advisor overrides and team labels are managed under Users & Roles, not here. The manual "Copy for Casebook" fallback always works regardless of this setting.