Feature Guides¶
Focused, per-feature guides for ClientVerse. Each page explains what a feature is, who it's for, how it works, and how to use it — and points to the deeper reference docs rather than repeating them. Read these when you want to understand or roll out a single capability; for end-to-end workflows see the User Guide, and for setup see the Admin Guide.
Two editions¶
ClientVerse ships in two packages (see conventions §1):
- ClientVerse Core — unlocked, namespace
clientverse, every client has it. The foundational CRM, BD, and relationship workflows. - ClientVerse Modules 🧩 — managed add-on, some clients. In 0.8.0 this is Dispatch (notifications/digests), Whitespace (revenue-opportunity scoring), AI (in-platform chat, AI Actions, email ingestion and data cleansing), Analytics (Power BI / Tableau embedding), Event Check-In (campaign check-in console and kiosk), and General (background automation, no objects or UI of its own). AI and Analytics arrived in 0.4.0 and ship off; Event Check-In is new in 0.8.0 and its components ship unplaced.
Default assumption on every page: the reader has Core only. Anything that needs Modules carries the 🧩 badge.
Compatibility note. Modules 0.8.0 requires Core 1.1.10 (declared dependency
ClientVerse Core Unlocked@1.1.10-2). This floor moved up from 1.1.7, so an org running Modules 0.4.0 quite happily may still be below it — upgrade Core before Modules. See../_package-facts/sync-report.md.
Core features¶
These ship with every client (applies_to: [core]).
| Feature | Guide | Roadmap | Status |
|---|---|---|---|
| Classification taxonomy & assignment | classification | Classification Picker (1.1) | Full guide |
| List Builder (static + dynamic lists) | list-builder | M1.1–M1.4 | Full guide |
| BD trip planning | trip-planning | — | Full guide |
Experience management (Experience__c, Experience_Holder__c) |
experience-management | — | Full guide |
| Collaborators & Walls (team sharing) | collaborator-wall | A4.7, A5.3 | Full guide |
| Pitch / Proposal Builder | pitch-proposal-builder | BD3.1 | Full guide |
Connections & relationship intelligence (Connection__c) |
connections | RI2.1/2.2 | Full guide |
| Client Locator | client-locator | L2.2 | Full guide |
| Rollups | rollups | P4.x | Full guide |
| Record merge | record-merge | — | Full guide |
| Client groups & account hierarchy | client-groups | Core | Full guide |
| Data quality & governance | data-quality-governance | A2.2, A2.3.1 | Full guide |
| Export | export | EXP | Full guide |
| Bulk operations & mass update | bulk-operations | A2.5 | Full guide |
| Recognition (awards, rankings, directories) | recognition | RECOG | Full guide |
Core 1.1.10 ships more features than this list covers at feature granularity — the engineering feature registry indexes 89 at the 1.1.10 build. The fifteen guides above are the customer-facing write-ups. For the authoritative object inventory see
../_package-facts/andobjects/core-key.yaml.The five gaps this index previously named — client groups, data quality and governance, export, bulk operations, and Recognition — are now written. The remaining known gaps are AI, Analytics and Event Check-In, all covered inline below; AI and Analytics are early access, and a full guide each is worth writing once their behaviour settles.
Module features 🧩¶
Optional — only clients with the ClientVerse Modules package have these
(applies_to: [modules]).
Dispatch — shipped¶
The data-driven notification and digest engine.
| Feature | Guide | Roadmap code |
|---|---|---|
| Dispatch (definitions, runs, delivery, subscriptions, sections, actions, ERM) | modules/dispatch | P3.3–P3.6, NCR 1–5 |
Whitespace — shipped¶
Revenue-opportunity scoring for untapped practice-area coverage.
| Feature | Guide | Roadmap code |
|---|---|---|
| Whitespace analysis & opportunity scoring | modules/whitespace | BD1.4 |
AI — shipped, early access¶
New in Modules 0.4.0. This supersedes the 0.3.0 guidance that described AI as foundation only and instructed writers to document it as "coming" — it is in the package now.
What ships: the CV AI Chat interface (a CV_AI_Chat tab and FlexiPage, backed by
CV_AI_Session__c and CV_AI_Session_Item__c), the AI Actions framework
(CV_AI_Action_Template__mdt), system prompt configuration, and per-provider adapter limits.
Modules 0.8.0 adds two capabilities, bringing the AI module to 13 objects, 4 LWCs and 8 permission sets:
- AI Email Ingestion. A lawyer forwards an email to a firm address; AI classifies it, matches real Contacts and Accounts, and proposes a Task or Event for a person to confirm. It never creates an Opportunity itself, and it ships switched off.
- AI Data Cleansing. AI suggests fixes to casing, phone formats and abbreviations, and fills
empty Account and Contact fields. Each suggestion is staged for a steward to accept or reject;
applying suggestions automatically is blocked by three separate settings. It needs the
CV_AI_Cleansing_*permission sets,AI_Cleansing_Setting__mdtturned on, andAICleansingSchedulerscheduled.
Setup for both is in the 1.1.10 release notes.
| Feature | Guide | Roadmap code |
|---|---|---|
| CV AI Chat + AI Actions | — | F-series, AI-CHAT |
| AI Email Ingestion, AI Data Cleansing | — | — |
Early access, and off by default. The chat is invisible to every user until CV_AI_Chat_User
is assigned, and engineering still tracks it as maturing. Document it as available, early
access, off by default — never as unavailable, and never as simply "shipped" without the
qualifier.
Two facts belong in any customer-facing description:
- Record access is enforced. Tool queries run through the Core named-query framework in
USER_MODE, so every row the model sees is scoped to the running user's CRUD, field-level security, and record sharing. The assistant cannot reach a record the user could not open. - Firm data goes to a third-party provider. Queries and their results are sent to Anthropic or OpenAI, and prompt-injection hardening is explicitly incomplete at this stage. For a law firm that is a general-counsel decision, not a configuration step.
Detail: objects/ai.yaml,
Admin Guide §13–§14.
Analytics — shipped, early access¶
Also new in 0.4.0, and likewise supersedes the "not present" note that stood through 0.3.0.
Components embed Tableau views and Power BI reports inside ClientVerse screen flows and
Lightning pages, so the firm's existing dashboards appear in the workflow rather than a separate
tool. Record context is passed in as filters mapped through a custom property editor, and Tableau
mark selections flow back into flow variables. Six LWCs plus CV_BI_Connection__mdt.
| Feature | Guide | Roadmap code |
|---|---|---|
| Power BI & Tableau embedding | — | P2.8.3, P2.9.1 |
Early access, and off by default — gated behind CV_BI_Visualization. Each platform's own
permissions and row-level security still apply, so a user who can open the ClientVerse page may
still be unable to render the dashboard inside it. Connections double as an embed host
allowlist: content whose host does not match an active connection is refused.
Detail: objects/analytics.yaml.
Event Check-In — shipped, components unplaced¶
New in Modules 0.8.0.
- A staff console on the Campaign: roster, search, tap to check in, guest count, and CLE check-out.
- A self-service kiosk.
- De-duplication of walk-ins, and an email to the sponsor when a guest arrives.
- Close Attendance, which marks no-shows.
| Feature | Guide | Roadmap code |
|---|---|---|
| Event Check-In (console, kiosk, Close Attendance) | — | — |
None of the three components is placed on a page. An admin adds cvEventCheckInConsole to the
Campaign page, creates an App Page for cvEventCheckInKiosk, and creates a quick action for
cvEventCloseAttendance. Access comes through the CV_Event_Check_In_User_Access,
CV_Event_Check_In_Admin_Access and CV_Event_Check_In_Kiosk_Access permission-set groups. Full
setup is in the
1.1.10 release notes.
How these pages are organized¶
- Core feature guides live under
core/and open with no badge. - Module guides live under
modules/, useapplies_to: [modules], and open with the 🧩 badge. - Every page cites object/field facts from
../_package-facts/and links the field-level reference in../../data-model/— it never duplicates them.