Back to the guides

PRACTICAL SOFTWARE GUIDE

Pipedrive email sync: review personal, team and conversation visibility

Treat mailbox access, CRM item access and conversation sharing as separate controls before connecting a real address.

SOURCE-BASED ANALYSIS · NO HANDS-ON RATING

Choose the account model before connecting

Pipedrive documents personal email accounts for an individual mailbox and team accounts for shared addresses used by multiple people. A personal inbox is private unless conversations are shared, while a team inbox can be available to selected team members. Neither choice replaces the visibility rules on the CRM item to which a conversation is linked.

Map audiences for a controlled pilot

Use synthetic contacts and non-sensitive messages to test a private personal conversation, a shared conversation linked to a deal and a message in a fictional shared sales mailbox. Record who should see each item before syncing. This procedure is a proposed pilot, not evidence that an inbox was connected.

FixtureMailbox ruleExpected viewer
Personal confidential notePrivateConnected user only
Deal handoff messageShared and linkedUsers who can access the linked item
Team sales enquiryTeam onlySelected team-mailbox members

Reconcile links rather than relying on subject lines

Email sync can link conversations to deals, leads, projects or contacts automatically or manually. Verify the actual linked item, owner and audience. A message visible on a linked record does not necessarily appear in another user's mailbox, and a shared mailbox does not automatically make every linked CRM record visible.

  1. Identify the mailbox owner and operational audience.
  2. Choose personal or team account intentionally.
  3. Set default and exception visibility rules.
  4. Send only synthetic pilot messages.
  5. Link each thread to the expected CRM item.
  6. Compare the view of the sender, a permitted colleague and an excluded user.
  7. Document disconnection and ownership-transfer steps.

Keep privacy and tracking explicit

If open tracking or notifications are enabled, review the organization's communications and privacy rules separately. Do not infer consent from feature availability. Accept the pilot when mailbox membership, conversation visibility and record access produce the written audience for every fixture.

Sources and verification

Official documentation checked on 2026-10-29. Worked examples are hypothetical planning exercises, not measured product benchmarks.

Continue your evaluation

Practical guides for this topic

Put your tools to work.

Need help choosing or setting up your tools? Tell Koldia what you want to improve.

Discuss your project