Incoming Mail and OAuth Connections

Overview

Incoming Mail and OAuth Connections are separate setup areas in the current OneSuite release. Incoming Mail covers receiving-mail configuration, while OAuth Connections is the canonical place for provider authorization such as Google or Microsoft connections. Keeping these destinations separate makes it easier to diagnose whether a problem is related to mailbox receiving configuration or provider authorization.

Business Value and Typical Use Cases

Connect a supported provider account.
Repair an expired or revoked provider authorization.
Review incoming-mail configuration when outbound email works but new inbound messages do not appear.
Confirm the correct account before reconnecting a mailbox.

Before You Begin

Use the provider account that owns or is authorized for the mailbox.
Make sure browser pop-ups or redirects are not being blocked.
Know whether you are troubleshooting incoming mail or the provider connection itself.

Prerequisites and Permissions

Administrator access.
Supported provider account.
Internet access and provider login access.

Concepts

OAuth gives OneSuite permission to access a supported provider account without storing the user password. Incoming-mail configuration governs how messages are retrieved. A healthy mailbox may require both a valid account record and a valid connection.

How This Feature Fits Into OneSuite

Communications intersects with CRM, tasks, appointments, booking, and customer history. Use related records to avoid repeating conversations or contacting the wrong person.

Connected services such as Gmail, Microsoft/Outlook, Google Calendar, Google Meet, and Zoom should be treated as provider connections that enable specific OneSuite workflows; their presence does not automatically grant every user access.

Screen Orientation

Communications brings multiple channels into OneSuite, including supported email, SMS, browser calling/phone functions, voicemail, calendar connections, meetings, and booking. Each channel has its own connection and permission requirements, so validate setup before diagnosing a user workflow.

Always confirm the sender, mailbox, phone number, extension, calendar, or meeting provider context before sending or placing an action. Shared communication resources can serve multiple users, but ownership and visibility rules still matter.

Use customer context whenever available. Messages, calls, appointments, and related activity are more useful when staff can understand who the customer is and what happened previously.

Open the area described in this guide and pause before editing. Identify the page heading, primary action button, search/filter controls, record list or detail panel, status indicators, and any related-record or history areas. This quick orientation prevents users from applying instructions to the wrong record or module.
When the page contains both a list and a record/detail view, use the list for discovery and the detail view for action. Search or filter first, then open the exact record and verify identifying information before making changes.

Role-Specific Guidance

End users work within the channels assigned to them and should not change provider-level configuration unless their role explicitly requires it.
Managers establish communication practices such as response ownership, shared-number usage, appointment handling, and escalation.
Administrators configure supported accounts, numbers, extensions, provider connections, permissions, and organization-level communication settings.

Step-by-Step Instructions

Open the Email section in OneSuite.
Use Incoming Mail when reviewing receiving-mail configuration.
Use OAuth Connections when connecting or reconnecting a supported Google or Microsoft account.
Follow the provider sign-in and consent process.
Return to OneSuite and confirm the connection is shown as active.
Open Email Client and run a manual Sync to verify incoming messages.

Expected Results

The connection should return to OneSuite successfully, the mailbox should remain available, and incoming mail should be retrievable by the Email Client.

Verification Checklist

Confirm the correct OneSuite user is signed in and the expected role/permissions are active.
Confirm the customer, company, invoice, product, message, appointment, employee, or other record shown on screen is the one intended for the task.
After saving or completing the action, refresh or return to the relevant list and verify the new status, history entry, balance, message, appointment, or record appears where expected.

Business Workflow

Mailbox exists → Incoming-mail setup is confirmed → OAuth provider is authorized → Email Client syncs → User receives and sends email.

Real-World Business Scenarios

No additional role-specific guidance is required for this topic.

Advanced Operational Guidance

For repeatable business work, standardize naming, ownership, tags/statuses, and staff responsibilities before increasing volume. Consistency makes OneSuite search, reporting, history, and handoffs substantially more useful.
When multiple modules participate in the workflow, verify each handoff. Do not assume that completing one screen automatically proves the customer, payment, communication, or reporting outcome is correct elsewhere.

Screenshots

Production screenshots appear here only after approved OneSuite captures are attached. Written instructions are complete without screenshots.

Best Practices

Reconnect from the mailbox or connection area that matches the account you intend to authorize.
Use manual Sync immediately after reconnection as a verification step.
Avoid disconnecting a working account when troubleshooting an unrelated mailbox.

Common Mistakes

Treating Incoming Mail and OAuth Connections as the same screen.
Signing in with the wrong Google or Microsoft account during authorization.
Assuming outbound success proves incoming authorization is healthy.

Troubleshooting

OAuth returns but mailbox is not active: verify the account selected during provider sign-in.
Incoming mail still does not appear: confirm the mailbox, provider authorization, and manual Sync.
Connection options appear different by role: use an administrator account for setup.

Frequently Asked Questions

Why are Incoming Mail and OAuth Connections separate?: They serve different setup purposes.
Should I reconnect if email is working?: Not unless you are resolving a connection problem or intentionally changing the account.
Can a normal user manage OAuth?: Connection setup is generally an administrator task.

Next Steps

Continue with the Related Articles section to follow the workflow into the next OneSuite function instead of returning to the homepage after every task.

Last Updated: August 21, 2026
Version: 0.3.2-Phase2B-SHORTCODE-RENDER-RECOVERY
Verified Public Source Baseline: PASS35H66DN RC1 GOLD R63.97
Documentation Revision: Phase 2B Enterprise Detail Expansion