# Accounts **Accounts** are separate spaces within the Orchestrator, each having its own set of Jobs, Processes, Resources, Robots, Queues, and Users. Accounts are completely isolated from each other: regarding Robots, Processes, and other objects. With Accounts, the Orchestrator can be divided into several logical, unrelated areas (for example, by departments), and maintain separate accounting and usage of all objects for each of them. Accounts represent isolated spaces for storing Orchestrator entities, access to which is provided by the User's login and password.


	Accounts within the Orchestrator are not Users. A separate screen “Users” is provided to define User rights.

Often, two Accounts are used to divide the Orchestrator and the Robots it manages into those used for testing purposes (test road) and those engaged in real business tasks. With a small number of Robots to perform current Tasks, one account is usually sufficient. The “Accounts” screen contains the “Accounts” table:

## **Creating a New Account** To create a new Account, you need to click the “Create” button in the “Accounts” table and fill out the opened form:

The new Account creation form offers three authentication options, from which you can select the desired one by setting a flag: * Local authentication; * LDAP authentication; * OpenID authentication.


No.	Interface Element	Description
1.	“Local” flag	Allows setting the local authentication option for the Account.
1.1	“Login” text field	Account login. This field is required.
1.2.	“Password” text field	Account password. This field is required.
2.	“Use LDAP authentication” flag	Allows setting the authentication option for the Account via LDAP.
2.1	“LDAP Users” field	Allows specifying an LDAP User using a dropdown list. This authentication option is available if the Orchestrator configuration contains connection data for the LDAP server. This field is available for LDAP authentication.
3.	“Use OpenID authentication” flag	Allows setting the authentication option for the Account via OpenID.
3.1	“oAuth id” text field	oAuth identifier. This field is required. This field is available for OpenID authentication.
4.	“Company” text field	The name of the company where the Account will be created.
5.	“Department” text field	The name of the department, workplace, or location of the Account.
6.	“Administrator's First Name” text field	The first name of the Account administrator.
7.	“Administrator's Last Name” text field	The last name of the Account administrator.
8.	“Administrator's Email” text field	The email address of the Account administrator.
9.	“Phone” text field	The phone number of the Account administrator.
10.	“Can create accounts” flag	Allows granting the Account the right to create other Accounts.
11.	“Can create partner accounts” flag	Allows granting the Account the right to create partner Accounts.
12.	“Time zone” field	Allows selecting a time zone for the Account.
13.	“Language” field	Allows selecting a language for the Account. Possible options: Russian; English.

## **Editing a Previously Created Account** To view and edit the properties of a specific Account, you need to select it 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 Account settings will open, where you can make the necessary changes. In addition to the fields filled in when creating a new Account, the editing form has an additional field “API Key” (a unique code used for authentication when working with the Orchestrator API). This field cannot be edited.

--- # 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/akkaunty.md?ask= ``` 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.