Person in CRM
Local use of People in the CRM.
Shared definition and source fields.
Use the shared Person as the counterparty of Deals and Interactions: they link here through People°, and the inverse links are Deals (Counterparty) and Interactions (Counterparty). Intake Step supports CRM work. Search by email before requesting a new identity. Older descriptions promise two-way editing and automatic duplicate merging; the metadata does not verify those guarantees. The Cal.com integration creates People in Core and waits for the mirror.
People intake: name the person in the grid.
Local usage
| Field | Storage | Current configuration |
|---|---|---|
| Deals (Counterparty) | Linked records | Deal; inverse of People° |
| Interactions (Counterparty) | Linked records | Interaction; inverse of People° |
| Business Unit (from Memberships) | Lookup | Via Memberships → Business Unit |
| Intake Step | Formula | Calculated; see rules below. |
Local rules
Intake Step
IF(OR({Status} = "Proposed", {Status} = BLANK()),
IF({First Name*} = BLANK(), "Person - 1",
IF({Email} = BLANK(), "Person - 2", "")), "")Maintenance
Correct shared facts at their owning source and local links in CRM. A table name or field description alone does not verify sync direction, field mapping, refresh interval or API write support. Campaign has a separately verified contract; do not generalize it to the other mirrors.