Email and connected mailboxes
Work with customer email without losing the mailbox's access boundaries.
Connect personal or shared mailboxes, read conversations, prepare replies and use customer context with deliberate access and sending authority.
An inbox needs both a working connection and a clear audience.
Tsumira Mail brings connected email into the business workspace. It distinguishes an individual's personal mailbox from a shared team mailbox and keeps reading, responding and management rights separate. The email account still requires a supported working connection and the background mail service. A mailbox interface alone does not prove that synchronization or delivery is healthy.
Explore each function
See what each capability does, how it works and where it fits into your team’s workflow.
Connect email accounts
Connect supported IMAP and SMTP mailboxes with the account type, credentials and provider requirements appropriate to your organization.
Shared team inboxes
Connect a shared address and choose who may read, respond or manage it while role restrictions continue to govern sending and changes.
Personal email inboxes
Read your connected personal mailbox inside Tsumira, with owner-only access and deliberate sharing of selected conversations when CRM context is needed.
Email conversations and folders
Follow threaded messages, inspect participants and attachments, and organize permitted mail without confusing a folder or flag with ownership of the next action.
Write and send email
Compose messages with the appropriate sender, recipients, attachments and signature, with an eight-second undo window before sending is claimed.
Email signatures and company templates
Create personal signatures, use company templates and choose account or identity-specific defaults for new messages and replies.
Connect email and CRM records
Match conversation participants to CRM contacts and companies, maintain their details and explicitly share or withdraw a chosen customer thread.
Use Gmail in Tsumira
Connect your Gmail or Google Workspace mailbox, read conversations and prepare replies in Tsumira while keeping the chosen personal or shared access rules.
Connect the right kind of account.
Use supported IMAP and SMTP account settings, with the provider's permitted password or app-password method where appropriate. A configured Google OAuth path can connect Gmail or Google Workspace accounts, subject to provider policy and verification. Choose personal or shared deliberately before adding an account; account kind determines privacy and collaboration rather than simply changing the label in the sidebar.
- Personal and shared accounts with verified connection setup
Keep personal privacy and team access distinct.
A personal mailbox is for its owner alone; company administrators do not receive an override. Shared mailboxes use explicit grants with read, respond and manage levels. Role restrictions remain in place, so a viewer cannot send even if a mailbox grant would otherwise suggest broad access. Sending also requires an active human seat rather than a bot identity.
- Owner-only personal mail and role-aware shared grants
Use conversations, signatures and customer context deliberately.
Read threads and folders, prepare messages and maintain sending identities and signatures. When CRM is available, a conversation can be connected to the relevant customer record through the dedicated workflow. Review recipients, content and attachments before sending. AI can assist with a draft but does not remove outward confirmation or grant permission to expose a private personal conversation to the team.
- Reviewed replies and optional CRM context
A concrete workflow
Choose the mailbox
Decide whether this address is personal or shared.
Connect
Verify supported provider settings and the actual account status.
Review access
Test who may read, respond, send and manage the account.
Work in context
Review the conversation and customer relationship before replying.
An illustrative working example
Illustrative scenario: a customer service address
A company connects a shared customer address and grants selected colleagues the appropriate level. One person reads a request, checks the related customer and prepares a reply from the correct identity. A viewer can inspect the conversation but cannot send. The pilot verifies receipt, reply and access with the real setup, while personal inboxes remain owner-only. If the provider connection fails, the team resolves its status instead of assuming the presence of a draft means the customer received mail.
Questions about this topic
Can administrators read personal inboxes?
No. Personal mailbox privacy is owner-only, including against other company administrators and the tenant owner.
Can viewers send from a shared inbox?
No. Role-level outbound restrictions still apply even when a shared mailbox grant exists. Sending requires suitable authority and a human seat.
Is Google connection always enabled?
No. It requires configured OAuth and provider-side policy and verification conditions. Check availability with the actual account before adopting the flow.
Does AI send mail on its own?
Drafting does not remove confirmation or permissions. Review outward actions; a bot identity does not gain a mailbox sending seat.
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: Plan use of an eligible Gmail address with deliberate personal or shared ownership and a real receive-and-send test.
Outlook
Application concept: Review the Outlook account's permitted connection method and team access before assuming compatibility.
HubSpot
Application concept: Identify the customer conversation relevant to a HubSpot handover without publishing an entire personal inbox.