Connecting Gmail

Overview

A Gmail connection allows an authorized Google mailbox to participate in OneSuite email workflows. The current public build separates mailbox records, incoming-mail configuration, and OAuth provider authorization so administrators can verify each part of the connection without confusing the account record with the provider consent process.

Business Value and Typical Use Cases

Connect a Google business mailbox to OneSuite.
Reconnect a Gmail account after authorization expires or is revoked.
Verify incoming Gmail after connection.
Use the connected mailbox in the OneSuite Email Client.

Before You Begin

Sign in with the Google account that owns or is authorized for the mailbox.
Confirm the mailbox already exists in OneSuite when applicable.
Use an administrator account for initial connection setup.

Prerequisites and Permissions

Google account.
OneSuite administrator access for setup.
Browser access to complete Google sign-in and consent.

Concepts

The mailbox identifies the account inside OneSuite. OAuth Connections authorizes access to Google. Incoming Mail and the Email Client then use the connected account according to the current configuration and user permissions.

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.
Review Mailboxes and confirm the Gmail address is the account you intend to connect.
Open OAuth Connections.
Start the Google connection for the intended mailbox or account.
Sign in to the correct Google account and complete the requested consent steps.
Return to OneSuite and confirm the connection is active.
Open Email Client, select the mailbox, and use manual Sync once to verify incoming mail before relying on automatic Inbox checks.

Expected Results

The Gmail account should return to OneSuite as an active connection, the mailbox should remain available to authorized users, and the Email Client should be able to retrieve incoming mail.

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.
Verify the selected mailbox/account and intended sender identity before sending any customer communication.

Business Workflow

Create or review mailbox → Authorize Google → Confirm connection → Open Email Client → Sync Inbox → Send and receive business email.

Real-World Business Scenarios

Personal mailbox workflow: connect the authorized account, verify it is available to the intended OneSuite user, then use the Email Client to read and send within the supported workflow.
New message does not appear: confirm connection/account state, allow the documented sync interval, refresh the appropriate view, and verify filters or mailbox selection are not hiding the message.
Provider reconnection: use the supported OAuth/connection area rather than entering provider credentials into unrelated OneSuite fields.

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.
Keep mailbox ownership and connected-account responsibilities clear. Shared operational practices should not depend on users borrowing another person’s provider credentials.

Screenshots

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

Best Practices

Check the Google account name carefully before approving access.
Use manual Sync immediately after connection as a verification step.
Do not reconnect a different Gmail account over a working mailbox by mistake.

Common Mistakes

Authorizing the wrong Google account.
Creating a duplicate mailbox before checking the existing mailbox list.
Assuming a completed OAuth screen automatically grants every user access to the mailbox.

Troubleshooting

Connection returns but Gmail is unavailable: verify the Google account used during authorization and the mailbox record.
Incoming Gmail does not appear: run manual Sync and review Incoming Mail and OAuth connection status.
A user cannot see Gmail: review mailbox access for that user.

Frequently Asked Questions

Does Gmail use OAuth?: Yes, the current provider workflow uses the OAuth Connections area for supported Google authorization.
Should I use Incoming Mail instead of OAuth Connections?: They serve different purposes; use OAuth Connections for provider authorization and Incoming Mail for receiving-mail configuration.
Will Gmail auto-sync after connection?: The Email Client performs frequent Inbox checks while the Inbox is visible when the connection is healthy.

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