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

# Signers

{% hint style="info" %}
The signer of a document is generally a natural or legal person **referenced as a stakeholder in Dastra**.
{% endhint %}

In the **Signers - Signatories** tab, specify the parties who must sign the document.

A signer is a stakeholder from your [repositories](https://doc.dastra.eu/en/features/mapping/repositories.md). To add one, click **Add signer**, select the stakeholder, then click **Add**. If the stakeholder does not exist yet and you can write to the referentials, you can create it from the same window. The tab shows in brackets the number of signers.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-43f195d8bf9c30dd530e5a4573852df995590609%2Fcontracts-signers-1.png?alt=media" alt="The Signers tab with signers whose signature is recorded, pending or missing"><figcaption><p>The signers of a document</p></figcaption></figure>

If the selected stakeholder is linked to assets, Dastra offers to link them to the document automatically: tick the assets to add.

Each signer shows their email address, or the **Stakeholder doesn't have an e-mail address** warning when it is missing, and the state of their signature: **No signature**, **Pending signature** or **Signed on** followed by the date. You can manage the signature of each signer independently (see [Sign a document](https://doc.dastra.eu/en/features/contracts/sign.md)).

As for assets, the record of each stakeholder lists the documents they are associated with.


---

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