# Licenses
**Sherpa RPA License** is the key to the legal use of software Robots in Users' workplaces. To activate Licenses, it is necessary to confirm their legality, which occurs through the transmission of computer information to the vendor. License keys are sequences of letters and numbers that define the number and type of Robots.
### Types of Robot Licenses
There are several types of Licenses, including:
* **Attended** — The Robot is manually launched to solve specific tasks on the User's personal computer. It is launched from Sherpa Designer and used for development. It can be connected to Sherpa Orchestrator. It is tied to the account (not the personal computer) of a specific User (**1 License key for 1 Robot**).
* **Attended Floating** — The Robot is manually launched to solve specific tasks on the User's personal computer. It is launched from Sherpa Designer and used for development. It is tied to the Robot via GUID using Sherpa Orchestrator for a specific User [(**1 License key for 1 Robot**)](https://docs.sherparpa.ru/en/licenzii/dopolnitelno/otlichiya-attended-i-attended-floating-licenzii).
* **Unattended** — Robots are installed on virtual machines and can work simultaneously on several of them. Robots are not launched from Sherpa Designer, operate only under the control of Sherpa Orchestrator, and are used for debugging. Licenses are managed by Sherpa Orchestrator and are tied to Robots via GUID using Sherpa Orchestrator (**1 License key for an unlimited number of Robots, some of which can work in parallel, while others can work sequentially**).
If Robots are connected from Sherpa Designer to the Unattended License using the remote debugging feature, they will only be available for debugging, with no further development possible.
Unattended Licenses are triggered from Sherpa Orchestrator.
### Activation of Robot Licenses
The following table presents three types of activation. Each type describes the method of activation and data storage, as well as the degree of dependence on Sherpa Orchestrator.
| **Attended** | **Attended Floating** | **Unattended** |
| --------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------ |
|
Local activation or via Sherpa Orchestrator.
Stored locally.
Can be used without Sherpa Orchestrator.
|
Activation via Sherpa Orchestrator.
Stored in Sherpa Orchestrator.
Cannot be used without Sherpa Orchestrator.
|
Activation via Sherpa Orchestrator.
Stored in Sherpa Orchestrator.
Cannot be used without Sherpa Orchestrator.
|
### Transferring Robot Licenses Between Machines and Users
* **Attended**: To transfer this type of License, you need to contact technical support.
* **Attended Floating**: Transfer is done through Sherpa Orchestrator, providing flexibility and centralized management.
* **Unattended**: Transfer is also done through Sherpa Orchestrator, ensuring automated access without the need for User presence.
### Purpose of Robot Licenses
Each license is designed for specific scenarios of working with robots and has its unique capabilities.
* **Attended**: This License is intended for developing robots on a local machine together with Sherpa Designer. It allows running Attended robots on physical and virtual user workstations under their control, as well as periodically launching Attended robots from the local Windows scheduler when a real desktop is available.
* **Attended Floating**: This License allows running Attended robots on virtual machines without a constant RDP connection, which is especially useful for automating tasks that do not require User interaction. Development in Sherpa Designer is possible on any account with an Unattended License.
* **Unattended**: This License is necessary for running autonomous Robots using Sherpa Orchestrator without User involvement. It provides reliable, long-term, reproducible, and fault-tolerant processing of processes, data, and tasks, and is suitable for handling large volumes of tasks.
For each License, there is the possibility to perform Work with Logs, Processes, Resources, Tasks, Queues, and Storage.
The following table provides more detailed information about the purpose of Licenses:
| **Attended** | **Attended Floating** | **Unattended** |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
Can receive processes (scripts) from Sherpa Orchestrator for subsequent local execution.
Can run local scripts.
When the User disconnects from the RDP session to the machine where the Robot is running, the Robot loses the ability to work with UI elements on the screen.
|
Can receive processes (scripts) from Sherpa Orchestrator for subsequent local execution.
Can run local scripts (if not prohibited by Sherpa Orchestrator policy for this License).
When the User disconnects from the RDP session to the machine where the Robot is running, the Robot loses the ability to work with UI elements on the screen.
|
Always receives Processes (scripts) from Sherpa Orchestrator for subsequent local execution.
Cannot run local scripts.
The Robot always reliably works with UI elements, regardless of whether the User is connected to its graphical session or not.
|
### Running Robots
1\. **Attended**:
* **Manual launch**: The User can launch the Robot by double-clicking the Robot file, providing convenient and intuitive access.
* [**Launch via Sherpa Assistant**](https://docs.sherparpa.ru/en/licenzii/dopolnitelno/aktivaciya-licenzii-cherez-sherpa-assistant): The User launches the Robot from the list of available Robots, simplifying the search for the required file.
* **Launch via hotkeys**: Provides the ability to assign key combinations for quick Robot launch. This significantly speeds up work, allowing the User to instantly initiate processes without the need to search for them in the menu.
* **Launch from the command line**: For Users familiar with the command line, there is a way to activate Robots via the console, which can be useful in automation or when using scripts.
* **Launch from the local Windows Scheduler**: This feature allows launching Robots based on a predefined schedule, which is especially convenient for performing regular tasks.
2\. **Attended Floating**:
* **Manual launch**: The User can launch the Robot by double-clicking the Robot file, providing convenient and intuitive access.
* [**Launch via Sherpa Assistant**](https://docs.sherparpa.ru/en/licenzii/dopolnitelno/aktivaciya-licenzii-cherez-sherpa-assistant): The User launches the Robot from the list of available Robots, simplifying the search for the required file.
* **Launch via hotkeys**: Provides the ability to assign key combinations for quick Robot launch. This significantly speeds up work, allowing the User to instantly initiate processes without the need to search for them in the menu.
* **Launch from the command line**: For Users familiar with the command line, there is a way to activate Robots via the console, which can be useful in automation or when using scripts.
* **Launch from the local Windows Scheduler**: This feature allows launching Robots based on a predefined schedule, which is especially convenient for performing regular tasks.
3\. **Unattended**:
* **Launch via Sherpa Orchestrator**: Robots can be activated through Sherpa Orchestrator, allowing centralized automation management.
* **Launch upon receiving a new Task in the Queue**: This feature allows robots to automatically start executing tasks as they appear, minimizing the need for manual intervention.
* **Launch upon receiving an email**: Robots can be launched upon receiving specific emails, integrating automation with email-related workflows.
Thus, the choice between different types of Licenses and launch methods depends on the specifics of work, business needs, and the desired level of automation. Investing in the right type of License will not only increase productivity but also optimize workflows, ultimately leading to improved results and increased efficiency for the enterprise.
### Other Types of Licenses
To learn about and configure other types of licenses, follow the corresponding link:
* [Sherpa Orchestrator](https://docs.sherparpa.ru/en/licenzii/dopolnitelno/upravlenie-licenziyami-sherpa-rpa-cherez-sherpa-orchestrator)
* [Sherpa AI Server](https://docs.sherparpa.ru/en/licenzii/dopolnitelno/licenzii-sherpa-ai-server)
---
# 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/licenzii.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.
