> 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-v3.1-en/firma/firmadeficheros/detallefichero/firmar.md). # Sign This option is available only to signer-role users who have signing permission in the *file group* to which the system has assigned the document. To be able to sign the files, it is essential that the computer from which the request is made have the corresponding private key certificate, properly installed or accessible (cloud certificate), within the system certificate store. The private key certificate used to sign will be the one corresponding 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 computer where the private key certificate is located. The desktop application **Editranff-Firma**, which must also be installed on the computer at the time of signing, is the one that performs this task. ## Installation of the desktop application on signing workstations The application installer can be downloaded by clicking the link **download it here** in the first window shown in each signing request. In this way, it will be saved in the browser's downloads folder. ![Download desktop application](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-d4c8f34fbc6265c9bec4948cb9e08ce044acf7c7%2F01_descarga_aplicacion_escritorio.png?alt=media) Alternatively, the system administrator can obtain the application 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 installer is on the signer’s computer (either because it has been downloaded or because it has been transferred manually), proceed as explained below. Installation requires administrator privileges on the computer. When the installer is run, a welcome screen is displayed in which the button must be clicked **Next**. ![Desktop application installation](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-a4d0c68fa8f00014119747f6afe9d82130634529%2F02_instalacion_aplicacion_escritorio.png?alt=media) Next, choose the installation directory: ![Desktop application installation directory](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%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 **Editran Connect Sign** service on the machine where Connect is deployed. ![IP and port of the Editran Connect Sign service](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-03d42b23d7140d0443fe26ae32660ddc49d11613%2F04_ip_puerto_instalacion_aplicacion_escritorio.png?alt=media) After clicking the button **Next**, the application will be installed. ![Desktop application installation completed](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%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 click the button **Sign** to begin the process. ![Sign button](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-cf6589f2cd6f252f9fbc81dde4b1ec4f03eb7940%2F06_boton_firmar.png?alt=media) In each signing request, a pop-up window will remind the user of the need to have the desktop application to sign and will provide the download link. This window can take two forms: 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. It will be the signer themselves who chooses at that moment which one they will use to sign. ![Sign with any certificate](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-5a0836381e9931eec0f3f7f8d3374626cb92868b%2F07_firmar_con_cualquier_certificado.png?alt=media) ![Certificate selection](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-6bdfa0adf615067dea5b0add817fefc8ffc9b2ad%2F08_selector_certificado.png?alt=media) By contrast, 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 show 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 details**. ![No certificate selector](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-1f695624ac6d2a313a1edf11ee5806efbd371e16%2F09_sin_selector_certificado.png?alt=media) In either case, once the button is pressed **Sign** in the window, a new window notifies that the Editranff-Firma desktop application is going to be used. Click **Open**. ![Desktop application usage notice](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-19fcb419ccb6f8cc387e3e2c20c2a4b30c05938a%2F10_aviso_uso_aplicacion_escritorio.png?alt=media) A new window appears that reports on the processes being carried out and, depending on the level of protection with which the certificate was installed, another one will open informing that the certificate is going to be used (medium level) or also requesting that its password be entered (high level, recommended level). ![Screen that reports the signing processes](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-c1334f645c86e02854121863eb03e5770a892700%2F11_pantalla_informa_procesos_firma.png?alt=media) ![Certificate password entry screen in the signing process](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-76aaaae423931dcd184c64cf5c6be695c3709e25%2F12_pantalla_introduce_contrase%C3%B1a_certificado.png?alt=media) Once that window is accepted, the signature will be performed and a final window will report whether the operation succeeded or failed. ![Signing process completed screen](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-51c977c19b304b786b3400bd141c839dd4e80981%2F13_pantalla_proceso_firma_finalizado.png?alt=media) The user is returned to the file list filtered by the status `Pending for me to sign`, so the file that was just signed will no longer be shown. However, if the user clears that filter, they can view the newly signed file and its overall and individual statuses 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-v3.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.