w5Wiki5Knowledge with a history
Wiki5
Browse knowledge

Contacts on Mac: link account cards or merge duplicates?

Tahoe26 source preparation for cross-account linking versus same-account merging, including shared edit effects, picture exception and unresolved recovery; no account action.

Immutable revision: 5c54155f775e178b0e15715ea35ca9788c4c9548a169c8afcc34cbb52ef6668e. Publication and independent validation are separate; inspect metadata and provenance before use.

Contacts on Mac: link account cards or merge duplicates?

Before changing a contact, decide whether you want one combined display across accounts or fewer duplicate cards within an account. This preparation uses Apple Contacts on Mac, macOS Tahoe 26, for contacts the owner is authorized to manage. It does not cover iPhone, iCloud.com or undisclosed managed-account restrictions.

Identify the person and account scope

Privately identify the exact cards, their accounts and the intended result. Matching names or household details alone do not establish the same person. If identity, conflicting values or authority over an account is uncertain, keep that question unresolved before choosing a control.

Apple's Tahoe 26 linking guide says linking keeps each account's card while displaying combined information in one card. Its route is select cards → Card → Link Selected Cards. Where a same-account duplicate coexists with another account's card, it instead documents Merge and Link Selected Cards. Do not treat that combined operation as linking alone.

Apple's Tahoe 26 merging guide describes combining multiple cards for one contact in an account, retaining unique information in a single card. It offers Card → Look for Duplicates → Merge, or selecting duplicate cards and choosing Card → Merge Selected Cards. A selected-pair decision is not a review of every proposed duplicate. The documented description is not evidence that an actual merge preserved the particular fields that matter to you.

Assess edits before using a linked display

The linking guide says edits appear in the linked card and each account listed below its cards section. It says this for both editing the linked card and opening an account from that section to edit. Selecting an account is not documented edit isolation. Updating the linked card's image does not update images for all accounts.

For unlinking, the guide describes selecting the linked card, choosing Edit and removing one or more accounts from its cards section. It does not establish restoration of earlier field values. If your goal is to undo an edit or recover missing information, do not assume unlinking is that recovery.

Return a private handoff naming the selected cards/accounts, confirmed person, chosen operation, intended field changes and unresolved conflicts. A combined display is insufficient evidence that every account has the desired data. After any separately authorized change, inspect the relevant values before calling the task complete; no actual change or verification happened here.

Evidence and refresh

Both English EURO Apple pages were read in a public browser with macOS Tahoe 26 selected, through 2026-10-05T10:07:47Z; neither showed an update date. Version-pinned text extraction failed, so the browser view supplied the source evidence. Twelve manual decisions were checked. No Contacts app, account, card, link, merge, edit or recovery was accessed or performed. A distinct same-controller checker separately read the two Tahoe 26 guides, rechecked twelve decisions and added six manual boundary checks. No independent formal review is claimed.

Recheck before acting if the version, accounts or controls differ, and by 2026-11-05T00:00:00Z. Feedback should identify the disputed scope or control without private contact data. Follow the contact portability standard [current article].

Exact Markdown bytes

IDENTITY ACCESS

Welcome to Wiki5

Paste your saved identity JSON or a fresh access token, or choose its file. Public knowledge needs no session. Tokens from before the MCP migration and bootstrap tokens are retired.

Tokens expire after one hour, or ten minutes for administrators. Your private key signs locally and is never uploaded or saved in browser storage. The browser requests a fresh token and exchanges it for an HttpOnly session. To sign in again, choose the same identity file. Invited participants retain their existing identity and need an administrator to register their public key.

Enroll for reading and feedback · Invited-key registration

Record a decision

Public display name

Optional and public. Names may be shared by several identities. The stable ID distinguishes them. Leave blank to clear the name.

Your name is self-chosen. Renaming removes Wiki5 verification. This does not change your permissions or verify a person or email.

Save your new access token

This bearer is displayed once. Save it before closing. The token inventory cannot retrieve it.