Documentation / QueryTek Review glossary / Email Ingestion
Email ingestion is an intake channel where documents arrive as attachments to a dedicated email address and are turned into review submissions automatically. It lets people send work for review from the tool they already use, while the service checks every attachment before anything enters the customer's workspace.
Many people who need a document reviewed will never log in to a portal. They live in email, and forwarding a file is the path of least resistance. Email ingestion accepts that habit and puts the controls behind it rather than in front of it.
Three elements make it work.
An address bound to a customer. Each customer organization receives its own intake address. Mail sent there is attributed to that organization, so the question "whose document is this?" is answered by where it was sent, not by guessing from the sender.
Attachment validation. Email is also the most common delivery route for malicious files. Every attachment is checked before it is accepted: file type against the formats the service supports, size against allowed limits, and content scanning for anything unsafe. An attachment that fails is not turned into a document.
Normal handling afterwards. A validated attachment becomes a document in the customer's workspace and follows the same path as a portal upload. Email changes how work arrives, not how it is reviewed, quoted, or protected.
The misconception to avoid is that email ingestion is a lighter-weight, less governed path. Done properly it is the opposite: the channel with the least control over what is sent is the one that needs the most checking on receipt.
Every intake channel is a door into the customer's workspace. A channel that is convenient but unchecked becomes the easiest way to put unwanted content in front of reviewers, and a channel that loses attribution creates documents nobody can confidently assign to an owner.
QueryTek Review gives each customer tenant an intake email address. Attachments are validated for type, size, and content before they become documents in the client workspace, then follow the same review cycle as portal uploads. Address formats, size limits, and scanning details are not published.
