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

# Setting up Sign followers

Add a follower to keep them informed of the progress of signature procedures.

{% hint style="info" %}
**Prerequisites**

* Gonexa Sign installation and configuration
* Creation of a Gonexa Sign document template with a signature placeholder
* Have the Gonexa Sign Admin permission set to configure interactions
* Have at least package version 2.2
  {% endhint %}

## Why add followers

A follower lets contacts other than the signer be informed that a document has been sent for signature and view it. No action is expected from the follower; they simply follow the signing process

### What is a related document?

Related documents let you add one or more documents after a main document at generation. These documents can be added with or without conditions. They depend on the main document and cannot be generated on their own.

## Set up followers on the document template

* From your document template, go to the "Sign" tab
* In the "Followers" component, click Configure
* Enter the following information:

**Follower email template ID**: Salesforce ID of the email template used to send emails to followers

**Allow followers to be added**: This checkbox allows followers to be added when sending for signature

**Contact search filter**: This filter lets you limit the list of follower contacts

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

Only search for contacts whose title is Director
{% endhint %}

![Setting up followers on the template](https://content.gitbook.com/content/fJiC57rqLAtDo49GS6QB/blobs/jG6H6iYDEls0zyRi1E6b/50-01-configurer-suiveurs.gif)

## Add a follower

* Still in the "Followers" component, click New to add a follower
* Enter the following information:

**Type**: Role of the follower, used to identify them\
Example: Sales Director

**Default contact:** The field that references the contact who will be the default follower, when the "Allow followers to be added" box is unchecked

**Follower display filter**: This filter lets you show or hide this follower type

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

Sales Director (`DirecteurCommercial__c`), and select this follower only if a criterion is met on the context
{% endhint %}

When the document is generated, the send-for-signature component displays the default follower chosen previously, and lets you add other followers if needed

![Adding a new follower](https://content.gitbook.com/content/fJiC57rqLAtDo49GS6QB/blobs/vMFB741491JJxfLxxJAb/51-02-ajouter-nouveau-suiveur.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/advanced-features/followers.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.