> 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/configure-sign/choose-signer-interface-version.md).

# Choose the signer interface version

As of version 2.61, released in June 2026 (Biarritz), a new version of Gonexa Sign is available.

For **existing customers**, you are free to choose the version that best fits your needs, based on the features you want and the experience you wish to offer signers. Switching to the new Gonexa interface is optional.

Note: any new document template you create will be associated with the default signer configuration you have previously activated. This configuration does not apply retroactively to existing templates, so an additional step will be required for them.

For **new customers**, meaning new installations, follow the installation steps for option 2. All your new document templates will be associated with the default signer configuration.

{% hint style="info" %}
Make sure to contact support if the licenses are not active for your environment: [Contact support](/university/en/support.md)
{% endhint %}


---

# 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/configure-sign/choose-signer-interface-version.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.