Docupath sends transactional email notifications for account, document, and workspace events, such as user invitations, login codes, document rejections, and credit warnings. When documents are submitted by email, the sender also receives a status reply confirming what happened to their submission. Every notification is sent from a single Docupath address and shares one branded design, so recipients can recognize a genuine Docupath email at a glance.
How It Works
The Branded Email Design
All notification emails are built on a shared branded layout:
The docupath. wordmark at the top
A category label that identifies the type of email at a glance (for example Login code or Document rejected). Upload status replies use color-coded labels: green and black for received confirmations, red for delivery failures, amber for account-related holds.
A white content card with the message, and a call-to-action button where an action is needed
A footer with the support contact (support@docupath.ai)
Account and Document Notifications
Notification | Category label | Purpose |
User invitation | Activation | Invites a person to join a Docupath workspace |
Welcome email | Welcome | Welcomes a newly added user |
OTP login code | Login code | Delivers a one-time code for logging in |
Password reset | Password | Sent for a password reset request |
Email change verification | Verify email | Verifies a request to change the account email address |
Document rejection | Document rejected | Notifies configured recipients that a document was rejected, with the document attached as a PDF |
Document rejection (XML) | Document rejected | The same rejection notification with the XML output attached |
Low credits | Low credits | Warns workspace administrators that processing credits are running low |
Email Upload Status Replies
When someone submits documents to Docupath by email, the sender receives a status reply sent when the email lands. The reply confirms what happened at intake. An email whose files partly succeed and partly fail produces two replies: a Document processing issue naming each failed file, and a Documents received for the files that were stored.
Reply | Subject line | Label | Sent when |
Documents received | We've received your documents | Documents Received | One or more attached files are accepted (single or multi-file upload) |
Email received | We've received your email | Email Received | The email has no attachment, so the message body is processed as the document |
Document processing issue | Document processing issue | Document Failed | An attached file cannot be processed: too large (over 50 MB), empty, an unsupported file type, or the email carries more than 15 supporting attachments for a single primary document |
Document limit reached | Document limit reached | Document Limit Reached | The email is sent to a Multiple Primary Documents address and carries more than 10 attachments, so none of them are stored |
Organization not found | Delivery Failure Notice: Action Required | Organization Not Found | The recipient address reaches a valid workspace but does not match a known organization, so nothing can be stored. Sent for single-file, multi-file, and body-only submissions alike |
Workspace not found | Delivery Failure Notice: Tenant Not Found | Email Delivery Issue | The workspace in the recipient address does not exist |
Upload by email disabled | Upload via Email Feature Not Available | Email Upload Disabled | The workspace does not have upload via email enabled, or the feature has lapsed and is waiting to be renewed |
Insufficient credits | Insufficient credits | Insufficient Credits | The workspace does not have enough processing credits |
How the status replies behave:
They confirm receipt, not the processing outcome. The reply tells the sender their submission was accepted or why it was not. Processing results are tracked on the dashboard; there is no email when processing completes.
The received confirmations link to the dashboard. Both the Documents received and Email received replies carry a Track on your dashboard button that opens the workspace's document review page (signing in is required).
An unmatched organization always produces a delivery failure. The organization is matched from the recipient address, so when that address matches no organization, nothing is stored and the sender receives the Organization not found reply. This is the same for a multi-file upload as for a single file. If a batch does store some documents while others cannot be matched, the Documents received reply carries a notice such as "1 document couldn't be matched to an organization in your workspace and won't be processed."
Each sub-organization chooses which replies its senders receive. The Email types setting on the sub-organization offers three options. All emails (the default) sends every reply. Failed documents only silences the two received confirmations and sends everything else, so the sender still hears about a refused document (Document processing issue and Document limit reached) and about a blocked workspace (Upload by email disabled and Insufficient credits). No emails silences all of those. Documents are still stored and processed as usual; the setting only controls the replies. Delivery failure replies are never affected, so a sender is still told when an email could not be delivered at all.
One reply per email, whatever the number of Docupath addresses on it. An email addressed to several Docupath ingestion addresses is handled as one submission to the organization behind the last of those addresses. The sender receives a single reply covering that organization, governed by that sub-organization's Email types setting. Nothing is stored for the earlier addresses and no reply is sent on their behalf.
The sub-organization decides who is copied on the replies. The Copy additional recipients setting holds a comma-separated list of up to 10 addresses, and every reply that sub-organization sends is copied to them. It is empty by default, which means the reply goes to the sender alone. The addresses come from this setting rather than from the Cc line of the inbound email, so the customer chooses who hears the outcome instead of whoever the sender happened to copy. An address already receiving the reply is dropped so nobody gets two copies, and delivery failure replies never carry Cc. Because the copies ride on the reply itself, a sub-organization set to No emails sends nothing and so copies nobody.
The Insufficient credits reply goes to the sender, not to workspace administrators. It names the workspace and asks the sender to contact their administrator to add credits.
Failure replies echo the original message. Delivery failure replies include the address the email was sent to, the time it was received, and the attachment list (shown as "Email body" when there was no file).
Replies land in the sender's email thread. Status replies answer the original message, so mail clients group them into the same conversation with a "Re:" subject. Delivery failure notices can arrive as a separate new email instead.
What the Replies Look Like
Email received (no attachment, body processed as the document):
Document processing issue, showing the failed file and the reason:
Organization not found, with the original message details:
Workspace not found:
Upload by email disabled:
Insufficient credits, naming the workspace:
Supported Configurations and Options
Option | What it does | Where to configure |
Global rejection notification recipients | Sets who receives document rejection notifications (comma-separated, maximum 10 addresses) | System Settings |
Upload via email | Enables document submission by email for a workspace; when not enabled or lapsed, senders receive the Upload by email disabled reply | Enabled per workspace |
Email types | Chooses which status replies senders to a sub-organization's inbox receive: All emails (default), Failed documents only, or No emails. Delivery failure replies are always sent, whatever this is set to | Manage Organizations, edit a sub-organization, under Ingested email notifications |
Copy additional recipients | Copies every reply the sub-organization sends to a comma-separated list of up to 10 addresses. Empty by default, which sends the reply to the sender alone. A Docupath inbox address is rejected, as is a repeated address, and the whole list is limited to 1000 characters | Manage Organizations, edit a sub-organization, under Ingested email notifications |
Other Technical Specifications
Aspect | Details |
Sender address | Docupath AI auth@docupath.ai |
Support contact (footer) | |
Email type | Transactional (sent per event, not batched) |
Status reply timing | Sent when the email is received, not after processing finishes |
Threading | Status replies answer the original message and appear in the sender's thread; delivery failure notices can arrive as a new email |
Notes
Workspace branding does not apply to emails. Notification emails always use the Docupath branded design. A custom logo uploaded in System Settings > Branding appears in the platform interface only, not in emails, including white-label deployments.
Emails are not customizable. The template, subject lines, and sender address of notification emails cannot be changed per tenant.
Status replies are receipts, not results. A sender who receives "We've received your documents" should check the dashboard for the processing outcome; no follow-up email is sent when processing finishes.
Turning replies off does not hide delivery failures. Whatever Email types is set to, a sender whose email cannot be delivered at all still gets the matching delivery failure reply.
Only the received confirmations are silenced on Failed documents only. A sender blocked by a disabled upload feature or insufficient credits still hears about it in that mode, because those replies tell the sender their documents were not processed, which is what a refusal tells them.
Copy recipients follow the reply, not the setting. Nobody on the Copy additional recipients list is contacted for a reply that Email types has silenced, and nobody is copied on a delivery failure.