File source history and retagging
Every ingested file keeps source metadata — the automation that produced it, the Gmail message ID, the Drive file ID, the timestamp. You can change a file's category any time from Edit Case mode without losing that history.
Last updated
Every ingested file keeps source metadata — the automation that produced it, the Gmail message ID, the Drive file ID, the timestamp. You can change a file's category any time from Edit Case mode without losing that history.
Why source history matters
When something goes wrong — a file landed in the wrong case, an automation misfired, an unexpected attachment got ingested — the first question is where did this file come from?
For stream files, the metadata captures: which automation fired, the original Gmail message ID or Drive file ID, and the timestamp. With that you can:
- Trace back to the originating email or Drive file.
- Audit which automation processed which file.
- Correct an automation's filters after the fact.
- Prove provenance when downstream systems ask.
Changing a file's category
- Open the case and click Edit.
- In the Files section, each file has a category dropdown next to it.
- Pick the new category. The change is queued — click Save Changes at the bottom of the form to persist it.
The category change preserves all source metadata. Templates resolve by category ID, so the autofill picker updates to whatever templates consume the new category.