Personal email inboxes
Keep personal correspondence with the person it belongs to.
Read your connected personal mailbox inside Tsumira, with owner-only access and deliberate sharing of selected conversations when CRM context is needed.
Your mailbox stays personal
An administrator role does not open another person's personal mail.
A personal address is not automatically a company-wide archive.
People often need their own correspondence close to project and customer work without making every message visible to colleagues. A personal mailbox offers that separation. It is owned by the connected person, not treated as another shared queue. Decide whether the address is genuinely personal before connection; a central service address usually needs the separate shared-mailbox model instead.
Maintain owner-only access, including against administrators.
Personal mailbox access belongs to its owner. Company administrators and the tenant owner do not receive a general override to read somebody else's personal mail. The same boundary matters when choosing account settings and evaluating team adoption. Do not describe an administrator role as permission to browse all connected accounts or use personal mail as a substitute for a shared handover address.
- Owner-only mail without an administrator reading override
Read and reply through a working account connection.
Use the mailbox's threads and folders to follow the conversation and prepare the next reply from the appropriate sender identity. Incoming access and outgoing sending depend on a working provider connection and background mail processing. Check account status if correspondence stops arriving. A saved draft is useful working material, but it does not prove that a customer received a message.
Share this conversation with CRM?
People who may read this record can then read the thread.
The rest of your personal inbox stays private.
Share a relevant thread as a separate decision.
When CRM is available and your permissions allow it, a chosen conversation can be shared with the relevant contact or company record. This is deliberate publication of that thread to its permitted business context, not a transfer of the entire personal inbox. Review the conversation's content before sharing. Address matching alone does not mean every private exchange should become visible to the customer team.
- Selected thread sharing instead of whole-inbox disclosure
A concrete workflow
Choose personal
Confirm that the address belongs to one person's work.
Verify connection
Test incoming and outgoing access with the actual provider.
Work privately
Read correspondence and review the next response.
Share deliberately
Expose only the reviewed conversation needed for the customer record.
An illustrative working example
Illustrative scenario: a consultant's client exchange
A consultant receives scheduling details and a substantive project decision in a personal account. The inbox remains private. The consultant reviews the relevant decision thread and shares it with the appropriate CRM record so authorized colleagues can understand the decision. Other correspondence stays outside that disclosure. During rollout the team tests both sides: a colleague can see the selected customer conversation, while an administrator cannot simply open the consultant's personal inbox.
Questions about this topic
Can company administrators open my personal inbox?
No. Personal mailbox access is owner-only. An administrator role does not bypass that privacy boundary.
Does connecting CRM expose all personal mail?
No. A selected conversation must be shared deliberately through the permitted workflow. The personal inbox is not published wholesale.
Should a shared support address be personal?
Use the shared model when several colleagues need deliberate access levels. Personal mail is not a team delegation mechanism.
Does a draft mean the email was delivered?
No. Provider connection, sending and delivery are separate from preparing content. Inspect actual status before following up.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Gmail
Application concept: Keep personal Gmail ownership separate from any chosen customer-thread disclosure to colleagues.
Outlook
Application concept: Plan the use of a personal Outlook address without assuming administrators can inspect all correspondence.
Salesforce
Application concept: Identify one reviewed exchange for a Salesforce-related customer handover while other personal mail stays private.