Why this matters
A deal record without the email thread is a summary written by the least reliable narrator available, memory. With sync on, anyone picking up a deal reads the actual conversation. Handovers stop losing context, managers coach from reality, and the eternal question of who promised what gets answered by scrolling instead of arguing.
The risk is equally concrete. Full inbox sync means every mail lands in the CRM, and with shared visibility that includes the salary discussion with HR and the recruiter thread. One privacy incident is enough to make the whole team quietly disconnect their mailboxes, and then you are worse off than before. The setup below prevents exactly that.
The design decisions that matter
Decision one: full sync or selective. Pipedrive can sync the whole mailbox or only chosen labels and folders. For most teams the right answer is a label called CRM that reps apply to customer threads. Nothing private ever syncs, because nothing syncs without the label. The cost is one habit. The alternative is trusting every future email to be safe to share.
Decision two: default visibility. Synced mail can default to shared or private. Choose shared. A CRM full of private emails defeats the purpose, and reps can still mark the rare sensitive thread private by hand. Write both rules into a one-page policy the team has actually seen, which also keeps you honest under GDPR.
Decision three: group inboxes. Addresses like sales@ or info@ should be connected by the person who owns triage, or routed through the lead inbox instead. Two people syncing the same shared mailbox produces duplicate threads on every deal.
Decision four: tracking. Open and click tracking is per user and off by default is the safer European posture. Decide it company-wide rather than leaving it to taste, and put the decision in the same policy page.
A worked example
The rollout we run for a ten-person sales team, in order, in one week.
| Day | Step | Who |
|---|---|---|
| Monday | Policy agreed: selective sync on the CRM label, shared by default, tracking off | Sales lead |
| Monday | Two pilot users connect, sync history set to three months back | Pilots |
| Wednesday | Pilot review: spot-check twenty synced threads for anything that should not be there | Sales lead |
| Thursday | Whole team connects against the checklist, labels their open threads | Everyone |
| Friday | Connection check: every account green, every open deal shows its thread | Admin |
The pilot step earns its place every single time. In one rollout it caught a rep whose label had been auto-applied by a mail rule to the entire inbox. Two days of pilot beats one apology to the whole company.
Common mistakes
Half-team sync is the sneakiest one. Six reps sync, four do not, and every report or handover that leans on email history is now unreliable in a way nobody can see. Sync is a team decision. Make connection part of onboarding and check it in the monthly hygiene routine.
Second, full sync with shared default and no policy. This is the configuration that ends with a private email on a shared screen in a sales meeting. It is entirely avoidable and we still find it in most accounts we rescue.
Third, replying from outside. A rep who answers from their phone's mail app without the label breaks the thread's CRM trail. Selective sync needs the habit on every device, which is a training point, not a technical one.
Maintenance
Monthly: check every user's connection status and chase the red ones the same day. Also skim ten random synced threads for policy fit, thirty seconds each.
Quarterly: revisit the visibility policy with the team, especially after new joiners, and confirm mail rules have not started auto-labelling. Sync is also a dependency for the automations that send templated email, so a quarterly test send belongs in the same routine. Ten minutes, four times a year, and the highest-value switch in the account stays trustworthy.