Membership (mirror)
Local Membership usage in KPIs & OKRs; shared definition in Core.
The shared definition and source fields are in Core / Membership. This page explains only usage in KPIs & OKRs.
Use and boundaries
Member, Business Unit and Position Held are real links. Membership # is a shared identifier across bases; Airtable record IDs are local to each base. Accountable and Observation links use this table. Member Display Name and Business Unit (Legal Name) are derived values. Access Level and Approval Limit are business attributes, not proof of enforced application permissions.
Locally used fields
Membership #, Membership ID, Member, Business Unit, Membership Status.
These are consumer labels and may differ from the source. Local operational links and derived values:
| Field | Storage | Local usage |
|---|---|---|
| Task | Linked records | Task |
| Task 2 | Linked records | Task |
| Milestone | Linked records | Milestone |
| Milestone 3 | Linked records | Milestone |
| Recurrence Configurations (Accountable) | Linked records | Recurrence Configuration |
| Observations (About) | Linked records | Observation |
| Business Unit (Legal Name) | Lookup | Business Unit → Legal Name |
| Metric Target | Linked records | Metric Target |
| Member Display Name | Formula | Derived locally. |
| Tags | Linked records | op:tags · local label; does not update Core |
Member Display Name uses ARRAYJOIN({Member}). The consumer still exposes Membership #, while current Core exposes Membership ID and Membership (Name). Check the source mapping before changing the key used by integrations.
Where to correct
Correct shared data in Core Record Types[Membership]. Adjust links to tasks, targets and other operational records here. Check the column mapping, refresh interval and write-back behavior in the sync settings before relying on them. Do not assume editing a mirror updates Core. See Maintain shared records.