> 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/administracionconnectfirma/grupoficheros/exportar_e_importar.md). # Export and import The purpose of exporting and importing *file groups* is to facilitate the configuration between Connect installations that exchange signed files. Specifically, this functionality streamlines the configuration process of the endpoint that will receive and verify the signatures that the other endpoint performs and sends to it since, by leveraging the configuration already set up at the signing endpoint, in a single step it is able to incorporate into the system the set of remote signers, with their respective public certificates, and *file groups* for verification purposes, with all the signer groups and signers it contains. The export and import process must be carried out as indicated below. **Endpoint that signs the files and sends the signatures** The signing endpoint selects in its list of *file groups* to sign all those that are related to the files it is going to send to the other endpoint. Then it clicks the icon ![Icono exortar](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-a5b62144b9ece62cbeec0b343312e9cc50d125ae%2F11_icono_exportar_gf.png?alt=media). The following window will be displayed: ![Export file group](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-76c7b0e15eeb1e21e3e15f024f49fa05c8505386%2F12_exportar_gf.png?alt=media) When **Export**is clicked, a ZIP file containing all the parameters of each signer is created and saved in the browser's downloads directory, and **file group** that the other endpoint needs to know in order to register the configuration with which it will receive and verify the files signed by this endpoint. If before clicking **Export** the **Send by email** to the other endpoint and the parameters are completed **Email**, **Subject** and **Body**, the file will be sent to the indicated email address. If the email sending parameters have not been specified on screen, an administrator of the installation with which the files are signed will send the export ZIP to one of the administrators of the installation that verifies the signatures. **Endpoint that receives the signatures and verifies them** Once the ZIP is received at the signature-receiving and verification endpoint, a signing administrator of this installation goes to their list of *file groups*, clicks the filter **Verify** and the button **Import**. A file search window is displayed on the computer, where the ZIP received from the other entity will be selected. When **Import**, all the **file groups** to sign that the other endpoint exported will be incorporated into the configuration as **file groups** to verify. In addition, all users with signer role that at the signing endpoint are related to those *file groups* exported, will be incorporated as remote signers, with their corresponding public key certificates included. ![Import file group](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-b1a56eecf1fb0b943cd3d07617b0b15f48a31f59%2F13_importar_gf.png?alt=media) 📌 **Things to keep in mind** > The configuration of each of those *file groups* to verify is not completed until the notification email is indicated, the output directory of the files extracted from the signature is defined, and, if desired, one or more users with controller role. The edit and delete operations of the *file groups* to verify that have been incorporated into the system through import are the same as those that can be performed with *file groups* created from **New Group**. --- # 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/administracionconnectfirma/grupoficheros/exportar_e_importar.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.