> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/contracts/assets.md).

# Assets

In the **Assets** tab, link to your document the assets it concerns: software, equipment, data or any other physical or intangible resource involved in carrying out the document. You track the resources covered by each contract or policy.

The assets come from your [repositories](https://doc.dastra.eu/en/features/mapping/repositories.md). To link one, click **Add asset**, select the asset in your referential, then click **Add**. The tab shows in brackets the number of linked assets.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-87a0c9787661052195e29588051e9840d5eae807%2Fcontracts-assets-1.png?alt=media" alt="The Assets tab of a document with a linked asset and the Add asset button"><figcaption><p>Link assets to a document</p></figcaption></figure>

If the selected asset has an editor, Dastra points it out and offers to add it as a signer of the document: tick the box to add it together with the asset.

## Find documents from an asset

The documents linked to an asset also appear on the asset record, where the contracts button shows their number. From this button you can link an existing document with **Link to a document**, or create one with **Create a document**.


---

# 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://doc.dastra.eu/en/features/contracts/assets.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.
