Connect email accounts
Establish a working connection before treating the inbox as ready.
Connect supported IMAP and SMTP mailboxes with the account type, credentials and provider requirements appropriate to your organization.
How will this address be used?
Choose the account kind before connecting.
Only you can open this mailbox.
Choose who reads, replies or manages.
A saved account is not the same as verified mail access.
Mail account setup establishes how Tsumira reaches a real mailbox. Both incoming and outgoing access matter to a usable workflow. The account must satisfy the provider's authentication and secure-connection rules, and the background mail service must process it. Check actual account status rather than assuming a completed form means messages can already be received or sent.
Choose personal or shared before connecting.
A personal mailbox belongs to its owner alone, while a shared mailbox is managed for team access through explicit grants. Choose according to the address's operational role. Do not connect a private account as shared merely for convenience. A team address also needs a clear person responsible for settings, provider changes and reviewing who may use it.
- Purpose-driven personal or shared account setup
Verify the supported connection method.
Use the supported incoming and outgoing provider settings and the allowed password or app-password path where available. Google mail can use the separately configured OAuth flow. Provider policies may refuse a method even when the address and password seem correct. Do not bypass certificate failures or assume every enterprise authentication mode is covered; test the actual account requirements.
Check incoming and outgoing mail
A saved account is not yet a verified connection.
Use account status to guide recovery.
After connection, verification checks the account. A refused login, secure-connection failure or unreachable service needs the appropriate correction rather than repeated blind retries. Pause, resume or reconnect deliberately through account management. A disconnected account is not automatically revived. Review the real receive-and-send flow after changes before returning the mailbox to normal team use.
- Account lifecycle with explicit recovery actions
A concrete workflow
Decide kind
Identify the address's personal or shared purpose and owner.
Configure
Use the provider's supported connection and authentication settings.
Verify
Check actual account status and the incoming and outgoing flow.
Maintain
Review access and connection health when people or provider policies change.
An illustrative working example
Illustrative scenario: connecting a new team address
An administrator connects a service address as shared, verifies the provider requirements and assigns a responsible manager. The first account check reveals a provider-side authentication restriction. The team fixes the permitted method rather than continuing to send blind retries. After verification, selected colleagues test receipt and response. The pilot records who handles future reconnects and confirms that a readable inbox is not by itself evidence that outgoing delivery works.
Questions about this topic
Can every provider be connected automatically?
No universal compatibility is claimed. Check supported IMAP/SMTP settings, secure access and the provider's actual authentication policy.
Can I use an app password?
Where the provider permits the supported password path, yes. Some organizations restrict it and may require an available OAuth method instead.
Does the account automatically reconnect after disconnection?
No. Reconnection is deliberate. Check ownership, permission and the reason for disconnection before restoring the account's operation.
Should I ignore a certificate error?
No. Correct the server name or provider certificate issue. A failed secure connection should not be treated as a working mail setup.
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: Check the actual Gmail account's available authorization route before connecting the intended address.
Outlook
Application concept: Verify supported incoming, outgoing and authentication requirements for the real Outlook mailbox.
Microsoft Teams
Application concept: Plan a Teams setup handover naming who owns account verification and future reconnects.