> 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/apply-electronic-seal.md).

# Apply an electronic seal

Seal the authenticity of your digital documents with the electronic seal solution

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

* Gonexa Sign installation and configuration
* Creation of a Gonexa Sign document template with a signature placeholder
* Have the Gonexa Sign Admin permission set
* Have at least package version 2.5
* Have subscribed to the electronic seal feature
  {% endhint %}

## What is an electronic seal?

The **electronic seal** is a form of digital authentication that commits the identity of a **legal entity** (company, organization, institution), unlike the **electronic signature**, which commits a **natural person**.

In other words:

* It is the digital version of a company's stamp or seal.
* It is generally applied at the end of the process, once all signers have validated the document.

Using an electronic seal is particularly relevant for documents issued on behalf of an organization: invoices, attestations, standard contracts, certificates, etc.

## Step 1: Prepare the document template

* Create a document template in Gonexa Doc.
* Add a **recipient** and insert a **signature placeholder** into the document.
* Make sure the document is properly configured for signing via Gonexa Sign.

## Step 2: Create a Salesforce flow

* In Salesforce Setup, create a new flow.
* Add the Apex action named: **"Seal Content Version"**.
* In the **Content Version Id** parameter, specify the **variable that will contain the ID of the signed document version** (an essential prerequisite).

## Step 3: Save and activate the flow

* Save and activate the flow.
* When it runs, the system will automatically apply an electronic seal to the relevant document.
* The **"Seal Id"** field will then be populated on the content version record, confirming that the document has been electronically sealed.

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

* Always check that the content version used corresponds to a **finalized signed document** before applying the seal.
* You can automate adding the seal at the end of a **signature process** to avoid any manual intervention.
  {% 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/advanced-features/sign-and-flows/apply-electronic-seal.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.