> For the complete documentation index, see [llms.txt](https://alludium.gitbook.io/alludium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alludium.gitbook.io/alludium-docs/5.-artifacts/5.2-artifact-types.md).

# File Types

Different files serve different jobs in Alludium. Classifying them clearly makes agents easier to configure and makes project work easier to review later.

**Location:** Main navigation -> Files

***

## Templates and Examples

Templates show the structure an agent should produce. Examples show what good completed work looks like.

Use these for:

* Memo formats.
* Email and message examples.
* Report outlines.
* Proposal templates.
* Completed examples that demonstrate tone, level of detail, or structure.

Best practice: include at least one completed example when output quality depends on style, formatting, or judgement.

***

## Source Documents

Source documents are the material an agent should read, analyze, summarize, or transform.

Use these for:

* Meeting notes and transcripts.
* Contracts, policies, or playbooks.
* Research reports.
* Data room documents.
* Client or company background material.

Best practice: keep source files narrowly scoped. A smaller set of relevant files usually produces better results than a large folder of mixed material.

***

## Reference Data

Reference data gives agents a consistent factual base.

Use these for:

* CSV exports.
* Market maps.
* Account lists.
* Scoring rubrics.
* Structured lookup tables.

Best practice: prefer structured files such as CSV, XLSX, or clean tables when the agent needs to compare records or extract fields.

***

## Project Files

Project files belong to a specific project rather than the whole workspace. They can include inputs, intermediate work, and final outputs.

Use these for:

* Project briefs.
* Uploaded customer or deal material.
* Generated drafts that need review.
* Supporting evidence gathered during project tasks.

Best practice: keep project files attached to the project when they are part of that project's audit trail or handoff.

***

## Choosing the Right Place

Use this quick guide:

| Material                                | Best home              |
| --------------------------------------- | ---------------------- |
| Reusable company style guide            | Global Files           |
| One-off document for a single chat      | Chat upload            |
| Project brief or project-specific input | Project Files          |
| API credential or OAuth access          | Integration connection |
| Standing behavior rule                  | Agent instructions     |

***

## Next Step

Continue to **Uploading Files** to add material to the workspace or to a project.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://alludium.gitbook.io/alludium-docs/5.-artifacts/5.2-artifact-types.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.