> For the complete documentation index, see [llms.txt](https://university.gonexa.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.gonexa.fr/sign/en/getting-started/build-sign-template/place-signatures.md).

# Place one or more signatures in the document

From your document template configuration, go to the Sign tab

## Settings for adding signers

* From your document template configuration, go to the Sign tab
* In the Signers component, click "New" to add a signer

{% hint style="danger" %}
**Warning**

This button is greyed out if you have not selected a signature level. Refer to step 1
{% endhint %}

* Enter the following information:

**Type:**\
Role of the signer, used to identify them (e.g. Customer, Supplier, Partner, etc.)

**Default contact:**\
The field that references the default contact

**Contact search filter:**\
Lets you limit the list of signer contacts

Example: Find the contact on Prospect accounts

```
Account.Type = 'Prospect'
```

**Signer display filter:**\
This filter lets you hide a signer type when your business process does not require it.

Example: Show if the Supplier Signature box is checked

```
SignatureFournisseur__c = 'true'
```

You can also use a custom query, for example to only show the contacts of the quote's account

* In this case, choose "Custom Query" as the contact search filter
* Then enter a SOQL query

For example:

```
AccountId IN (Select AccountId from Quote where Id = {recordid})
```

![Adding a signer to the template](https://content.gitbook.com/content/fJiC57rqLAtDo49GS6QB/blobs/Uh4YPwH0CsDTGoUZjaNJ/43-03-placer-une-ou-plusieurs-signatures.gif)

## Add the signature placeholders

* Go to the Gonexa Doc document template where you want to place the signature(s)
* Open the assistant using the Go to tags button
* Access the different signer types in the "Add a signature" block
* Click a signer to copy the signature tag and paste it into your document where you want it

{% hint style="danger" %}
**Warning**

The signature tag looks like this: `{!s1}`

Make sure the signature tag is not split across two lines. It must remain complete!
{% endhint %}

![Adding a signature placeholder in the document](https://content.gitbook.com/content/fJiC57rqLAtDo49GS6QB/blobs/pCGUFng6ORNODPpqsXpX/44-04-ajout-emplacement-signature.gif)


---

# 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://university.gonexa.fr/sign/en/getting-started/build-sign-template/place-signatures.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.