Business / Separate mailbox access and fresh consent

MCP mailbox access with separate read permission

Share limited synced plain-text content from an authorized mailbox through a read-access decision separate from sending permission.

PRODUCT VIEW

See how it works.

Choose which authorized mailbox an MCP client may read, limited to conversation text already synced into Hubz. First, eligible mailbox access is specified; then fresh OAuth consent and explicit reading scope are assessed for the client. This does not grant unrestricted access to the live Gmail provider. Shareable information is limited plain-text conversation content; attachments, raw HTML, access details and provider credentials remain outside scope.

Hubz.Workspace / MCP mailbox read accessDK

EXPLORE THE PRODUCT

MCP mailbox read access

Sample view

◎

BUSINESS · MCP

MCP mailbox read access

1Specific mailboxDepends on scope

2Synced conversation textDepends on scope

3Permission independent of sendingDepends on scope

4Fresh user consentDepends on scope

5Permission lifecycleReview

Content → review → permitted action

Only limited synced plain text is shared; attachments and raw HTML are outside scope.

01Choose the mailbox.

02Authorize read access.

03Review and revoke access.

Interface illustration using sample data. The layout is simplified to explain the relevant feature.

FROM NEED TO OUTCOME

Where this helps.

Treating sending and reading as the same permission can expose sensitive correspondence too broadly. Assuming that the entire mailbox or attachments are automatically opened also misrepresents the actual access boundary.

WHAT YOU CAN WORK TOWARDS

Know which mailbox is readable by which client and under which explicit permission. Provide only the limited synced-text context the connection needs, keeping sending, attachments and live provider access separate.

STEP BY STEP

How to use it.

01
Choose the mailbox.
In the appropriate administrator and user context, review which mailbox can be selected for MCP reading.
02
Authorize read access.
Explicitly assess the client’s requested mail-read scope in a new OAuth review rather than relying on earlier sending permission.
03
Review and revoke access.
Check the authorized mailbox and connection validity, and revoke relevant access when it is no longer needed.

INSIDE THE MODULE

What can you do?

FOCUS 01⊙

MCP mailbox read access

Scope●Permission○Review○

Choose the mailbox.

Specific mailbox

Identify the readable account explicitly in connection policy instead of granting a general mail permission.

FOCUS 02▤

MCP mailbox read access

Scope○Permission●Review○

Authorize read access.

Synced conversation text

Give the assistant context through eligible conversation text retained in Hubz within the permitted limits.

FOCUS 03↗

MCP mailbox read access

Scope○Permission○Review●

Review and revoke access.

Permission independent of sending

Do not substitute email-sending or campaign-launching scope for a reading decision.

FOCUS 04◇

MCP mailbox read access

Scope●Permission○Review○

Choose the mailbox.

Fresh user consent

When adding reading, use a current permission review rather than letting an older connection gain access automatically.

FOCUS 05⌁

MCP mailbox read access

Scope○Permission●Review○

Authorize read access.

Permission lifecycle

Assess account access, connection validity and revocation together to avoid retaining unnecessary permissions.

IN EVERYDAY WORK

What it looks like in practice.

Business user

Providing context so an assistant can summarize a synced conversation in an authorized work mailbox.

Only the specified mailbox and explicit read scope are used. Attachments and the live Gmail account are not opened to general access.

Scenarios are illustrative; they are not customer testimonials or measured performance claims.

KNOW WHAT IS INCLUDED

Plans, permissions and limits.

MCP is available only on Business. Authorize each connection for the appropriate workspace and permissions, and review actions requiring separate approval. An earlier authorization does not remove the requirement for an eligible Business subscription.

Only limited synced plain text is shared; attachments and raw HTML are outside scope.
This feature does not provide live provider access or share credentials.
Sending permission does not automatically authorize reading, and reading permission does not authorize sending.

Compare plans

YOUR QUESTIONS

About this feature.

01Can a client read my correspondence if I granted email-sending permission?

No. Mail reading requires separate account access and fresh OAuth consent.

02Are attachments and raw email HTML shared too?

The current MCP Inbox scope is limited synced plain text. Attachments, raw HTML and provider credentials are not shared.

RELATED WORKFLOW GUIDES

You may also need these features.

MCP connectionsAuthorize a compatible MCP client through OAuth and review its accessible modules, permission validity and revocation options.MCP private plansReview proposals prepared under explicit planning permission with their content, recipient, cost and validity information.MCP communication approvalsReview an assistant-prepared email or limited campaign request in Hubz, with its sender, recipients and full message visible before approval.

MODULES THAT WORK TOGETHER

Explore related modules.

Inbox and Gmail

Use in-app notifications for daily work, and connect authorized Gmail conversations with Professional and Business.

MCP and AI connections

Connect compatible clients to permitted CRM context, with separate review and authorization for private plans and communications.

Security and team access

Arrange team access through workspace membership, existing roles, enabled modules and connection permissions.