> 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/alta-de-perfiles.md).

# Profile creation

To begin using the *AdminFF* it is necessary to set the directory where the Editran/FF profiles and log will be saved.

To do so, you must select the menu in the menu bar ***“Help->About AdminFF…”*** or click the button ![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/VmFcSUOUfJ7q7oqzd3ei/image1.png) on the taskbar.

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

In the field “*Editran/FF profile location*” the path to the directory where the profiles will be saved will be indicated. **This path must be accessible from each signing station** and will be stored in a file called “*path*” in the same directory as the AdminFF.exe executable. **The file “*****path”*****&#x20;must also be moved to the installation directory of each signing station.**

Whenever the contents of “*path*” the interface must be closed and reopened *AdminFF* to update the change.

**Once profiles have been added and/or modified, it is advisable to make a backup copy of the .cfg files found in the directory indicated in the file “*****path”.***


---

# 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/alta-de-perfiles.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.
