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

# Sign a document

Once you have added at least one signer to your document (see [Signers](https://doc.dastra.eu/en/features/contracts/signers.md)), you can manage its signature. Save the document first: as long as a change is not saved, the signature buttons are locked.

## Manual signature or Docusign

The **Add signature** window offers two modes:

* **Manual**: you declare that signers have signed. Select the signers whose signature you want to record, enter the **Signature date**, then click **Add signature**.
* **Sign with Docusign®**: Dastra sends the document for electronic signature and tracks its progress. This mode requires the [Docusign integration](https://doc.dastra.eu/en/features/contracts/docusign.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-880e411e6b4007c71fb066c0b2928c045ef1868c%2Fcontracts-sign-1.png?alt=media" alt="The Add signature window with the two modes, Manual and Sign with Docusign"><figcaption><p>The two signature modes</p></figcaption></figure>

When every signer has a signature, Dastra asks whether you want to publish the document. Confirm to set the document to the **Active** status.

## Open the signature window

There are three ways to open the signature window.

### Sign for one signer

In the **Signers - Signatories** tab, click **Add signature** on the row of the signer concerned.

### Sign for several signers

Click the arrow on the right of the **Add signer** button, then **Sign all - Apply all signatures**. You then select the signers for whom you record the signature.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-ec9b475a5caac245416af6cd7ecfeb0c5929ad46%2Fcontracts-sign-2.png?alt=media" alt="The Add signer button menu with the Sign all - Apply all signatures action"><figcaption><p>Sign for several signers from the Signers tab</p></figcaption></figure>

### Sign from the record

In the record, open the menu of the document row, then click **Add signature**. This action is disabled when all signers have already signed.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-ac91b675c749c0dd38fc4724fb5f60a75b21288e%2Fcontracts-sign-3.png?alt=media" alt="The menu of a record row with the Add signature action"><figcaption><p>Sign from the record</p></figcaption></figure>

## The signature button of the record

In the main actions menu of the record (see [Structure of a document](https://doc.dastra.eu/en/features/contracts/structure.md)), a button summarizes the state of the signatures. Its label changes with the number of signers and the number of signatures received.

### No signers

The button is disabled and shows **no signers**. Add signers to use 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-1ad184ae7b97a62e5df9d93ad9516105fc213950%2Fcontracts-sign-4.png?alt=media" alt="The disabled signature button with the label no signers"><figcaption><p>No signers</p></figcaption></figure>

### Signatures are missing

The button shows **Sign all - Apply all signatures** followed by the number of signatures received out of the number of signers. Click it to declare the missing signatures.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-62a611332c3d7363e97c1baf4c2ef0f60ce02413%2Fcontracts-sign-5.png?alt=media" alt="The Sign all - Apply all signatures button with the signature counter"><figcaption><p>Signatures are missing</p></figcaption></figure>

### Document signed by all signers

The button shows **Signed**. On hover, it becomes **Delete signature**: after confirmation, a click deletes the signatures if you need to redo them.

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-1879917dfbc07254f1640b2451552ec188518184%2Fcontracts-sign-6.png?alt=media" alt="The Signed button"><figcaption><p>Document signed by all signers</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/sign.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.
