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

# Details and attachments

The **Details** tab of a document record gathers the document information and its attachments. The file preview stays on the left whichever tab is open.

## Attachments

Add to your document the files that make it up: the contract itself, amendments, appendices or any other related file. To get the preview, store PDF files or images.

Drop the files in the drop zone, or click **File explorer** to choose them. If you installed the [OneDrive & SharePoint / Google Drive integration](https://doc.dastra.eu/en/features/settings/cloud-storage.md), a source selector lets you attach files from your own storage.

Attachment storage is linked to Dastra's [document management](https://doc.dastra.eu/en/features/files.md) module. Users who manage attachments can move a file to the common file manager with **Move to common file manager**, then open it from the document with **View in file manager**.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-a891eb0bd67e9d68355dec0f2aabf4e875107001%2Fcontracts-documents-1.png?alt=media" alt="The Details tab of a document with the drop zone, the source selector and the File explorer button"><figcaption><p>Add attachments to a document</p></figcaption></figure>

## Preview a document

The preview is on the left and the list of attachments on the right. To change file, click its name in the list, click the on-screen arrows or use the left and right arrow keys of your keyboard. The previewed file is highlighted in blue in the list. You can also rename the previewed file by clicking its name above the preview.

Because the preview stays visible on the **Signers - Signatories**, **Assets** and **Users** tabs, you can refer to the document while you fill in those tabs.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-33e4c68b0b5e5a086d4045ffdc45fa4e4279be93%2Fcontracts-documents-2.png?alt=media" alt="The preview of a document on the left and the Details tab on the right"><figcaption><p>Previewing a document</p></figcaption></figure>

## Document information

The **Details** tab contains the following fields:

* **Area**: the organizational unit the document is attached to.
* **Tags**.
* **Start date** and **Deadline**.
* **Description** and **Internal reference**.
* The custom fields defined for contracts in your workspace.

The deadline drives the follow-up of your due dates: a document past its deadline appears in the **Overdue** indicator of the **Reporting** page (see [Contracts and policies](https://doc.dastra.eu/en/features/contracts.md#reporting)), and a warning is displayed in the tab.

## Linked compliance tests

When a document is used as **evidence** for a test in the Compliance module, this link is visible directly from the document. An icon shows the **number of linked compliance tests**; clicking it opens the list of those tests. Clicking a test displays its details without leaving the document page.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-0974f0805c7440e6e88d577817f5f1505a2a948e%2Fconformite-liens-preuve-contrats.png?alt=media" alt="Icon showing the number of compliance tests linked to a contract"><figcaption><p>The icon shows the number of linked compliance tests; a click opens the list and then the test details without leaving the contract</p></figcaption></figure>


---

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