# Key Concepts

**Sherpa Orchestrator** — is a tool for centralized connection and management of software robots created on the Sherpa RPA platform. It manages the robots, determines their status, assigns different tasks to different robots, organizes task execution queues, and monitors their execution.

**Screen** – a part of the Orchestrator interface. Each screen within the Orchestrator represents a set of settings for organizing the work of robots.

**Attended robots** — are robots that are manually launched on the user's computer, either from startup, via a keyboard shortcut, or on a schedule from the Windows Task Scheduler.

**Unattended robots** — are robots that are launched by the coordinator. The coordinator starts the robots if there is work for them on the "Jobs" screen. A job can be created manually, by a trigger, or via API.

**Coordinator** — a service installed under the administrator account of the RDP server (terminal server) to launch Unattended Robots, if necessary, automatically logging into the robot accounts. For Attended robots, specifying a coordinator is not required.

**Process** — a robotic scenario that is executed by the robots.

**Package** — blocks and palettes created by the user using the "Package Manager" tool in Sherpa Designer.

**Resources** – objects available to all robots, a group of robots, or a specific robot. Supported resource types include: text (text string), credentials (login-password pair), and calendar.

**Job** – a combination of a robot and a process or a robot, process, and task.

**Task** – a set of parameters in the form of Parameter-Value pairs (Key-Value) that can instruct the robot on what exactly it needs to do within the process execution.

**Actions** – individual workspaces within the Orchestrator, created using the “Actions” screen, where actions for tasks in the queue can also be created, as well as a form for task execution.

**Trigger** – a tool that allows for the automatic creation of jobs based on specified conditions, which are then passed to robots for processing.

**Accounts** – are separate spaces within the Orchestrator, each possessing its own set of jobs, processes, resources, robots, queues, and users. Accounts are completely isolated from each other regarding robots, processes, and other objects.

**Users** – are workspaces created within an account. Each user is assigned a specific role or multiple roles.

**Role** – is a parameter that defines the set of access rights to the Orchestrator screens, as well as functions within the selected screens.

**Audit** – a screen in the Orchestrator that presents a list of messages about events that have occurred within the Orchestrator.

**License (license key)** – is issued by vendors for client companies. Licenses define the number and type of robots for which jobs can be launched by the Orchestrator. A robot can use either a local license (which is stored on the computer where the robot itself is installed) or a license from the Orchestrator. Licenses of both Attended and Unattended types can be added to the Orchestrator.


---

# 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/osnovnye-ponyatiya.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.