> 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/ibm-editran-v5.3-iseries-en/editran-ff/graphical-interface/user-management/add-users.md).

# Add users

Users of the Local type associated with an Editran/FF application of the Issuance – XAdES type can sign the application files, as allowed by the profiles with the registered group and/or user relationships. Likewise, if the application is of the Reception – XAdES type, a local user associated with it will be able to access that program to consult/verify the application. Users are associated with a session. There are two types of users:

Local: Own users

<figure><img src="https://2621858476-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F80nfuaOloGPZthms7LSJ%2Fuploads%2Fgit-blob-d0670ead592b3f9e049bdab8fb7966781204bd83%2Fimage%20(135).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2621858476-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F80nfuaOloGPZthms7LSJ%2Fuploads%2Fgit-blob-3624f98f72f55ef1ff7f8ff5aab9f9a482b4f8ac%2Fimage%20(136).png?alt=media" alt=""><figcaption></figcaption></figure>

These fields are:

* Type: The type of user. In this case it will always be local and it is the one that will sign the files to be issued
* Local entity: Editran local entity code
* User: The name by which the user will be identified.

In the case of performing multiple signatures, it may be required to be a signature or countersignature.

* Certificate alias: this is the alias of the user certificates.
* Keystore path: where the user certificates with private key are stored

Remote: Users from other entities

<figure><img src="https://2621858476-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F80nfuaOloGPZthms7LSJ%2Fuploads%2Fgit-blob-b532b52071d52f06fec8497da81fb3cbe3d11ab7%2Fimage%20(137).png?alt=media" alt=""><figcaption></figcaption></figure>

These fields are:

* Type: The type of user. In this case it will always be local and it is the one that will sign the files to be issued
* Local entity: Remote entity code
* User: The name by which the user will be identified.

In the case of performing multiple signatures, it may be required to be a signature or countersignature.

* Remote certificate identification:

- [x] DN where the user certificates with private key are stored.


---

# 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/ibm-editran-v5.3-iseries-en/editran-ff/graphical-interface/user-management/add-users.md?ask=<question>&goal=<endgoal>
```

`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.