Skip to content

Data Admin

The class for data administrators — the people who keep ClientVerse data trustworthy by working the CV Admin app. This is not Salesforce system administration (configuration, permissions, deployments — that's Salesforce Trailhead). It's the day-to-day data-stewardship workflow.

Backbone guide: CV Admin (data quality, ERM oversight) and CV Experience (the review experience).

Objectives

By the end you can: - Read the data-admin dashboards and spot data-quality issues. - Understand the ERM sync process — how contacts and companies are harvested from Outlook email and flow into the review queue. - Work the contacts-under-review queue: Promote, Mark Private, Delete, or Tag. - Carry out the routine data-management tasks that keep records clean.

Prerequisites

ClientVerse Introduction, and a Data Administrator (CV Admin app) permission set.

Agenda

  1. Orientation — the CV Admin app, the data-admin home, and where data comes from: clients via the financial-system integration, ERM-harvested contacts and companies from Outlook email, plus events, opportunities, and migration.
  2. Data-admin dashboards — read the Data Quality scoring (per-object 0–100, 12-week trend, threshold-breach table); recognize a degradation and who's alerted. (Backbone: CV Admin guide §3.)
  3. The ERM sync process — how Experience/Relationship Management surfaces newly discovered contacts; Engagement Level (frequency/recency of email) on the relationship tables.
  4. Reviewing contacts under review — the heart of the role. From the review queue, decide each contact:
  5. Promote (make active), Mark Private, Delete (noise), or Tag.
  6. Use subscription management and token-based email actions to work efficiently. (Backbone: CV Experience guide; feature cv-core/docs/features/erm-contact-review.md.)
  7. Other data-management tasks — duplicate review/merge, classification upkeep, and using the Support Ticket button to escalate locked actions (e.g. adding companies, which only the CRM team can do).

Hands-on (homework)

  1. Open the data-admin dashboard; identify the object with the lowest quality score.
  2. In the review queue, Promote one contact, Mark another Private, and Tag a third.
  3. Find a likely duplicate and note how you'd request a merge.
  4. Log a Support Ticket for an action you're locked out of.

You're ready when…

You can keep the review queue clear, read the data-quality dashboard to catch a dip early, and explain where each record came from and who can change what.