Skip to main content
How-To

Add project files

Attach source files to a project so Joule can use the right references for related chats and outputs.

Last verified 3 days ago

Add project files when you have source material that should travel with a project: launch notes, research summaries, approved copy, product screenshots, slide decks, spreadsheets, PDFs, or brand references.

Project files work with the project brief. The brief tells Joule what matters; files give Joule source material to inspect when a later chat or task needs it.

Add files to a project

  1. Open Projects from the app sidebar.
  2. Open the project that should hold the files.
  3. Stay on the Context tab.
  4. In Uploaded Files, select Click to browse or drag files here.
  5. Choose one or more supported files.
  6. Review the Ready To Upload list.
  7. Select Save Changes.
Project file staged in the Ready To Upload list
Files staged in a project appear under Ready To Upload until you save the project changes.

Confirm the file is attached

After saving, the file appears under Already Uploaded. From there, you can open it or remove it from the project.

Project file attached in the Already Uploaded list
After saving, attached project files appear under Already Uploaded and can be opened or removed from the project.

Some files may show a preparing status while Ampere processes the file for project context. You can keep working while that finishes. If a file is not accepted, check the file type and size, then export it to a supported format and try again.

Supported project file types

Project files support these extensions: .txt, .md, .markdown, .mdx, .html, .htm, .rtf, .docx, .pptx, .xlsx, .pdf, .png, .jpg, .jpeg, .webp, and .svg.

The default per-file limit is 25 MiB. Legacy .doc and .ppt files are not accepted as project context files; export them as .docx, .pptx, PDF, or another supported format before uploading.

Only upload files your team is allowed to use for the project. If a file belongs in your broader organization knowledge base instead of one project, add it to the knowledge base rather than attaching it to a single project.

Was this article helpful?

Related articles