Files and permissions
You can add a file to a conversation without storing its original contents in the Gateway.
Attach a local file
- Select the intended Agent and start its Worker.
- Use + → Add files in the conversation.
- Review the material permissions shown for the selected destination.
- Add the file and tell the Agent what you want done with it.
The original is placed in that profile's local Worker material area. The conversation carries a reference and descriptive metadata. Adding an attachment does not itself make the model read the contents or certify the claims in the document.
An authorized Action must make material available before the Agent can read it. The installed capability determines the available actions, supported formats and evidence requirements. In the published document workflow, configure the Source's material delivery permissions in Document assistant → Prepare local assistant. Console's Source binding editor is not a general material-permission editor in this release.
Where the data goes
| Data | Location or recipient |
|---|---|
| Original attached file | Local Worker material area |
| Material reference, identity and access metadata | Governed service records |
| Text approved for a remote model | The configured model service |
| Facts, Action results and Case evidence | The Board and its records |
| A draft explicitly saved to your account | Private draft storage in the service |
In the Rulith workbench, permitted material reads go directly to the local Worker. A third-party Agent can use the Gateway to relay a permitted read from the Worker. A reference does not guarantee availability: the Worker must be reachable and retain the material.
Local files do not mean a local model. When you use a remote model, authorized text can leave the computer for that provider. Drafts and quoted passages can also become part of the governed work. Choose material accordingly.
Permission and evidence are different
Material delivery permission controls whether content may be read and where it may be delivered. A Source's evidence tier controls which claims it can support.
A document or user answer can provide a clue. An authorized Source may attest what it observed. Neither a file attachment nor a model's interpretation automatically becomes an attested business conclusion.
Changing the model destination does not transfer a file's previous disclosure permission. Follow the workbench's prompts before sending conversation history or material to a different service.
Keep material available
Keep the original file area and the Worker available while a task needs them. A Case receipt can describe an artifact without being a backup of its bytes. If material is removed or the Worker is offline, a later read may be unavailable.
For the supplied document-to-draft workflow, see Document to draft.