Skip to content

CV Admin — Administrator Guide

CV Admin is the control room: installing and seeding the package, governing the classification taxonomy, monitoring data quality, managing sharing and notifications, and running the engines (rollups, dispatch) that the other apps depend on. If CV Lawyer is about consuming intelligence, CV Admin is about keeping it trustworthy.

Who uses it: CRM administrators and data managers.

1. Installation & setup

  1. Pre-installation — work through the cv-core/docs/guides/cv-core-pre-installation-guide.md (org prerequisites and package dependencies; Core installs before Modules).
  2. Seed required records — after install, open the Setup Checklist card on the CV Admin Home page. It seeds required records (e.g. Notification Templates) into the org, driven by CV_SeedDataConfig__mdt records that map each step to a Static Resource of seed JSON. Run steps individually or all at once; the card shows live status, last-run time, and created/skipped counts. Re-running is safe — existing records are detected by a unique field and skipped.
  3. Add a new setup step by dropping a CV_SeedData_<Functionality>.json static resource and a matching CV_SeedDataConfig__mdt record — no code changes.
  4. Feature: cv-core/docs/features/admin-setup-checklist.md.

2. Classification & taxonomy governance

The Classification Hierarchy is the firm's taxonomy for accounts, contacts, opportunities, campaigns, and projects. Records are auto-classified on create/update via object triggers; admins maintain the tree, assignment rules, and audit history through a tree-editing UI.

  • Govern the taxonomy centrally so segmentation and reporting stay consistent.
  • Feature: cv-core/docs/features/classification-hierarchy.md. Process: Business Process Library §3.14 (Taxonomy & Classification Governance).

3. Data quality

Two systems keep data clean:

  • Data Quality Monitoring — a nightly batch scores Contact, Account, and Opportunity on a weighted 0–100 scale (field completion, activity recency, open duplicates), snapshots per object per run, and shows per-object gauges, a 12-week trend, and a threshold-breach table on a native dashboard. When a score drops below a per-object minimum (Contact 75, Account 80) or falls more than the configured points week-over-week, in-app + email alerts fire to the Data Manager audience. Weights and thresholds are 100% custom-metadata driven — re-weight or change recipients without code (weights are enforced to total 100). (cv-core/docs/features/data-quality-monitoring.md)
  • Record-type integrity — Contact RecordTypes stay in sync with their parent Account's RecordType automatically; a configurable bypass lets migrations and integrations skip the sync. (cv-core/docs/features/data-integrity-recordtype-sync.md)
  • Process: Business Process Library §3.13 (Data Quality & Administration).

4. Sharing & access

Collaborators & Wall sharing provides dynamic record access: users create Collaborators (named groups), associate records to a Wall, and Wall members gain access automatically through sharing rules. An initial batch sync plus ongoing queueable sync keep access current as membership changes. Use this instead of hand-managed sharing. (cv-core/docs/features/collaborator-wall-sharing.md)

5. Notifications (Dispatch) · 🧩 Modules

🧩 Dispatch is a ClientVerse Modules feature (the largest Modules module, 12 objects). Core-only firms won't have it; alerts that rely on it (below) require the Modules package.

The Dispatch framework is the firm's notification engine: admins configure Dispatch Definitions with SOQL templates, and scheduled jobs generate run items delivered as digest emails or in-app notifications. It backs alerts across ERM review, data quality, market research, and more — configure once, reuse everywhere. (cv-core/docs/features/dispatch-notification-framework.md)

6. Rollups

The Rollups Engine computes summary values across related records. Admins define rollup definitions in a UI (parent/child objects, field, aggregation type — COUNT, SUM, MIN, MAX, AVG, FIRST, LAST, CONCAT, CONCAT_DISTINCT), optionally scoped by filter records. The engine runs on schedule or on-demand, and a monitoring dashboard surfaces execution status and errors. Up to 20 active rollups per child object. (cv-core/docs/features/rollups-engine.md)

7. Record operations

  • Merge — a generic deep-merge service merges a source record into a target for any object, reparenting all child records and consolidating fields. Small objects merge synchronously; large ones defer to a queueable. Exposed as an invocable action for use in flows. (cv-core/docs/features/merge-records.md)
  • Layouts & record pages — every in-scope object carries exactly one CV-prefixed layout and one CV record page per record type, with no empty shells. Keep new objects consistent with this standard. (cv-core/docs/features/cv-layout-record-page-normalization.md)

8. ERM review queue

CV Admin owns the oversight side of Experience Review Management — the admin queue, subscription management, and the dispatch digests that drive reviewer notifications. Setup and QA detail live with the code in cv-core/docs/dispatch/ (architecture guide, QA walkthrough, Experience-site setup). See the CV Experience guide for the reviewer experience.

Integrations note

The MCAE marketing-integration spine (transport layer) landed in Core in the 1.1.6 line as the foundation for marketing automation — say MCAE, never "Pardot." Integration configuration is documented separately under ../integrations/.

  • Product guides: BD · Lawyer · Marketing · Experience
  • ../../data-model/CLAUDE.md — the objects behind these features.
  • ../../release-notes/CLAUDE.md — what changed, per release.