# Connect email to Masheev

Email and provider email connections are **beta**. Your workspace must be eligible
and the provider's authorization requirements must be met. A plan entitlement
does not guarantee that a connection is available today.

## Choose an available connection

Open the workspace's inbox/integration settings in the [dashboard](https://app.masheev.com).
Use the connection methods actually offered for the account:

- Gmail or Microsoft email, when the account is eligible for the provider beta.
- SMTP/forwarding, when enabled and configured for the workspace.

Complete provider authorization in the provider's own sign-in flow. Never paste
your mailbox password or OAuth tokens into an agent prompt. If a method is absent,
confirm eligibility with Masheev rather than inventing an API connection.

## Configure the inbox

Select or create the email inbox, assign the agent and relevant knowledge, and
choose the intended review/handoff behavior. For forwarding, copy the exact
inbound address from the dashboard and configure the provider's routing settings.
Use only DNS/sender verification records shown for your configured sending service.
Do not add example SPF or DKIM records without checking the existing domain setup.

## Verify before routing customers

Use a test sender to check inbound delivery, correct inbox routing, reply threading,
draft review or automatic reply behavior as configured, and human handoff. Verify
that a disconnected/revoked provider is reported as unavailable. Avoid a forwarding
loop between the original mailbox and Masheev.

Browser client tools are not email-agent tools. An email workflow needs a supported
server-side integration. See [availability](https://docs.masheev.com/capabilities.md) and [business tools](https://docs.masheev.com/client-tools.md).