# Users

**Users** are created within an Account. Each User is assigned a specific Role on the “Roles” screen, which must be done before creating the User on the “Users” screen. A User can be assigned a specific Role or multiple Roles.

<table data-header-hidden><thead><tr><th width="51"></th><th></th></tr></thead><tbody><tr><td><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfULVh2I8ZLLI93Na4MtacqNRJq83fWlbfE6mb2yQrWIqk4AVRUlPsZzbxcQCeEJTVoVZrRGe7Tt1_1XKxES5tqkNaOjAIeGUxaEHrTcRnqmS3mCR6DweV1dDlvmnnqdr9ArLjWug?key=6sbXsIGaTS3XX9nMXq1GDfiN" alt="" data-size="line"></td><td>The User logging in from the Designer must have access rights to Processes. That is, if they do not have access rights to Processes in their Role, they will not be able to publish new scenarios from the Designer.</td></tr></tbody></table>

The Users screen contains the “Users” table:

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-e1fb69ea952f4472e9f679bf0510643c93fb9932%2F%D0%B8%D0%B7%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%B8%D0%B5%20(315).png?alt=media" alt=""><figcaption></figcaption></figure>

## **Creating a New User**

To create a new User, you need to click the “Create” button in the “Users” table and fill out the opened form:

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-76bf00a5e488d773b635931b94a9a811eb4b84b4%2F2025-04-22_16-47-43%20(1).png?alt=media" alt=""><figcaption></figcaption></figure>

<table data-header-hidden><thead><tr><th width="52"></th><th></th></tr></thead><tbody><tr><td><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfULVh2I8ZLLI93Na4MtacqNRJq83fWlbfE6mb2yQrWIqk4AVRUlPsZzbxcQCeEJTVoVZrRGe7Tt1_1XKxES5tqkNaOjAIeGUxaEHrTcRnqmS3mCR6DweV1dDlvmnnqdr9ArLjWug?key=6sbXsIGaTS3XX9nMXq1GDfiN" alt="" data-size="line"></td><td>When creating and/or editing a User, it is necessary to specify which authentication method to use for them.</td></tr></tbody></table>

The form for creating a new User offers three authentication options, which can be selected by setting a flag:

* Local authentication;
* LDAP authentication;
* OpenID authentication.

<table data-header-hidden><thead><tr><th width="54"></th><th width="205"></th><th width="287"></th></tr></thead><tbody><tr><td><strong>No.</strong></td><td><strong>Interface Element</strong></td><td><strong>Description</strong></td></tr><tr><td>1.</td><td>“Local” flag</td><td>Allows setting the local authentication option for the User.</td></tr><tr><td>1.1</td><td>“Login” text field</td><td>User's login. This field is required.</td></tr><tr><td>1.2.</td><td>“Password” text field</td><td>User's password. This field is required.</td></tr><tr><td>2.</td><td>“Use LDAP authentication” flag</td><td>Allows setting the User authentication option via LDAP.</td></tr><tr><td>2.1</td><td>“LDAP Users” field</td><td>Allows specifying an LDAP User using a dropdown list. This authentication option is available if the Orchestrator configuration contains data for connecting to the LDAP server. This field is available for LDAP authentication.</td></tr><tr><td>3.</td><td>“Use OpenID authentication” flag</td><td>Allows setting the User authentication option via OpenID.</td></tr><tr><td>3.1</td><td>“oAuth id” text field</td><td>OAuth identifier. This field is required. This field is available for OpenID authentication.</td></tr><tr><td>4.</td><td>“Email” text field</td><td>Email address for automatic message sending.</td></tr><tr><td>5.</td><td>“First Name” text field</td><td>User's first name.</td></tr><tr><td>6.</td><td>“Last Name” text field</td><td>User's last name.</td></tr><tr><td>7.</td><td>“Department” text field</td><td>Name of the department/location of the User's workplace.</td></tr><tr><td>8.</td><td>“Notify about messages from robots of the following types” flags</td><td><p>Allows the User<br>(when specifying an email address and setting flags for Robot message types) to receive automatically sent notifications to their email. Possible options:</p><ul><li>Critical;</li><li>Error;</li><li>Warning;</li><li>Notice;</li><li>Info;</li><li>Debug.</li></ul></td></tr><tr><td>9.</td><td>“Notify about audit messages of the following types” flags</td><td><p>Allows the User<br>(when specifying an email address and setting flags for Orchestrator message types) to receive automatically sent notifications to their email. Possible options:</p><ul><li>Critical;</li><li>Error;</li><li>Warning;</li><li>Notice;</li><li>Info;</li><li>Debug.</li></ul></td></tr><tr><td>10.</td><td>“Role” flags</td><td>Allows specifying a pre-configured Role (one or more), according to which access to Orchestrator screens and Actions on those screens (creation, editing, reading, and deleting objects) will be configured.</td></tr><tr><td>11.</td><td>“User is blocked” flag</td><td>Allows blocking the User.</td></tr><tr><td>12.</td><td>“Notify about license expiration to email” flag</td><td>Allows enabling the function to notify the User about license expiration via email.</td></tr></tbody></table>

## **Editing a Previously Created User**

To view and edit the properties of a specific User, you need to select them from the list and click the icon ![](https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-c896ddd3b4a74e8561a716a7ef28ca5c7164505d%2F2025-04-17_22-35-51.png?alt=media). After that, a form with the User's settings will open, where necessary changes can be made. There are no new fields in the previously created User.


---

# Agent Instructions: 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:

```
GET https://docs.sherparpa.ru/en/sherpa-rpa/sherpa-orchestrator/rabota-v-sherpa-orchestrator/ekrany/polzovateli.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.