People email sync
Control whether shareable email activity is saved to People records by default.
Check which workspace behavior, access rule, credential, usage signal, or data-model surface the control changes.
What People email sync is for
People email sync controls whether shareable email activity is persisted to People records by default for workspace members.
This setting affects customer memory. When enabled, relevant email activity can become part of the Person timeline that operators, Max, and workflows can reference.
What each control changes
Sync emails to People records by default turns the default persistence behavior on or off. Save applies the policy.
Use this deliberately. Enable it when email history should support customer context; disable or review policy elsewhere when the organization needs stricter boundaries.
Operational outcome
A good sync policy makes CRM memory more useful without surprising the team about what email context becomes visible.
Operational playbook
Use this page to identify what the control changes, which source context it uses, who owns the result, and where to verify it.
Use the page to identify the trigger, source data, owner, visible result, and review point before changing production behavior.
Best practices
Start with the operational job before changing configuration. Name the owner, define the trigger or source context, and decide how the result should be reviewed.
Start with one workflow, message, record update, or Max task before expanding. The team should know what changed, who owns it, and how to pause or adjust it.
Troubleshooting
If the result is wrong, debug in this order: source data, permissions, connected tools, required fields, workflow logs, then any generated output used later.
When debugging, open the related CRM record, Max activity, workflow run, or integration log first. Fix the source data or rule before adding more automation.
FAQs
What does People email sync control?
Control whether shareable email activity is saved to People records by default.
Who should use this page?
Workspace admins, implementation owners, and operators responsible for configuring access, account behavior, developer integrations, or the data model.
How should this page fit into onboarding?
Use it to understand the product surface, inspect real UI states, and connect the concept to daily operating workflows before configuring production behavior.
What should I verify before using this in production?
Verify ownership, permissions, source context, failure behavior, and the handoff path so teammates can trust what the system does next.