Mailboxes and Email Accounts

Overview

Mailboxes identify the email accounts that OneSuite users can read from or send through according to their permissions. Keeping mailbox records organized is important because email, campaigns, notifications, and other communications may need a clearly selected sender or receiving account.

Business Value and Typical Use Cases

Give staff access to their authorized business mailbox.
Use a shared mailbox for a team or department.
Choose an email-of-record sender for campaigns or operational messages.
Separate provider connection setup from the day-to-day Email Client.

Before You Begin

Know the mailbox email address and provider.
Decide which users should be allowed to read or send.
Complete provider authorization when required.

Prerequisites and Permissions

Administrator access for mailbox setup.
Valid email account with the provider.
Provider credentials or OAuth authorization as required.

Concepts

A mailbox is the user-facing account record. Provider authorization determines how OneSuite connects to the email service. User access determines who can see or send from the mailbox. These are related but separate concerns.

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 Mailboxes from the Email section.
Review existing accounts before creating another record.
Open or add the mailbox that should be available in OneSuite.
Confirm the mailbox identity and the users who should have access.
Complete the applicable provider or OAuth connection.
Open Email Client and verify the mailbox appears for an authorized user.

Expected Results

Authorized users should see the mailbox in the Email Client and be able to perform the actions granted to them, such as reading or sending.

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

Administrator configures mailbox → Provider connection is authorized → User access is assigned → Mailbox appears in Email Client → Staff reads and sends 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

Use clear mailbox names when multiple departmental accounts exist.
Avoid creating duplicate mailbox records for the same address.
Review access when staff roles change.

Common Mistakes

Creating a mailbox but not completing its provider connection.
Giving a user mailbox access without send permission when sending is required.
Using the wrong sender mailbox for a campaign.

Troubleshooting

Mailbox does not appear: confirm the account is active and the user has access.
Sending fails: verify provider authorization and sender permissions.
Incoming mail does not update: review Incoming Mail or OAuth connection status.

Frequently Asked Questions

Can multiple users access a mailbox?: Yes, where the administrator grants access.
Can OneSuite have multiple mailboxes?: Yes.
Does creating the mailbox automatically authorize Gmail or Microsoft?: No. Provider authorization is a separate step when required.

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