> 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/publico-editranff-v6.2-windows-en/usuario-de-onesait-ecosystems-editran-ff/operaciones-principales-sobre-los-ficheros/procedimiento-de-firma.md).

# Signing procedure

The signing task can be carried out from the branch “*Files to be signed*” of the tree or from the sub-branch with the name of the signing user hanging from the branch *Applications -> Purpose -> Application name.*

The file will only appear as available to the user

1. if it is part of any application to which the user is associated.
2. if it does not yet have the number of required signatures.
3. if it passes the validation check (signers' order, file amount, etc.).

The interface offers three ways to do it:

1. The “Operations” menu –> “File” -> “*Sign”.*
2. The second button on the toolbar ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/cvoZw6scO8QluBGvWsAi/image1.png) .
3. The context menu (right mouse button).
4. If the selected branch is “Files to be signed”, by double-clicking the file row in the list.

![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/rILizGdOGFyKehzZNwKy/image2.png)

The system will display the file content with the associated viewer in the dialog of the relationship between the user and the application.

All file viewers included in the system *Editran/FF* (see **6.1**) allow, in addition to signing, printing the entire file, a listing or a summary of it, or generating a PDF with the edited content.

![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/1WisczayiIEGLPtvxRfz/image3.png)

If the certificate with which it is going to be signed was installed with a high security level, if it is a card certificate, or if 5 minutes have elapsed since it was last entered, the PIN will be requested.

When the file is signed successfully, with the branch “*Files to be signed*”, the signed file disappears from the list. Conversely, if the signature is made while the logged-in user is selected under the branch *“Applications”,* the file will show its new status with respect to it, normally “*File signed successfully*” and the user's name will appear under the “*Signed by” column.*

![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/Ppo22VWvxVA4ayccnbNM/image4.png)

The signature file will be saved in the signatures directory specified in the application profile, with the extension corresponding to the chosen signature type, *.p7b* or .*xsig.*

If other users should then sign from the same interface of *Editran/FF User* the “*User -> Log in as another user*” menu will be selected, and the process described here will then be repeated.


---

# 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://docs.editran.onesait.com/documentacion-editran/publico-editranff-v6.2-windows-en/usuario-de-onesait-ecosystems-editran-ff/operaciones-principales-sobre-los-ficheros/procedimiento-de-firma.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.