> 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/administrador-de-onesait-ecosystems-editran-ff/barras-de-menu-y-herramientas/menu-administrador.md). # "Administrator" Menu ## 4.1.1.1 General settings ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/ZEwelxvM2E4W6cuwFvYv/image1.png) Selecting this menu will display the dialog: ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/oIND9BlztndU7qOxGq2P/image2.png) **Tab “*****Miscellaneous”*** * **First automatic signature:** by checking this option, an initial signature will be performed immediately on each new file in the applications directory, provided that: 1. The application has associated a user of type “*Local*” with the attribute *“Automatic signer”.* 2. The Editran/FF service is running. 3. If the application's signing mode is XAdES, the service *Editran Signature* *Services.* This signature will always be performed first and automatically, therefore **the certificate associated with the automatic signer must have been installed without enabling secure private key protection.** Until this first signature is produced, no other signing user associated with the application will be able to access the files to sign them. Once this signature has been performed, any modification to the data file would be detected by the product, showing this signature as incorrect, so using this functionality provides a security mechanism for the information to be signed. * **EditranFF Server/Service Port:** if the EditranFF server or service is to be used (for performing the first automatic signature, sending warning emails about files available to be signed to the corresponding users, submissions with Editran version 5.2.1 and later, etc.), the port on which it should be started will be indicated here. By default, 8300 is used. * **Editran submissions directory:** this directory is used for sending the files with Editran. When all files of an application reach the number of signatures required (according to the profiles) and all of them are correct, the set of application files (data files, signature files and enablement files, if applicable) will be moved automatically to a subdirectory under this one whose name will be that of the application. This directory and its subdirectories must be accessible from the signing stations (just like the data and signatures directory) since the move will be triggered from one of them. To use this functionality, it is necessary to select in the tab *Sending* of the application configuration dialog at least Data or Signatures, otherwise the files will not be moved. Once the application files are in the corresponding subdirectory under this one, Editran version 5.2.1 and later will send only those of the type selected in the configuration. **When this directory is modified, the value of the submission directories of all applications in which some type of files is marked in the tab *****Sending***** of the application configuration dialog** (see **4..2.2**, Directories). **Tab “*****Email sending”*** ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/Z7NunEOLgFLv3VAzpDLR/image3.png) * **Automatic email sending from services:** this parameter allows enabling the sending of notification emails about new files to sign to all users who have pending files to sign. Only users who have configured an email address in their profile will receive this notification and only if the Editran/FF service is running on the server machine. In addition, it allows sending error emails from the Editran/FF services to the email configured in each application's profile. Since it is performed from a Windows service, this functionality can only be provided under SMTP, so if enabled, the parameters in the box “*SMTP server* *configuration*” on the same tab must be filled in. * **Email sending from the signing stations:** this parameter allows enabling email sending from *UserFF*, both between the users themselves and for task notifications that Editran/FF reports in the email configured in the application. If enabled, one of the following must be selected: *“Use Microsoft Outlook client*”: the Microsoft Outlook client must be installed and correctly configured. or *“Use standard SMTP server*”: in this case, the parameters in the box “*SMTP server configuration*” on the same tab must be filled in. * **SMTP server configuration:** contains all the parameters needed to send emails via SMTP. All fields are mandatory and must always be filled in whenever you want to enable “*Sending* *automatic email sending from services*” and/or *“Email sending from the signing stations”* with *“Use standard* *SMTP server*”. The password for authentication is stored encrypted. The “*Check SMTP*” button sends an email, with the indicated parameters, to the sender's same address, which makes it possible to confirm whether the indicated values are correct. **Tab “*****Connections to servers”*** ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/TH30PJO1ohzvbTQXkTND/image4.png) This tab contains all the parameters required so that access from the signing stations, both to the server hosting the profile files and to the one containing the files to be signed and the signatures, can be carried out automatically and transparently for the signing users. If the profile files and the files to be signed are going to be on the same server, the check “*Common server for the* *configuration files and files to be signed*” will be checked and the “*Files-to-be-signed server*” column will be disabled. In this case, a directory that the other two depend on will be indicated, as well as a user who has read, write and execute permission in those directories. The connections established are to: ***\\\IP*** *or DNS name\Shared resource or directory* with the user: *User domain\User* and the *Password for authentication* The “*Check connection*” button allows confirming that the indicated values are correct. Once “*Save*” is pressed, two . files will be generated.*cfg* in the directory indicated in the file “*path*”. The file *cnx.cfg* must be copied into the Editran/FF installation directory of each of the signing stations from which *UserFF.exe.* If the parameters on this tab are not configured, the connection to the servers must be made manually from each signing station. ## 4.1.1.2 Exit Selecting this menu will close the interface *AdminFF* of Editran/FF --- # 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/administrador-de-onesait-ecosystems-editran-ff/barras-de-menu-y-herramientas/menu-administrador.md?ask=&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.