> 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/usuario-de-onesait-ecosystems-editran-ff.md).

# Onesait Ecosystems · Editran/FF User

Once configured in *AdminFF* the user, application, and relationship profiles between them, and **once the computers from which the signatures will be made have the personal certificates installed that are associated with the signatories of each position**, users will be able to access the graphical interface *UserFF* to validate, view, and sign the files of the applications they are associated with, or simply check which files belong to that application and view them. Likewise, from *UserFF* they will be able to enable sending the applications for signing and accept the application signatures for verification.

On the next screen, the user will enter the name or alias of the user under which they were registered, and the system will request the PIN code for their certificate.

![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/odZcily2MJXU4l5BExIM/image1.png)

If there is more than one certificate associated with the user on the computer, a dialog will be shown where they must select one of them. If the certificate requires it, the PIN will then be requested.

Next, automatically:

* If it was configured in *AdminFF.exe*, the connection to the file server will be made.
* The XAdES service will be started if there is any application that will use any of its modes, and provided that XAdES/bin/start\_xades.bat is correctly configured (it is recommended to check XAdES/logs/out.log).

If the logged-in user is one of those configured in the profiles, an interface will be shown that again has two main branches.

* **Applications**: collects the applications to which the user is linked. This branch is dedicated to consultation. Double-clicking on an application in the tree displays the structure of the application, showing all its users and groups. The logged-in user is marked with a different icon from the other users. Selecting an application in the tree, the view on the right will show information for each user associated with it. On the other hand, selecting a group shows the parameters of the application–group relationship profile (number of mandatory signatures and number of permitted signatures), and selecting the user shows a list of the application's files and the signature status they are in.

![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/Wo7cFWevhh5QwLZUxgNe/image2.png)

If the user selected in the branch is the logged-in one, the file operations will be enabled in the menus. If the selected user is any other, only the status of their signatures with respect to each file of the application can be consulted.

* **Files to be signed**: this is the branch that appears selected by default, and it shows in the right panel the list of files from the different applications that the user can sign. Specifically, the view shows the file name, the name of the application it belongs to, the total amount of the file (in the formats where applicable), the aliases of the users who have already signed it, as well as those who have commented on it. The purpose of this branch is the viewing and signing of the files that are pending for the user. The signing process will be explained in more detail in the section **5.2.1.**

![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/dyyYB5hQgjkukmtryZI4/image3.png)


---

# 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/usuario-de-onesait-ecosystems-editran-ff.md?ask=<question>&goal=<user_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.