> 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/listado_ficheros.md). # File list Again, in this view the buttons **Sign** and **Verify** in the upper-right corner allow filtering the list of files corresponding to *file groups* of either purpose. ![File list](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-143fbb84f62dd6ab5b8f5523e5f45d36c6eef0cc%2F02_listado_ficheros_pendientes_firmar_por_mi.png?alt=media) The accessing user can see only the files corresponding to the *file groups* in which they are involved (either as local signer, as controller, or as administrator and signature controller). The list shows the file names, their overall signature status, the application indicated in the definition of the file group, the highest transaction amount, the total amount, and, if the accessing user has the signer role, the certificate with which they must sign. Also, if you expand the symbol (![Consulta de firmantes](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-3a1a5dab26fadee2dfe0a5be158695fb38cbacec%2F05_icono_consulta_firmantes_gf.png?alt=media)) to the left of the name, you can view the file's signature status for each of the signers involved in the *file group* that applies to the selected document. The overall signature status of a file can be one of the following: * **Pending signature**: the file does not yet have all the required signatures according to those established in the *file group*. * **Signed**: the file has all the required signatures according to those established in the *file group*. * **Pending sending**: the file has all the required signatures according to those established in the *file group* and the type of file to be sent defined in the *file group* (data, signature, or data and signature) is in the channel's send directory. * **Sent**: the file has all the required signatures according to those established in the *file group* and the type of file to be sent defined in the *file group* (data, signature, or data and signature) that is in the channel's send directory has already been sent by Connect. The signature status of a file with respect to a user can be: * **Cannot sign**: users who belong to the *file group* but do not have permission to sign the documents or whose role is controller or administrator and signature controller). * **Pending to sign**: users who can sign the document at the time of the query. * **Cannot sign yet**: users who can sign the document but must wait for others to sign first, so they cannot sign at the time of the query. * **Their signature is not required**: users who have permission to sign the document but do not need to because other people in their same signer group have already signed, or because the required number of signatures of the *file group*. * **Signed**: users who have already signed the document at the time of the query. * **Countersigner**: user who must countersign other users' signatures. The check **Pending for me to sign** appears checked when accessing the menu **Files**. In this way, the signing task is made easier, since only the documents that require action from the signer are shown. By unchecking the filter **Pending for me to sign**, the signer can view all documents related to their *file groups*, regardless of their current status: * Documents pending signature by the user. * Documents that have already been signed by them. * Documents in which their signature is not necessary, because other members of the group have already signed them. * Documents pending sending. * Documents already sent. * Withdrawn documents (those showing the information icon to the left of their name). ![File list](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-5453c48300a9018a9265abd8ff40e2535f65520e%2F03_listado_ficheros_todos.png?alt=media) Using the button **Filters** it is possible to refine the list of files according to the following data: * **Purpose**: sign or verify * **Application**: category that groups together a set of file groups or signing rules. * **Electronic certificate**: certificate with which the files must be signed. This filter is only available for the sign purpose. * **File group**: name of the *file group*. By clicking on the icon (![Detalle del fichero](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-3b23b0a14ecf9d7432234763be2923319e763d60%2F02_icono_detalle_gf.png?alt=media)) you access the view **File details** from which multiple operations are performed such as viewing the file, signing, withdrawing or recovering documents, removing the signature, hash lookup, and others that will be seen in detail below. --- # 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/listado_ficheros.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.