Use Gmail in Tsumira
Your Gmail address, close to your customer work.
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 identity
Use the account for the mailbox you want to connect.
Your organization must allow this connection.
Work with the address your customers already know.
A connected Gmail address brings correspondence into the same working environment as your customers and projects. You can read the exchange and prepare the next answer without treating the account as a new address for customers to learn. Choose personal ownership or shared team access before connecting. The Google authorization route is available only when configured and allowed for the actual account.
Connect the right account
Choose the address to connect and sign in to the matching Google account. Tsumira checks that the verified address returned by Google matches the mailbox you selected. This matters when several Google accounts are open in the browser. A personal inbox remains owner-only; a shared address follows explicit team grants. Review the intended account instead of accepting whichever identity appears first.
How will this address be used?
Choose the account kind before connecting.
Only you can open this mailbox.
Choose who reads, replies or manages.
Review access in Google
Read the permission request in Google and confirm that the account and requested mail access fit your purpose. This connection serves email; it does not silently enable every Google product. Your company may need to allow the application before authorization succeeds. If access is refused, clarify the permitted route with the responsible administrator rather than assuming the sign-in screen guarantees a working mailbox.
Review the Google permission
The connection requests access to the mail account.
Check the account and the permission before continuing in Google.
Reconnect the same mailbox
If the continuing Google authorization is refused, use the explicit reconnect action for the same address. Your existing mailbox, folders and conversation history remain. Do not create another account simply to bypass the recovery step. After reconnecting, verify that receiving and sending work again. The responsible person should know how to recognize the account status and coordinate support if the customer address is temporarily interrupted.
Reconnect your Google mailbox
Google has refused the continuing authorization.
Your mailbox, folders and history remain.
A concrete workflow
Check availability
Confirm configured access and organization approval for the real account.
Choose purpose
Select personal or shared and the correct address.
Authorize
Review the Google identity and complete the permitted flow.
Verify operation
Test receive, send and future reconnect responsibility.
An illustrative working example
Illustrative scenario: a Workspace team address
A company wants a Workspace service mailbox in Tsumira. Its administrator first confirms that the organization permits the configured application and the intended user. The team chooses shared access, authorizes the correct address and tests incoming and outgoing mail. When continuing authorization is later refused, the responsible person reconnects the same mailbox. Colleagues check recovery rather than creating duplicate accounts or assuming a provider sign-in removes mailbox permission rules.
Questions about this topic
Is the Google button always available?
No. It depends on configuration and provider-side availability and approval.
Why can Google require reconnection?
Authorization can be revoked or refused under provider or organization policy. Testing applications can have short-lived refresh access. Configuration and provider verification determine availability; reconnect the same mailbox when requested.
Do I lose history when reconnecting?
The reconnect flow uses the same mailbox, preserving its folders and history. Confirm the intended account rather than adding a replacement.
Does this enable every Google product?
No. This page concerns mail authorization. It does not promise Drive, Calendar or document synchronization.
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: Test the intended Gmail identity, requested permission and explicit reconnect of the same mailbox.
Google Drive
Application concept: Plan a separate review of file-sharing needs; mail authorization must not be treated as an existing Drive connection.
Microsoft Teams
Application concept: Prepare an internal Teams handover naming who checks company approval and restores a refused Google connection.