How IntELIEDocs works
IntELIEDocs has three moving parts: an orchestrator that holds the configuration, the documents you send into it, and the review step where a person confirms what was read.
The orchestrator
The orchestrator is the unit you configure and the place your documents live. Everything else is set on it: which connectors feed it, who can see it and where its results go. There is nowhere to put a document until an orchestrator exists.
There are four kinds. Choose the one that matches the outcome you want.
| Orchestrator | What it does |
|---|---|
| Smart Extract | Reads named fields out of a document. You define each field, its type and how to recognise it. |
| Smart Classes | Works out which type a document is, from the classes you describe. |
| Smart Queue | Routes each document. It can sort it into a Smart Class's categories first, then extract fields with a Smart Extract, redact it with a Smart Redact, or both. A queue that redacts also limits its originals to the people in its Original Access. |
| Smart Redact | Finds sensitive content and burns a box over it, and a reviewer can add a box detection missed. Only roles granted the IntELIEDocs · Original document permission can see the unredacted original. |
Getting documents in
Three routes lead to the same place. You add files by hand with Upload Document; an IntELIEKonnect import connector attached on the orchestrator's Import Channels tab brings them in on a schedule; or a voice conversation registers one. However it arrived, the document lands in that orchestrator's document list, and the Uploaded By column shows its origin.
What processing produces
Processing begins on arrival and runs unattended, so a new document opens at Processing. Depending on the orchestrator, it produces extracted field values, a class or a redacted copy, along with a status you can read at a glance. A locked PDF stops at Password Required and waits for you; a failure ends at Exception, which names the stage that failed.
Where review fits
Where you asked for review, a document stops at Waiting for Review rather than finishing on its own. A reviewer checks the values, corrects anything wrong and selects Mark as Reviewed. The document then reaches Completed, and delivery to any Export Channels you attached starts, either straight away or at that connector's next run. A saved correction stays marked: hover the field and it reads Edited by reviewer.
Running a document again
Once a document has an outcome (Waiting for Review, Completed, any export status or Exception), Re-run sends it through processing again from the start, if your role can run document actions. Except on an Exception, you confirm first. A re-run discards the current result and every reviewer correction, and a document that was already exported is delivered to your connectors again.
Next
- What an orchestrator is - the four kinds, and what they all share.
- Document statuses - what each badge means and what to do about it.
- Signing off and re-running a document - the review and re-run actions in full.