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
| Screen | Where it lives | What you need |
|---|---|---|
Sync Proposals — /sync-proposals | Settings → Communication & integrations → Sync Proposals | Permission to review sync proposals |
What a proposal looks like
Each waiting proposal is a card that names the contact, then Proposed by with who proposed the change and when. Beneath it is the difference — not the whole record, only what would change — as a small table with three columns, Field, Current and Proposed:
- A changed field shows your copy's value under Current and the owner's new value under Proposed, side by side.
- Phones, emails and addresses show, under Proposed, how many entries would be added (
+), updated (~) and removed (-), each followed by the entries themselves. - Custom fields are shown the same way as ordinary fields.
A long queue pages.
The two answers
| Button | What happens |
|---|---|
| Approve | the difference is applied to your copy: Proposal approved — your copy was updated. |
| Reject | after you confirm (Reject this proposal?), the proposed changes are discarded and your 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, and the page says No pending sync proposals. Proposals only appear when an owner has actually changed a shared record.