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

# Contracts and policies

Declare, sign and track your contracts, policies and other legal documents directly in Dastra.

The **Contracts & policies** module in Dastra lets you declare, edit, sign and version your legal and organizational documents: contracts, policies, notices and procedures. Each document is linked to the assets, stakeholders and users it concerns, so your commitments stay consistent with your record and your referentials.

## Access the module

Your subscription must include the contracts feature. If it is active in your plan, open **Operations** > **Contracts & policies** in the sidebar. The module has three entries:

* **Record of contracts & policies**: the list of your documents.
* **Reporting**: the indicators and charts of the module (see [Reporting](#reporting)).
* **Templates of contracts & policies**: the templates used to generate documents (see [Contract templates](https://doc.dastra.eu/en/features/contracts/templates.md)). This entry is hidden from users whose role is `User`.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-f9d8fe7e00b46c7bcc3962aad91ea3180c938473%2Fcontracts-readme-1.png?alt=media" alt="The sidebar with the Operations group open on Contracts &#x26; policies and its three entries"><figcaption><p>The Contracts and policies module in the sidebar</p></figcaption></figure>

## Document types

Each document has a type: **Contract**, **Policy**, **Notice**, **Procedure** or **Other**. You choose the type when you create the document (see [Create a document](https://doc.dastra.eu/en/features/contracts/declare.md)). To change it later, click the type badge next to the document title.

In the record, the **Types** filter limits the list to one or several types.

## The record of documents

The record lists your documents in a table whose columns you choose, for example the version, the number of signatures, the number of attachments and the deadline. Filters let you find a document by organizational unit, step, signature status, type, status, tag or user.

The **Create a document** button opens the creation wizard (see [Create a document](https://doc.dastra.eu/en/features/contracts/declare.md)). The arrow on its right opens the other actions of the module:

* **Import**: import several documents from a file.
* **Export**: export the list.
* **Set up regular review**: define how often documents are reviewed (see [Regular review of documents](https://doc.dastra.eu/en/features/contracts/review.md)).
* **Email-to-Document Integration**: create documents from the emails received at a collection address.
* **Read the documentation**: open this documentation.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-0091a0572490e3c8e55f627f07c2bcd95babdfe4%2Fcontracts-readme-2.png?alt=media" alt="The record of contracts and policies with the Create a document button menu open"><figcaption><p>The record and the actions of the Create a document button</p></figcaption></figure>

## Import and export

**Import** opens the import wizard for documents. It is available to users who have the import permission on contracts. The wizard is described in [Import your data (Excel, Csv)](https://doc.dastra.eu/en/features/general/import.md).

**Export** opens a window where you choose the format: CSV, XLSX, JSON, PDF, HTML, DOCX or Markdown. From the record, the export covers the list. From a document, the menu of the **Save changes** button offers **Export** for that document only, with the **Include documents** option to add its attachments.

## Create documents from your emails

The **Email-to-Document Integration** entry leads to the integration of collection email addresses. Once the address is created for contracts, each email received creates a document: the subject becomes the name, the body becomes the description, and valid attachments are added to the document. Installing the address requires the permission to manage integrations; it is described in [Incoming mail data collection](https://doc.dastra.eu/en/features/settings/mailboxes.md).

## Reporting

The **Reporting** entry gives an overview of your documents. The indicators at the top show the number of documents that are **Overdue**, the **Total**, the **Drafts** and the **Published** ones. Click an indicator to open the matching list.

The charts show:

* **New documents**: the change in the number of documents in the workspace and the number created on each date.
* **Signers**: the number of documents per signer.
* **Workflow stages**: the number of documents per workflow stage.
* **Tags**: the number of documents per tag.
* **Contracts & policies by areas**: the number of documents in each organizational unit, for each workflow stage.

The **Filters** button narrows the indicators and charts, and **Print** produces a printable version. The **Overdue** indicator relies on the deadline of your documents: fill it in on the **Details** tab (see [Details and attachments](https://doc.dastra.eu/en/features/contracts/documents.md)).

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-0bb1a94968da4098014483387ab3e5d880f469e7%2Fcontracts-readme-3.png?alt=media" alt="The Reporting page with the four indicators and the charts"><figcaption><p>The Reporting page of the module</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.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.
