Attachments
Attachments are files added to a specific chat or note context. They are useful for quick analysis, visual context, or one-off material that does not need the full source pipeline.
Attachments are different from sources. A source becomes part of the project library and can support search, citations, summaries, and maps. An attachment helps the current workflow.
Where attachments appear
| Surface | Attachment role |
|---|---|
| Chat | Add files or images that should inform the current answer. |
| Notes | Preserve screenshots, figures, diagrams, or visual evidence next to written notes. |
| Source workflows | Prefer source import when the material should become reusable project evidence. |
Use attachments for
- screenshots you want to ask about once
- figures or images that clarify a note
- small supporting files for a single question
- drafts or snippets that are not part of the permanent research corpus.
Use sources instead for
- PDFs you will cite later
- articles, papers, websites, or videos that should be searchable
- material that should appear in project-wide retrieval
- evidence that should support knowledge maps or summaries.
Attachment boundaries
An attachment can help Atlas interpret the immediate context, but it should not be treated as a fully indexed source unless the product explicitly imports it as one.
For durable research evidence, import the material as a source first, then ask questions against that project context.
Decision table
| Attachment use | Best for |
|---|---|
| Chat attachment | Temporary analysis in one conversation. |
| Note image | Visual context attached to written interpretation. |
| Source import | Searchable, citable, reusable project evidence. |
| Unsupported file | Convert to a supported source or attach only for limited context. |