Business / Human-approved email and bounded campaign requests

Human approval for MCP email and campaign requests

Review an assistant-prepared email or limited campaign request in Hubz, with its sender, recipients and full message visible before approval.

PRODUCT VIEW

See how it works.

An MCP client can prepare an email or campaign request for you to review. Only a separate approval in Hubz can send an eligible request to the delivery queue. The user sees the mailbox or campaign sender, the recipient or saved audience and the complete message. Account access, connection communication limits and the required approval validity are assessed separately. Unlike private-plan review, an eligible request approved here can proceed to an authorized delivery process.

Hubz.Workspace / MCP communication approvalsDK

EXPLORE THE PRODUCT

MCP communication approvals

Sample view

◎

BUSINESS · MCP

MCP communication approvals

1Exact sender selectionDepends on scope

2Single-recipient email requestDepends on scope

3Bounded campaign requestDepends on scope

4Separate human approvalDepends on scope

5Operation statesReview

Content → review → permitted action

Communication permission does not grant mailbox reading; reading is authorized separately.

01Define account and connection limits.

02Review the prepared request.

03Make the operation decision.

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

FROM NEED TO OUTCOME

Where this helps.

General permission for an assistant must not be treated as approval to send for every message and recipient. Reusing an old review after the sender or audience changes also fails to establish a reliable decision.

WHAT YOU CAN WORK TOWARDS

Review the exact sender, recipients, content and requested action. Proceed to an eligible queue only with separate approval for that request, tracking request, approval and provider result as different states.

STEP BY STEP

How to use it.

01
Define account and connection limits.
Specify the exact mailbox or campaign sender permitted by an eligible administrator and the connection’s boundaries.
02
Review the prepared request.
Check sender, recipient or audience snapshot, message and validity information in the separate Hubz review.
03
Make the operation decision.
Approve or reject an eligible request, then separately track the provider result of any queued operation.

INSIDE THE MODULE

What can you do?

FOCUS 01⊙

MCP communication approvals

Scope●Permission○Review○

Define account and connection limits.

Exact sender selection

Tie the operation to explicit access for a specific mailbox or campaign sender.

FOCUS 02▤

MCP communication approvals

Scope○Permission●Review○

Review the prepared request.

Single-recipient email request

Review one-to-one communication against its actual recipient and full message.

FOCUS 03↗

MCP communication approvals

Scope○Permission○Review●

Make the operation decision.

Bounded campaign request

Assess selected saved audiences together with recipient and daily limits in the permission profile.

FOCUS 04◇

MCP communication approvals

Scope●Permission○Review○

Define account and connection limits.

Separate human approval

Use the workflow that prevents a client-prepared request from reaching delivery without this review in Hubz.

FOCUS 05⌁

MCP communication approvals

Scope○Permission●Review○

Review the prepared request.

Operation states

Track prepared, approved, blocked and provider-result-pending stages without confusing them.

IN EVERYDAY WORK

What it looks like in practice.

Authorized Business user

Assessing an assistant-prepared single-recipient feedback request before sending.

Mailbox, recipient and complete content are reviewed in a separate approval; only an eligible approved request enters the delivery queue.

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.

Communication permission does not grant mailbox reading; reading is authorized separately.
Accepting a private plan does not replace approval of the communication request.
Sending capacity, recipient eligibility, approval validity and provider conditions are reassessed before execution.

Compare plans

YOUR QUESTIONS

About this feature.

01Can the MCP client send on its own?

In the current workflow, the client prepares a request. Separate Hubz approval is required to queue an eligible request for provider delivery.

02Can it use any campaign list?

Only saved audiences included in the permission profile and defined limits are available. The request’s exact scope is visible during human review.

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 mailbox read accessShare limited synced plain-text content from an authorized mailbox through a read-access decision separate from sending permission.

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.

Email marketing

Manage campaign preparation, templates, audiences and delivery records in one place.

MCP and AI connections

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