Positions table: mapping gap
Local use of Positions in the CRM.
Shared definition and source fields.
Despite its name, this table has the same field shape as Team: Parent Organization, Classification Term, Departments, Head Membership, Members and Positions. Do not treat it as the canonical Position reference or merge it with bds:position by name. Its source mapping needs confirmation. Compare the Team definition while investigating; this is a structural observation, not proof of synchronization.
Local usage
Tags was added on 2026-10-22 by the Universal Tags rollout. It is an optional local classification from the shared catalog; it does not grant access, create tasks, change status or enroll a campaign, and it never writes back to the source.
| Field | Storage | Current configuration |
|---|---|---|
| Tags | Linked records | Tags; Multiple-record picker |
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.