Email configuration and delivery

Understand platform email, staff account email and customer email integrations.

Three different purposes

Account verification/recovery, business/team notifications and customer email workflows are different functions. Configuring one does not automatically enable the others. Your deployment’s supported integration determines which customer email operations are available.

Platform and sender setup

Authorised operators configure the approved email provider, verified sender/domain and required DNS/authentication records. Production sending permissions, bounce/complaint handling and provider limits must be confirmed. Tenants should use only the sender identities authorised for their business.

Business configuration

1. Open Business Admin → Integrations and review the email capability offered by your deployment.
2. Enter only the identifiers/settings required by that supported connector and store credentials through the protected configuration.
3. Confirm the intended sender, recipient purpose and workflow permission.
4. Test with an authorised test recipient and inspect the actual delivery result.

Scope and permissions

MAY does not promise automatic access to every Gmail, Outlook or IMAP mailbox. A mailbox connection requires an implemented connector and explicit provider authorisation. Custom mailbox or enterprise mail-system development can be discussed through Custom.

No-email staff and sample workspaces

Staff without email can use the administrator-provisioned account path and direct setup/reset codes. The MK Autoz sample tenant retains outbound-email suppression; changing display names or uploading vehicle knowledge does not enable real email delivery.