User guide
Inbound email
Use inbound email to receive new messages into a tenant review inbox and turn authorized replies to QMPlus notifications into comments.
Inbound email has two separate purposes: receiving new email for tenant review and accepting verified replies to selected QMPlus comment notifications. Each purpose uses a different kind of address and a different authorization flow.
Before you begin
The Inbound email feature must be enabled for the tenant, and system operations must have configured the inbound SMTP service. A system administrator can then open Administrator → Preferences → Email → Inbound email and choose which processing cases the tenant allows.
Enabling the product feature does not enable mail processing by itself. Missing or disabled tenant settings are treated as off.
Email address types
| Address type | Format | Purpose |
|---|---|---|
| Tenant inbox | <tenant-id-or-name>@inbound.qmplus.app | Receives new email into the tenant’s inbound review inbox. |
| Verified reply | r+<token>@inbound.qmplus.app | Routes a reply to the notification recipient and QMPlus entity for which the address was issued. |
The tenant reference is the exact tenant ID or tenant name recognized by QMPlus. Ask your QMPlus system administrator or operations contact to confirm the address before distributing it.
Verified reply addresses are created automatically and placed in the outgoing notification’s Reply-To header. The user’s normal Reply action selects that address. Do not create, edit, share, or reuse a reply address manually: its opaque token is a short-lived authorization capability tied to a specific recipient and notification context.
QMPlus routes mail from the SMTP envelope recipient. Text in the message’s visible To, Cc, or subject fields does not select another tenant or target.
Enable the tenant inbox
Turn on Accept mail into the tenant review inbox to allow new messages sent to the tenant inbox address.
When the setting is enabled:
- The SMTP service validates the recipient and resolves exactly one active tenant.
- QMPlus durably records the accepted delivery before background processing begins.
- The message is parsed into a safe preview, with its processing and audit history available in the
Inbound emailworkbench. - Enabled triage or review rules determine the next proposed outcome.
When the setting is disabled, new messages to the tenant inbox address are rejected. Deliveries accepted earlier remain available according to their access and retention rules.
Configure AI triage and outcomes
AI triage is optional and remains off until an administrator accepts the current provider disclosure. Consent is tied to both the policy version and configured provider; a change to either one invalidates the existing consent.
Before enabling AI triage, select an eligible Triage actor. QMPlus uses that active user’s identity and current access when it evaluates tenant context. You can then allow one or more review outcomes:
- Attach the email to an existing case the triage actor can access.
- Create a new entry through the normal form-entry flow.
- Mark the delivery as spam.
- Send uncertain or policy-limited mail to human review.
AI produces a proposal for review; it does not bypass the selected outcomes or current QMPlus authorization. Raw MIME and attachment contents are excluded from AI triage. The settings panel lists the provider’s current data scope before consent is accepted.
Enable verified comment replies
Verified replies can be enabled independently for comments on messages, actions, documents, audits, and hearings.
The flow is:
- QMPlus sends an eligible comment notification with a unique verified reply address in
Reply-To. - The intended recipient replies from the email address associated with their active QMPlus user.
- On receipt, QMPlus validates the reply route, sender identity, tenant access, supported entity type, target state, and the user’s current permission to comment.
- If every check passes, QMPlus creates one comment and records its inbound-email provenance. Retries do not create duplicate comments.
Forwarding a notification does not transfer the right to comment. An expired, revoked, already consumed, mismatched, or unauthorized reply route cannot perform the business action. A reply that cannot be applied safely is rejected or retained for review according to its processing state.
Attachments
Attachment contents are never sent to AI triage. Turn on Allow inbound attachment processing only when clean, retained attachments may be copied into an approved business operation.
Inbound attachments remain untrusted. Review the sender and expected file before downloading or opening one. Raw email and retained attachment access are restricted separately from ordinary inbox access and may expire according to server retention policy.
Access and administration
Inbound email permissions are separate so tenants can limit sensitive operations:
| Permission | Allows |
|---|---|
| Inbound email menu access | View the tenant inbox, delivery detail, safe preview, and operation timeline. |
| Mail triage review access | Review and decide AI triage proposals. |
| Raw inbound email access | Deliberately download retained raw message source or retained attachments. Raw access is audited. |
| Inbound email administration | Retry, quarantine, release, or otherwise administer eligible deliveries. |
System administrators manage the tenant processing settings. System operations manages the server-wide SMTP domain, availability, storage, security, and retention configuration.
Troubleshooting
| Symptom | What to check |
|---|---|
| New mail is rejected | Confirm the exact tenant inbox address, tenant feature, tenant status, and Accept mail into the tenant review inbox setting. |
| A reply does not create a comment | Reply to the notification without changing Reply-To; use the intended recipient’s QMPlus email address; confirm that the entity’s comment type and current user permission are still enabled. |
| AI triage cannot be enabled | Confirm that the tenant inbox is enabled, an eligible triage actor and at least one outcome are selected, the AI feature is available, and current provider consent has been accepted. |
| A message is quarantined or needs review | Open its processing history. A disabled outcome, failed authorization check, unsafe content, or temporary processing failure can prevent automatic action. |
| An attachment is unavailable | Confirm attachment processing and raw-access permissions, scanning/retention status, and whether the retained file has expired. |
If the displayed address or server availability is unclear, contact QMPlus system operations before publishing the address externally.