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

# Structure of a document

The elements that make up a document record in Dastra: title, actions, shortcuts, tabs and preview.

Once your document is created, Dastra opens its record (see [Create a document](https://doc.dastra.eu/en/features/contracts/declare.md)). The file preview takes the left of the screen and the input tabs take the right.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-e0d9f49eb51cd7734c3eded6b86693b85340589d%2Fcontracts-structure-1.png?alt=media" alt="A document record with the header, the preview on the left and the tabs on the right"><figcaption><p>A newly created document record</p></figcaption></figure>

## The title and the type

The editable title of the document is at the top left. The type badge (contract, policy, notice, procedure or other) appears above the title: click it to change the type.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-a1c0a1d9502331a0b752625712f2c97a368022d2%2Fcontracts-structure-2.png?alt=media" alt="The record header with the type badge, the title, the shortcuts menu and the action buttons"><figcaption><p>The type, the title, the shortcuts and the main actions</p></figcaption></figure>

## The shortcuts menu

Under the title, on the left, the shortcuts menu gives access to the elements associated with the document:

* internal discussions;
* associated tasks, if task management is active;
* the audit log, if audit is active, and the **Activity history** of the document;
* linked compliance tests, if the Compliance module is active (see [Details and attachments](https://doc.dastra.eu/en/features/contracts/documents.md));
* the regular review of the document (see [Regular review of documents](https://doc.dastra.eu/en/features/contracts/review.md)).

If you came from the record, arrows let you move from one document to another.

## The main actions

The main actions menu, at the top right, gathers:

* the **AI analysis (beta)** button: it opens the AI analysis of the document. This feature is in beta, it requires the AI analysis and AI agent features, and its results must be interpreted with caution;
* the signature button, whose label follows the state of the document (see [Sign a document](https://doc.dastra.eu/en/features/contracts/sign.md));
* the **Version** button followed by the version number, which opens the versions manager (see [Document versions](https://doc.dastra.eu/en/features/contracts/versions.md));
* the workflow stage selector;
* the **Save changes** button.

The arrow on the right of **Save changes** opens three actions:

* **Share**: create a sharing link for the document.
* **Export**: export the document (see [Contracts and policies](https://doc.dastra.eu/en/features/contracts.md#import-and-export)).
* **Move to recycle bin**: put the document in the recycle bin.

A document in the recycle bin carries the **Into recycle bin** badge. The same menu then offers **Restore** to put it back in the record, and **Delete** to delete it.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-d9bd795018575f960686956fe8435b792f16b063%2Fcontracts-structure-3.png?alt=media" alt="The Save changes menu open, with the Share, Export and Move to recycle bin actions"><figcaption><p>The actions of the Save changes button</p></figcaption></figure>

## The input tabs

Four tabs are displayed on the right of the screen. Their content changes when you switch from one to another:

* **Details**: the general information, the attachments and the custom fields (see [Details and attachments](https://doc.dastra.eu/en/features/contracts/documents.md)).
* **Signers - Signatories**: the parties who sign the document (see [Signers](https://doc.dastra.eu/en/features/contracts/signers.md)).
* **Assets**: the assets the document concerns (see [Assets](https://doc.dastra.eu/en/features/contracts/assets.md)).
* **Users**: the workspace users who work on the document (see [Linked users](https://doc.dastra.eu/en/features/contracts/users.md)).

Except for **Details**, each tab shows in brackets the number of items it contains.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-b1e5afb17c3435bdfca0f5b2212f331ee423b0ed%2Fcontracts-structure-4.png?alt=media" alt="The four tabs Details, Signers - Signatories, Assets and Users"><figcaption><p>The tabs of a document record</p></figcaption></figure>

## The attachments preview

The area on the left previews the files of the document: the contract or policy and any appendices. It stays displayed whichever tab is open. When the document has no file yet, it offers to drop a file or write a policy.


---

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