> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/artifacts/at-project-level.md).

# At Project Level

### Overview

Project-level Artifacts store delivery material tied to a specific Project.

They support traceability from requirements and tasks to evidence and references.

### Key Concepts

* **Project scope**: content visible based on Project access
* **Evidence**: screenshots, exports, and reference files used for approvals
* **Traceability**: linking Artifacts to requirements, tasks, and tests

### How It’s Used

Use Project Artifacts for delivery-specific documents and evidence.

Such as design drafts, test evidence, and stakeholder-approved outputs.

### Benefits

* Cleaner audits through linked evidence
* Faster review cycles with consistent reference material
* Reduced context loss during handoffs

### Setup Steps

{% stepper %}
{% step %}

### Navigate to Project Artifacts

1. Open the Organization.
2. Open the Project.
3. Open **Artifacts** (or equivalent navigation label).
   {% endstep %}

{% step %}

### Create the Artifact

1. Select **Create artifact** (or **New artifact**).
2. Upload a file or add a link.
3. Enter a title that matches the delivery milestone or decision.
   {% endstep %}

{% step %}

### Link the Artifact to work items

1. Open the related requirement, task, or test case.
2. Add a link to the Artifact in the description or links area.
3. Add a comment with `Decision:` or `Approved by:` when the Artifact is approval evidence.
   {% endstep %}
   {% endstepper %}

### Best Practices

* Link Artifacts from requirements to preserve origin context.
* Keep evidence close to the work item that depends on it.
* Archive outdated drafts after a milestone is approved.

### Summary

Project-level Artifacts keep delivery evidence and references traceable to scope and execution 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.transform.ai/artifacts/at-project-level.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.