> 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/advanced-features/sign-and-flows/dynamic-number-of-signers.md).

# Manage a dynamic number of signers

Dynamically add the right number of signers to your document

In some cases, such as attendance sheets, the number of signers of a document is not known in advance.

{% hint style="info" %}
**Prerequisites — before you start**

* Have a Gonexa Sign document that works with 1 signer

**Tip**: Make sure to contact support if the licenses are not active for your environment
{% endhint %}

## Step 1: Configuration in Salesforce

* In your document template, make sure you have at least 1 recipient configured. If not, click New in the "Recipient" section
* In the child objects, make sure you have created a child object based on the standard Salesforce "Contact" object, which will be used to build the recipient list dynamically

## Step 2: Configuration in your document template

* Create a standard table with the columns of your choice and the desired 1st header row
* Keep 1 table column for the signature placeholder
* Add the following signature tag to this column: `{{signatures|index de départ|width|height}}`
* The starting index (index de départ) corresponds to the number of the 1st signer in the table.

{% hint style="success" %}
**Example**

If you only want signers in the table, simply set "1" as the starting index. If you have, for example, a trainer's signature followed by the list of trainees in the table, the starting number will be "2", because number 1 is the trainer, who is not in the table.
{% endhint %}

![Example of a dynamic signers table](https://662319530-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2NCR55D80zRSC5C7jbsg%2Fuploads%2Fy1m5r0aR2uO2UwNGFOMG%2Fsign-18.png?alt=media)

## Step 3: Sending for signature

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

Sending for signature can only be done via a Salesforce flow, since the number of signers is not known in advance and there may be a large number of signers
{% endhint %}

**Flow Org:**\
Find all the documentation on flows in our Flow Org


---

# 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/advanced-features/sign-and-flows/dynamic-number-of-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.