Microsoft OAuth
Use the supported provider authorization experience for approved Microsoft accounts. The user completes consent through Microsoft rather than storing a Microsoft password in a union record.
Union email management software
Connect supported Microsoft, Gmail or IMAP and SMTP accounts, then relate conversations, senders, recipients and attachments to cases, people and organizational entities.
Email in context
Union work often begins or advances through email, but a private inbox is a fragile system of record. The person who receives a message may not own the case forever, attachments can become detached from decisions, and another representative may see only a forwarded fragment.
UnionStack lets an authorized user connect an approved mailbox, review conversations and relate the relevant thread to a case, person or organizational entity. Senders, recipients, priority, importance, signatures and attachments remain part of the communication context.
The relationship is the key design choice. The message remains a message; a case remains the record of the procedure. Teams can use notes for analysis and decisions without copying full email bodies into multiple places.
Connection options
Use the supported provider authorization experience for approved Microsoft accounts. The user completes consent through Microsoft rather than storing a Microsoft password in a union record.
Connect supported Google accounts through the approved authorization flow and verify the identity, inbound conversation and outbound message behavior.
For another approved provider, configure the permitted incoming and outgoing server settings, encryption, ports and credential method required by the organization.
Four connected capabilities
UnionStack combines provider connectivity with record context, journal visibility and controlled contact provisioning.
Use supported Microsoft Outlook, Google Gmail, or IMAP and SMTP providers to send and receive operational email.
Connect an email account to the case type it supports, keeping the mailbox aligned with the procedure and team responsible for the work.
Track member and employer conversations in the modern journal so communication remains visible alongside the related operational record.
Maintain approved external domains, such as an employer. When email arrives from a specified domain, UnionStack automatically provisions and connects the person record to the platform.
Real workflow
Confirm organizational ownership, the intended user, provider requirements and the records the mailbox will support. Use a controlled test account first.
Use Microsoft or Gmail authorization where supported, or enter approved IMAP and SMTP settings. Do not put mailbox credentials in notes or custom fields.
Review the connected addresses, signature and outbound behavior. Send an internal test and confirm the recipient sees the expected identity.
Open the test thread and verify subject, participants, importance, message order and attachments before relating it to operational work.
Connect the conversation to the case that owns the procedural context, then add other person or entity relationships only when they aid discovery.
Ask another authorized user to open the case, find the related conversation and understand why the message matters without accessing the original private inbox.
Feature evidence
| Capability | Demonstration evidence |
|---|---|
| Provider connection | Show the supported Microsoft, Gmail or server-based setup without exposing a credential in application records. |
| Conversation fidelity | Open a multi-message thread and identify sender, recipients, subject, importance and attachments. |
| Record relationships | Relate the thread to a grievance, member and organizational entity, then navigate back from the connected case. |
| Outbound identity | Send a controlled message with the intended address and signature, then verify receipt. |
| Access and ownership | Explain who authorizes, maintains and disconnects accounts and what happens when a user’s responsibilities change. |
| Failure handling | Show how an expired authorization or server error is surfaced and how the team validates recovery. |
Buyer guidance
Operational mailbox integration preserves communication around members, cases and entities. Campaign segmentation, consent, bulk delivery, unsubscribe handling and marketing analytics are different requirements.
UnionStack includes connected email workflows and a Mailchimp integration path. During evaluation, identify which messages belong in case or member context, which belong in a campaign platform, and which system is authoritative for consent and audience membership.
Also document retention, legal hold, access and attachment rules. Connecting an inbox does not remove the organization’s responsibility to decide what communication should be maintained and who is authorized to see it.
From the UnionStack blog
See how approved Microsoft, Gmail or IMAP and SMTP accounts can keep operational conversations connected to union cases, people and entities.
Read the article →Related implementation guides
Use these maintained UnionStack 2.0 guides to evaluate the workflow in detail.
Choose Microsoft, Gmail or IMAP/SMTP and keep relevant messages with the work.
Support Team · UnionStack 2.010 min read → MicrosoftAuthorize Microsoft email securely and verify the sending and conversation experience.
Support Team · UnionStack 2.08 min read → Email providersChoose the supported connection for Google or another approved mail provider.
Support Team · UnionStack 2.09 min read → RelationshipsPreserve the conversation while making its relationship to union work explicit.
Support Team · UnionStack 2.08 min read →Built for connected work
Connect a controlled mailbox, relate a sample conversation and validate the handoff.