People email sync
Control whether shareable email activity is saved to People records by default.
Use this settings state to understand which workspace behavior, access rule, credential, usage signal, or data-model surface the control changes.
Learn the system by following the product states.
Use the screenshots as the primary map: start with the full context, trace the connected workflow, inspect the focused UI, then compare against the completed operating state.
Visible controlAccess or policyOperational effectUse this settings state to understand which workspace behavior, access rule, credential, usage signal, or data-model surface the control changes.
Summary
Control whether shareable email activity is saved to People records by default.
Concepts covered
Step breakdown
- Open People email syncStart in the People email sync section of the Admin control center.
- Inspect the real controlsIdentify the visible fields, buttons, switches, tables, and menus before changing configuration.
- Connect the setting to operationsUnderstand which user access, customer memory, developer access, usage, billing, or data-model behavior this setting affects.
What this screen does
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 People email sync as part of the Frontline Admin People email sync operating loop: inspect the current product state, confirm the source context, and decide what should happen next.
The goal is not to memorize screens. The goal is to understand how the product surface supports repeatable work, AI assistance, and accountable handoff.
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.
Prefer narrow, inspectable setups over broad automation. Teammates should be able to explain why the system took an action from the visible product state.
Troubleshooting
If the result does not match expectation, check the source context first, then permissions, connected integrations, required fields, workflow logs, and any AI-generated output used by downstream steps.
When in doubt, compare the latest product state with the related record, activity, or workflow execution so debugging starts from evidence rather than guesswork.
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.