> 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.md).

# Files

Files are the documents, templates, source material, and durable knowledge that agents, tasks, and projects can use as context.

The user-facing workspace section is **Files**. Some older docs and technical surfaces may still use the term **artifact** for the same underlying object. In these docs, "file" is the product term and "artifact" is the platform object behind it.

**Location:** Main navigation -> Files

## What You'll Learn

**What Is a File Artifact** - How uploaded and generated files become reusable context.

**File Types** - The kinds of files Alludium can store, preview, and use.

**Uploading Files** - How to add files to your workspace or project.

**Managing Files** - How to search, sort, preview, select, and organize files.

**Linking Files to Agents** - How files become available to agent workflows.

**How Files Flow Through Workflows** - How files move between tasks, projects, and agents.

## Global Files And Project Files

Alludium has both workspace-level Files and project-specific file views.

**Workspace Files** are available from the main navigation. Use this area to upload, search, preview, and manage files across the workspace.

**Project Files** live inside a project. Use project files when the document belongs to a specific deal room, campaign, customer engagement, or other project workspace.

## Files Assistant

The Files area includes an assistant panel where available. It can help with file search, metadata review, and supported file inspection. The assistant only works with the file access and workspace state available to it.

## Why Files Matter

Agents and tasks work better when they can reference real source material instead of relying only on instructions. Files help teams:

* Reuse source documents and templates
* Keep supporting evidence close to the task or project
* Provide richer context to agents
* Reduce repeated prompt setup
* Preserve institutional knowledge across workflows


---

# 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.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.