# Robots

**Robots** are instances of the Sherpa RPA platform software deployed on specific user workstations, virtual machines, and terminal servers, connected for management to the Orchestrator. Robots can be grouped into Robot Groups. One Robot can be included in multiple Groups.

For more flexible management of a Robot's access to various resources, the same Robot can be assigned to process different Task Queues across different Processes.

The "Robots" screen contains two tables: "Robot Groups" and "Robots".

The "Robot Groups" table includes the following information:

<table data-header-hidden><thead><tr><th width="169"></th><th></th></tr></thead><tbody><tr><td><strong>Column Name</strong></td><td><strong>Description</strong></td></tr><tr><td>Name</td><td>Contains the name for the Robot Group.</td></tr><tr><td>Description</td><td>May include information about the Processes that the Robots in the Group perform or the scenarios in which they are used.</td></tr><tr><td>Access Folder</td><td>Indicates the Access Folder to which the Robot Group belongs. The Access Folder serves as a means of access control, allowing only those Users whose Roles provide access to interact with the Robot Group. Thus, the Access Folder not only controls who can see and manage the Robot Group but also ensures data security by creating a clear structure of User rights.</td></tr></tbody></table>

The "Robots" table includes the following information:

<table data-header-hidden><thead><tr><th width="187"></th><th></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td><strong>Description</strong></td></tr><tr><td>Robot Active</td><td>Indicates the current activity status of the Robot. It allows you to understand whether the Robot is currently active or disabled, and also to manually change the activity status using the toggle <img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXffE6ZX5LFvW0ZelBpvfpGHGl2crsINoGtpGjE9RkAB26-JCstrYCuaw0IZ_hd3sgb-fovEUNUWuPnxW778j-qmgLm_eWANJJghaWHyocAO2cpJ8xbHoFyLJflzHgEAsmpmK4Vd9A?key=7eRqoaatii1RYxZsI15sTcHF" alt="">. It is important to note that changing this status does not physically turn off the Robot on the remote machine; it simply informs the Orchestrator that no Tasks should be assigned to this Robot. This frees the Robot from performing tasks but does not affect its functioning or availability to the system.</td></tr><tr><td>Name</td><td>Contains the name of each Robot.</td></tr><tr><td>Status</td><td><p>Contains the state of each Robot, including the following values:</p><ul><li>Disconnected;</li><li>Ready;</li><li>Working;</li><li>Unlicensed.</li></ul></td></tr><tr><td>Type</td><td>Contains the type of Robot, defining its capabilities and purpose. Includes values: “Attended”, “Unattended”, “Coordinator”.</td></tr><tr><td>Description</td><td>Contains additional information about the Robot, such as its purpose, operational features, or configuration details.</td></tr><tr><td>License Expiration</td><td>Indicates the expiration date of the License required for the Robot to function correctly.</td></tr><tr><td>License</td><td>Contains data about the type of License used by each Robot in this group.</td></tr><tr><td>Last Communication</td><td>Indicates the date when the last data exchange occurred between the Robot and the server.</td></tr><tr><td>Access Folder</td><td>Indicates the Access Folder to which the Robot belongs. The Access Folder serves as a means of access control, allowing only those Users whose Roles provide access to interact with the Robot. Thus, the Access Folder not only controls who can see and manage the Robot but also ensures data security by creating a clear structure of User rights.</td></tr></tbody></table>

Each column can be [pinned, resized, or filtered](https://docs.sherparpa.ru/en/sherpa-rpa/sherpa-orchestrator/rabochaya-oblast-orkestratora#deistviya-s-dannymi-tablic-ekranov-orkestratora) by clicking on the icon ![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXe-8-ms7cwjBWoQqIzUtlBtNGPD95zMEWOQYdi_8xL_KuzlDvk8DDKMyaoNS8DQjp-8ZqTVqYYv02ruqnVoXvpkvvLicSmUasJ623oNejvyMHRLXvVlCFmBpJgDTV8tpHSmYiUX?key=7eRqoaatii1RYxZsI15sTcHF).

You can also sort the rows of the table in ascending/descending order based on the values in the selected column by clicking on the empty area of the corresponding header. This allows for quick and convenient organization of data in the desired order.

## **Creating a New Robot**

To create a new Robot, you need to click the "Create" button in the "Robots" 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-aa18a7f149dc35f7ae40d405c2d1852e8a370848%2Fimage%20(201).png?alt=media" alt=""><figcaption></figcaption></figure>

<table data-header-hidden><thead><tr><th width="49"></th><th></th></tr></thead><tbody><tr><td><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdUbbixgI5adNj0Hu6Yrqsjb3eCW28i2418RwSVZZAJVSpO7DBYPF-5d_PQrDx5T0Hr-3DAUGdgzza3-J5Q3t7doFA0JETNuOHILx3jWsc2TnbM8lhho8h2vWpdKJklxGuxLa7h5g?key=Xplr0gVoyx3tqpkkXjZLx1lq" alt="" data-size="line"></td><td><strong>If the "Role" field is left blank and saved, the flag will default to the "Attended" Role.</strong></td></tr></tbody></table>

### **Creating an Attended Robot**

**Attended Robots** are Robots that are manually launched on the User's computer, from startup, by a keyboard shortcut, or on a schedule from the [Windows Task Scheduler](https://docs.sherparpa.ru/en/sherpa-rpa/sherpa-designer/nastroika-zapuska-robota-cherez-planirovshik-windows).

For Attended Robots, it is sufficient to specify a display name and select the License used by the Robot [License](https://docs.sherparpa.ru/en/licenzii).

<table data-header-hidden><thead><tr><th width="56"></th><th width="264"></th><th></th></tr></thead><tbody><tr><td><strong>No.</strong> <strong>p/p</strong></td><td><strong>Interface Element</strong></td><td><strong>Description</strong></td></tr><tr><td>1.</td><td>“Robot Active” toggle</td><td>An enabled toggle indicates that the Robot is active on the Orchestrator side. If the toggle is in the "Robot Inactive" position, a command to turn off this Robot will be sent to the Orchestrator upon request.</td></tr><tr><td>2.</td><td>“Name” text field</td><td>The name of the Robot. This field is mandatory.</td></tr><tr><td>3.</td><td>“Attended Role” flag</td><td>The Role of the Robot.</td></tr><tr><td>4.</td><td>“Description” text field</td><td>Description of the Robot.</td></tr><tr><td>5.</td><td>“Access Folder” text field</td><td>Allows specifying the Access Folder for the created Robot.</td></tr><tr><td>6.</td><td>“License” field</td><td><p>Allows selecting the type of License for the Robot. Available options:</p><ul><li>Local license;</li><li>Attended License added to the Orchestrator and assigned to a specific Robot.</li></ul></td></tr><tr><td>7.</td><td>“Create Job on Local Robot Launch” flag</td><td>Allows automatically creating a Job when the Robot is launched locally from Sherpa Assistant.</td></tr></tbody></table>

### **Creating an Unattended Robot**

**Unattended Robots** are Robots launched by the [Coordinator](#sozdanie-koordinatora). The Coordinator starts Robots if there is a Job for them on the "Jobs" screen. A Job can be created manually, by Trigger, or via API.

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-2367dcaf317090b8cde8d0fc5bbd013802bb7080%2F2025-04-17_20-57-08.png?alt=media" alt=""><figcaption></figcaption></figure>

<table data-header-hidden><thead><tr><th width="54"></th><th width="266"></th><th></th></tr></thead><tbody><tr><td><strong>No.</strong> <strong>p/p</strong></td><td><strong>Interface Element</strong></td><td><strong>Description</strong></td></tr><tr><td>1.</td><td>“Robot Active” toggle</td><td>An enabled toggle indicates that the Robot is active on the Orchestrator side. If the toggle is in the "Robot Inactive" position, a command to turn off this Robot will be sent to the Orchestrator upon request.</td></tr><tr><td>2.</td><td>“Name” text field</td><td>The name of the Robot. This field is mandatory.</td></tr><tr><td>3.</td><td>“Unattended Role” flag</td><td>The Role of the Robot.</td></tr><tr><td>4.</td><td>“Machine<br>(IP address or domain name)” text field</td><td>The IP address of the terminal server or virtual machine where this Robot is deployed.</td></tr><tr><td>5.</td><td>“Domain (if any) and account login in the format domain\username” text field</td><td>The domain name of the terminal server or virtual machine where this Robot is deployed or the account login (if necessary including the domain) under which the Robot should run.</td></tr><tr><td>6.</td><td>“Account Password” text field</td><td>The password for the user account under which the Robot should run.</td></tr><tr><td>7.</td><td>“Login and Password from Resource” text field</td><td>Allows specifying the login and password from the selected Resource for this Robot.</td></tr><tr><td>8.</td><td>“Remote Debugging” checkbox</td><td>Indicates that the Robot will run in remote debugging mode through Sherpa Designer.</td></tr><tr><td>9.</td><td>“IP address of the Designer machine for remote debugging” text field</td><td>The IP address of the machine where Sherpa Designer is located, through which the Robot will run in remote debugging mode.</td></tr><tr><td>10.</td><td>“Remote Debugging Server” text field</td><td>The server where remote debugging of this Robot will take place.</td></tr><tr><td>11.</td><td>“Coordinator” text field</td><td>The instance of the Coordinator that will be used to launch this Robot.</td></tr><tr><td>12.</td><td>“Description” text field</td><td>Description of the Robot.</td></tr><tr><td>13.</td><td>“Access Folder” text field</td><td>Allows specifying the Access Folder for the created Robot.</td></tr><tr><td>14.</td><td>“License” text field</td><td><p>Allows selecting the type of License for the Robot. Available options:</p><ul><li>Local license;</li><li>Unattended License added to the Orchestrator and assigned to a specific Robot.</li></ul></td></tr></tbody></table>

### **Creating a Coordinator**

**Coordinator** is a service used to launch Unattended Robots in user accounts where automatic login to Robot Accounts is required. It is installed from the corresponding Sherpa Coordinator distribution provided by the vendor and does not require a separate License. More about the Coordinator and its installation can be found in the section on [Coordinator](https://docs.sherparpa.ru/en/sherpa-rpa/sherpa-orchestrator/razvertyvanie-platformy-pod-upravleniem-orkestratora/ustanovka-sherpa-rpa-coordinator).

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

<table data-header-hidden><thead><tr><th width="56"></th><th width="265"></th><th></th></tr></thead><tbody><tr><td><strong>No.</strong> <strong>p/p</strong></td><td><strong>Interface Element</strong></td><td><strong>Description</strong></td></tr><tr><td>1.</td><td>“Robot Active” toggle</td><td>An enabled toggle indicates that the Robot is active on the Orchestrator side. If the toggle is in the "Robot Inactive" position, a command to turn off this Robot will be sent to the Orchestrator upon request.</td></tr><tr><td>2.</td><td>“Name” text field</td><td>The name of the Coordinator. This field is mandatory.</td></tr><tr><td>3.</td><td>“Coordinator Role” flag</td><td>The Role of the Coordinator.</td></tr><tr><td>4.</td><td>“Description” text field</td><td>Description of the Coordinator.</td></tr><tr><td>5.</td><td>“Access Folder” text field</td><td>Allows specifying the Access Folder for the created Robot.</td></tr></tbody></table>

To save the created Robot, after filling out the form, you need to click the "OK" button. The Robot will be created.

## **Editing a Previously Created Robot**

### **Editing a Previously Created Attended Robot**

To view and edit the properties of a specific Robot, you need to select it from the list and click the button ![](https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-a9308c6b65bcecb20a053a25924cb0614f2b60d8%2Fimage%20\(220\).png?alt=media). After that, a form with the settings of the selected Robot will open, where you can make the necessary changes. In addition to the fields filled out when creating a new Robot, the edit form has additional settings.

<table data-header-hidden><thead><tr><th width="52"></th><th width="213"></th><th></th></tr></thead><tbody><tr><td><strong>No.</strong> <strong>p/p</strong></td><td><strong>Interface Element</strong></td><td><strong>Description</strong></td></tr><tr><td>1.</td><td>“GUID” text field</td><td>A unique identifier assigned to the Robot after its creation. This field cannot be edited.</td></tr><tr><td>2.</td><td>“Status” text field</td><td><p>Status of the Robot. Possible options:</p><ul><li>Disconnected;</li><li>Ready;</li><li>Working;</li><li>Unlicensed.</li></ul><p>This field cannot be edited.</p></td></tr><tr><td>3.</td><td>“IP” text field</td><td>The IP address of the terminal server or virtual machine where this Robot is deployed. This field can be edited only for Unattended and Attended Robots.</td></tr><tr><td>4.</td><td>“MAC” text field</td><td>The MAC address of the terminal server or virtual machine where this Robot is deployed. This field can be edited.</td></tr><tr><td>5.</td><td>“License Expiration” text field</td><td>The expiration date of the License. This field cannot be edited.</td></tr><tr><td>6.</td><td>“License Key” text field</td><td>The license key of the Robot. This field can be edited.</td></tr><tr><td>7.</td><td>“Created” field</td><td>The date and time the Robot was created. This field cannot be edited.</td></tr><tr><td>8.</td><td>“Updated” field</td><td>The date and time the current Robot record was updated in the Orchestrator. This field cannot be edited.</td></tr><tr><td>9.</td><td>“Last Communication” field</td><td>The date and time of the Robot's last communication. This field cannot be edited.</td></tr></tbody></table>

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-08d1a55c3b2a81563ef794acc5c60872e14b93c2%2F%D0%A0%D0%B5%D0%B4%D0%BA%D1%82%D0%A0%D0%B0%D0%BD%D0%A1%D0%BE%D0%B7%D0%B4Att%D0%A0%D0%BE%D0%B1%D0%BE%D1%82.png?alt=media" alt=""><figcaption></figcaption></figure>

### **Editing a Previously Created Unattended Robot**

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-d26c2e365fa1f8fd6591fda2fff7f2d37cc9411f%2F2025-04-17_21-08-04.png?alt=media" alt=""><figcaption></figcaption></figure>

<table data-header-hidden><thead><tr><th width="53"></th><th width="197"></th><th></th></tr></thead><tbody><tr><td><strong>No.</strong> <strong>p/p</strong></td><td><strong>Interface Element</strong></td><td><strong>Description</strong></td></tr><tr><td>1.</td><td>“GUID” text field</td><td>A unique identifier assigned to the Robot after its creation. This field cannot be edited.</td></tr><tr><td>2.</td><td>“Status” text field</td><td><p>Status of the Robot. Possible options:</p><ul><li>Disconnected;</li><li>Ready;</li><li>Working;</li><li>Unlicensed.</li></ul><p>This field cannot be edited.</p></td></tr><tr><td>3.</td><td>“IP” text field</td><td>The IP address of the terminal server or virtual machine where this Robot is deployed. This field can be edited only for Unattended and Attended Robots.</td></tr><tr><td>4.</td><td>“MAC” text field</td><td>The MAC address of the terminal server or virtual machine where this Robot is deployed. This field can be edited.</td></tr><tr><td>5.</td><td>“License Key” text field</td><td>The license key of the Robot. This field can be edited.</td></tr><tr><td>6.</td><td>“Created” field</td><td>The date and time the Robot was created. This field cannot be edited.</td></tr><tr><td>7.</td><td>“Updated” field</td><td>The date and time the current Robot record was updated in the Orchestrator. This field cannot be edited.</td></tr><tr><td>8.</td><td>“Last Communication” field</td><td>The date and time of the Robot's last communication. This field cannot be edited.</td></tr></tbody></table>

### **Editing a Previously Created Coordinator**

<figure><img src="https://3237142148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FscP4BXwl9ufpJr5mfVln%2Fuploads%2Fgit-blob-cc12ced4434b073bae78c3a560fdb227ee4d439a%2F2025-04-17_21-16-30.png?alt=media" alt=""><figcaption></figcaption></figure>

<table data-header-hidden><thead><tr><th width="56"></th><th width="211"></th><th></th></tr></thead><tbody><tr><td><strong>No.</strong> <strong>p/p</strong></td><td><strong>Interface Element</strong></td><td><strong>Description</strong></td></tr><tr><td>1.</td><td>“GUID” text field</td><td>A unique identifier assigned to the Robot after its creation. This field cannot be edited.</td></tr><tr><td>2.</td><td>“Status” text field</td><td><p>Status of the Robot. Possible options:</p><ul><li>Disconnected;</li><li>Ready;</li><li>Working;</li><li>Unlicensed.</li></ul><p>This field cannot be edited.</p></td></tr><tr><td>3.</td><td>“IP” text field</td><td>The IP address of the terminal server or virtual machine where this Robot is deployed. This field can be edited only for Unattended and Attended Robots.</td></tr><tr><td>4.</td><td>“MAC” text field</td><td>The MAC address of the terminal server or virtual machine where this Robot is deployed. This field can be edited.</td></tr><tr><td>5.</td><td>“Created” field</td><td>The date and time the Robot was created. This field cannot be edited.</td></tr><tr><td>6.</td><td>“Updated” field</td><td>The date and time the current Robot record was updated in the Orchestrator. This field cannot be edited.</td></tr><tr><td>7.</td><td>“Last Communication” field</td><td>The date and time of the Robot's last communication. This field cannot be edited.</td></tr></tbody></table>

## Creating a New Robot Group

The "Robot Groups" table allows grouping Robots together, combining them into logical groups.

For example, if necessary, you can create a Group for working within a specific terminal server, assign it a name, and add the corresponding Robots to it.

To display the list of Robots in the "Robots" table, you first need to select the required Robot Group.

The "All Robots" Group lists all available Robots present in the Orchestrator. It is created automatically and cannot be deleted.

When selecting the desired Robot Group, the lower "Robots" table will display a list of all Robots belonging to the selected Group, including the Robot with Coordinator functionality (for Unattended Robots).

<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_4nXdQp1pOQhWN7LzJuCN_Q2c_Ya2mZlrqHwN2ALYQoFJ44BcSlIGIRIkZNZmtmuJZYuvQjhd6vc1MMJNQ8lEF4U415Xl3N3jPI6bIL3o-DOc9q5yEmznax4whuWKiDW3nti0EhmbYBw?key=6sbXsIGaTS3XX9nMXq1GDfiN" alt="" data-size="line"></td><td><strong>The Coordinator is always in an active state, indicated by a green indicator. This service ensures the creation and maintenance of user account sessions for Unattended Robots within the used terminal server.</strong></td></tr></tbody></table>

All other Robots are technical accounts running on the same terminal server.

To create a new Robot Group, you need to click the "Create" button in the "Robot Groups" table and fill out the opened form: specify the name of the Robot Group (mandatory), the description of the Robot Group, and the Access Folder. To save the created Robot Group, after filling out the form, you need to click the "OK" button. The Robot Group will be created.

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

## **Editing a Previously Created Robot Group**

To view and edit the properties of a specific Robot Group, 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-690447737878822a051c1768d4d44828fa21d624%2F2025-03-19_21-36-15.png?alt=media) ("Edit").

After that, a form with the settings of the selected Robot Group will open, where you can make the necessary changes.

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

In addition to the fields filled out when creating a new Robot Group, the edit form has an additional field:

“**Record GUID**” – this is a unique identifier assigned to the Robot Group after its creation. 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/roboty.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.