Shared Records & Sync Proposals

A contact can be shared from one space into another. When it is shared as a linked copy, the original space keeps the master, and your space holds a copy that stays in step with it — but never behind your back. Every change the owner makes arrives in your space as a proposal that somebody has to accept.

That is the whole design: an owner can update their record without your permission, and your copy does not change without yours.

Where to find it

ScreenWhere it livesWhat you need
Sync Proposals — /sync-proposalsthe sidebar, under Communication & integrationsPermission to review sync proposals

What a proposal looks like

Each waiting proposal names the contact, who proposed the change, and when. Beneath it is the difference — not the whole record, only what would change:

  • A changed field reads as from → to, so you can see the old value and the new one side by side.
  • Phones, emails and addresses read as a list of what would be added, updated and removed.
  • Custom fields are shown the same way as ordinary fields.

The two answers

ButtonWhat happens
Approvethe difference is applied to your copy
Rejectyour copy stays exactly as it is

Rejecting does not break the link and does not stop future proposals: the next change the owner makes arrives as a new proposal. You are declining this change, not the arrangement.

Nothing waiting

An empty queue is the normal state. Proposals only appear when an owner has actually changed a shared record.

Note
If the queue cannot be loaded, the page says so and offers Retry — it never spins indefinitely. A spinner that never ends is a bug; an error with a retry button is an answer.
Tip
Sharing a contact into another space, and the difference between a one-off copy and a linked copy, are explained on Contacts. For links between records inside one space — family ties, referrals, org structures — see Linking Records.