> 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.1-what-is-an-artifact.md).

# What Is a File Artifact

A **file artifact** is a durable file stored in Alludium so agents, tasks, and projects can use shared context instead of relying on one-off uploads or repeated instructions.

In the product UI, this area is labelled **Files**. Older internal names and older URLs may still use "artifact", but user-facing documentation should say **Files** unless it is explaining the underlying concept.

**Location:** Main navigation -> Files

***

## What Files Are For

Files give Alludium persistent reference material:

* Templates and examples that show the expected output shape.
* Source documents that agents need to read, summarize, compare, or transform.
* Style guides, policies, checklists, and team standards.
* Project-specific inputs that belong with a project rather than a single chat.
* Supporting material produced during a workflow and reused by later work.

Files are most useful when the same information should be available again later, to another task, another agent, or another team member.

***

## Files vs. Other Inputs

**Files vs. system instructions**

System instructions define how an agent should behave. Files provide the reference material the agent should use.

Example:

* Instruction: "Write in our investment memo format."
* File: The actual memo template and completed examples.

**Files vs. chat uploads**

Chat uploads are useful for a single conversation. Files are persistent and can be reused across future work.

Example:

* Chat upload: A one-off report you want summarized now.
* File: A standing diligence framework used by every investment analysis task.

**Files vs. integrations and tools**

Integrations and tools let agents retrieve data or perform actions in external systems. Files provide the internal context that shapes how the agent uses that data.

Example:

* Tool: Search CRM records.
* File: The qualification criteria that determine which records matter.

***

## Global and Project Files

Alludium uses files in two common scopes:

* **Global workspace files** for shared templates, standards, and reusable references.
* **Project files** for material tied to a specific project or project task.

Use global files for durable institutional knowledge. Use project files for inputs and outputs that belong to a project timeline.

***

## What Files Are Not

Files are not a safe place for secrets. Do not upload API keys, passwords, private credentials, or anything that should only live in a secure connection.

Files are also not executable code. Agents can read and reason over supported file contents, but uploaded files do not run as scripts inside Alludium.

***

## Next Step

Continue to **File Types** to decide which material belongs in Files and which should stay as a chat upload, instruction, integration, or project note.


---

# 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.1-what-is-an-artifact.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.