> 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-v2.1-en/firma/firmadeficheros/detallefichero/firmar.md). # Sign This option is available only to signer-role users who have signing permission on the *file group* to which the system has assigned the document. In order to sign files, it is essential that the device from which the request is made has the corresponding private key certificate, properly installed or accessible (cloud certificate), within the system certificate store. The private key certificate used to sign will correspond to one of the public key certificates that the signer has configured in their Connect profile. On the other hand, for the signature to be considered secure, it must be performed on the device where the private key certificate is located. The desktop application **Editranff-Firma**, which must also be installed on the device at the time of signing, is the one that performs this task. ## Installation of the desktop application on signing workstations The application's installer can be downloaded by clicking the link **download it from here** in the first window displayed on each signing request. This way, it will remain in the browser's downloads directory. ![Download desktop application](https://64653979-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvdpBggYaSLH9X3nOAiMG%2Fuploads%2Fgit-blob-d4c8f34fbc6265c9bec4948cb9e08ce044acf7c7%2F01_descarga_aplicacion_escritorio.png?alt=media) Alternatively, the system administrator can obtain the application's installer from the directory `[Connect installation directory]\EditranConnect\signs\app` of the Connect installation on the server to install it on each signing workstation. Once the application's installer is on the signing device (either because it was downloaded or transferred manually), proceed as explained below. Installation requires administrator privileges on the device. When the installer is run, a welcome screen is shown in which the **Next**. ![Installation of the desktop application](https://64653979-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvdpBggYaSLH9X3nOAiMG%2Fuploads%2Fgit-blob-a4d0c68fa8f00014119747f6afe9d82130634529%2F02_instalacion_aplicacion_escritorio.png?alt=media) Next, choose the installation directory: ![Desktop application installation directory](https://64653979-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvdpBggYaSLH9X3nOAiMG%2Fuploads%2Fgit-blob-1a167ff3f5033bc6c288e344f062f78c4b8302a2%2F03_dir_instalacion_aplicacion_escritorio.png?alt=media) And finally indicate the server (ip/hostname, without https\://) and the listening port of the service **Editran Connect Sign** of the machine where Connect is deployed. ![IP and port of the Editran Connect Sign service](https://64653979-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvdpBggYaSLH9X3nOAiMG%2Fuploads%2Fgit-blob-03d42b23d7140d0443fe26ae32660ddc49d11613%2F04_ip_puerto_instalacion_aplicacion_escritorio.png?alt=media) After pressing the **Next**, the application will be installed. ![Desktop application installation completed](https://64653979-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvdpBggYaSLH9X3nOAiMG%2Fuploads%2Fgit-blob-cbdd9ddb85b22bd61cf04d1bbec60873d803d1f4%2F05_terminada_instalacion_aplicacion_escritorio.png?alt=media) ## Signing process Once the signer accesses the file details and, if applicable according to format and permissions, has viewed it, they will press the **Sign** button to begin the process. ![Sign Button](https://64653979-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvdpBggYaSLH9X3nOAiMG%2Fuploads%2Fgit-blob-cf6589f2cd6f252f9fbc81dde4b1ec4f03eb7940%2F06_boton_firmar.png?alt=media) In each signing request, a popup will remind the need to have the desktop application to sign and will provide the download link. This window can have two appearances: If in the configuration of the signer's participation in the file group it was indicated that they can act with any of their certificates (none was selected specifically), the window offers the signer the set of certificates associated with their user profile in Connect. The signer will choose at that moment which one to use to sign. ![Sign with any certificate](https://64653979-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvdpBggYaSLH9X3nOAiMG%2Fuploads%2Fgit-blob-5a0836381e9931eec0f3f7f8d3374626cb92868b%2F07_firmar_con_cualquier_certificado.png?alt=media) ![Certificate selection](https://64653979-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvdpBggYaSLH9X3nOAiMG%2Fuploads%2Fgit-blob-6bdfa0adf615067dea5b0add817fefc8ffc9b2ad%2F08_selector_certificado.png?alt=media) On the other hand, if in the configuration of the signer's participation in the file group it was indicated that they must act with a specific certificate, this window does not offer the list of certificates. In this case, the signer can find out which certificate they must use by checking the information in the view itself **File detail**. ![No certificate selector](https://64653979-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvdpBggYaSLH9X3nOAiMG%2Fuploads%2Fgit-blob-1f695624ac6d2a313a1edf11ee5806efbd371e16%2F09_sin_selector_certificado.png?alt=media) In any case, once the **Sign** button in the window is pressed, a new window notifies that the Editranff-Firma desktop application will be used. Press **Open**. ![Notice of use of the desktop application](https://64653979-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvdpBggYaSLH9X3nOAiMG%2Fuploads%2Fgit-blob-19fcb419ccb6f8cc387e3e2c20c2a4b30c05938a%2F10_aviso_uso_aplicacion_escritorio.png?alt=media) A new window appears informing about the processes being carried out and, depending on the protection level with which the certificate was installed, another window will open informing that the certificate will be used (medium level) or also requesting the entry of its password (high level, recommended level). ![Screen informing about the signing processes](https://64653979-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvdpBggYaSLH9X3nOAiMG%2Fuploads%2Fgit-blob-c1334f645c86e02854121863eb03e5770a892700%2F11_pantalla_informa_procesos_firma.png?alt=media) ![Certificate password entry screen in the signing process](https://64653979-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvdpBggYaSLH9X3nOAiMG%2Fuploads%2Fgit-blob-76aaaae423931dcd184c64cf5c6be695c3709e25%2F12_pantalla_introduce_contrase%C3%B1a_certificado.png?alt=media) After accepting that window, the signature will be performed and a final window will report the success or failure of the operation. ![Screen signing process completed](https://64653979-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvdpBggYaSLH9X3nOAiMG%2Fuploads%2Fgit-blob-51c977c19b304b786b3400bd141c839dd4e80981%2F13_pantalla_proceso_firma_finalizado.png?alt=media) The user is returned to the file list filtered by the `Pending signatures for me`, so the file that has just been signed will no longer be displayed. However, if the user unchecks that filter, they can view the newly signed file and its overall status and its specific status with respect to each signer, if they wish. From the file list, the signer can repeat the described process with the rest of the files that are still pending their action. --- # 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-v2.1-en/firma/firmadeficheros/detallefichero/firmar.md?ask=&goal= ``` `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.