> 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.5-linking-artifacts-to-agents.md).

# Linking Files to Agents

Uploading a file makes it available in Alludium, but it does not mean every agent automatically uses it. Link or select files deliberately so agents receive the right context for their job.

***

## Why Linking Matters

Explicit linking keeps agent context focused:

* Agents only use files relevant to their purpose.
* Large or conflicting documents do not dilute the prompt.
* Builders can review exactly which references shape an agent's output.
* Shared agents do not accidentally inherit unrelated workspace material.

***

## How to Link Files

The exact UI can vary by agent type and workspace configuration, but the pattern is consistent:

1. Upload the file through **Files** or the relevant project.
2. Open the agent in **Agent Builder**.
3. Go to the configuration area for files or context.
4. Add the relevant file.
5. Save and test the agent.

If the agent is already deployed, test the updated configuration before relying on it for production work.

***

## Selecting Multiple Files

Agents can use multiple files when the references serve different purposes.

Good combinations:

* One template plus one completed example.
* A policy document plus a checklist.
* A project brief plus supporting source documents.
* A scoring rubric plus a dataset.

Avoid linking multiple files that give conflicting instructions. When conflict is unavoidable, state the priority order in the agent instructions.

***

## Reusing One File Across Agents

A reusable file can support many agents.

Examples:

* A brand voice guide used by several content agents.
* A diligence framework used by deal-screening and memo agents.
* A customer support policy used by triage and response agents.

When you update a shared reference file, test the agents that depend on it. One file change can affect several workflows.

***

## Testing Linked Files

After linking files, run test prompts that prove the agent is using them:

* Ask for output in the linked template format.
* Ask a question whose answer appears only in the linked file.
* Compare output against the expected example.
* Check that the agent ignores unrelated files.

If outputs do not reflect the file, confirm the file finished processing, is linked to the correct agent, and does not conflict with the prompt.

***

## Next Step

Continue to **How Files Flow Through Workflows** to understand how files are used across tasks, projects, agents, and automated work.


---

# 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.5-linking-artifacts-to-agents.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.