> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/connect-3.2-en/firma/administracionconnectfirma.md).

# Connect Signature administration

The use of the Connect Firma module requires certain configuration, and this section explains how to carry it out. In addition, the different locations where the module's events are recorded (Activity Log and log files) and other functionalities and information that users with the signature administrator role should know will be identified.

Before continuing, it is worth remembering that, in general, at the start of a signing process there is a single file, while at the end there are two.

When the process corresponds to the **carrying out a signature**, at the beginning there is only a data file—the one to be signed—and at the end, in addition to that file, another is generated that contains the signatures made. The file with the signatures made usually includes the data file that has been signed, although that depends on the mode or format and subformat of signature used.

When the process is the **verification of a signature**, depending on the signature mode or format used:

Case 1 - At the beginning there is a single file --the one that was received-- which contains the data file and the signatures, but at the end of the process there are two: the one that arrived through the channel and the data file, which is extracted from the received signature file. This is the most common case and the one for the signature modes and submodes that are implemented in this version of Connect.

Case 2 - Two files are received: the one that was signed and the signature file. This case is typical of signature modes and submodes in which the signature file does not include the signed file and therefore the same two files exist from the beginning to the end of the verification process.

In Connect, the data file and its corresponding signature file share the same name, differing only by the added extension (.p7b or .xsig) in the signature files.

📌 **Important**

> The product administrator must take this peculiarity of the file pair in signing processes into account. This behavior differs from that of the *channels* and non-signature-related submissions, where a single file remains from the beginning to the end of the process.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.editran.onesait.com/documentacion-editran/connect-3.2-en/firma/administracionconnectfirma.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.