# Screens

The screen is part of the Orchestrator interface. Each screen within the Orchestrator represents a set of settings for organizing the work of Robots.

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

Descriptions of the screens are presented in the following table:

<table data-header-hidden><thead><tr><th width="53"></th><th width="130"></th><th></th></tr></thead><tbody><tr><td><strong>No.</strong></td><td><strong>Screen</strong></td><td><strong>Screen Description</strong></td></tr><tr><td>1.</td><td>Overview</td><td>A dashboard with a set of widgets displaying key parameters and data slices regarding the operation of software Robots and the Orchestrator. Basic dashboard statistics (number of Robots, Processes, etc.) are displayed here.</td></tr><tr><td>2.</td><td>Robots</td><td>Displays the “Robots” and “Robot Groups” tables. Allows various operations (creation, editing, grouping, etc.) with all available Robots in the Orchestrator.</td></tr><tr><td>3.</td><td>Processes</td><td>Displays the automation scenarios executed by the Robots and their versions.</td></tr><tr><td>4.</td><td>Packages</td><td>Displays packages and their available versions.</td></tr><tr><td>5.</td><td>Resources</td><td>Displays a list of objects available to all Robots, Robot Groups, or a specific Robot. Supported resource types: text (text string), credentials (login-password pair), calendar.</td></tr><tr><td>6.</td><td>Storage</td><td>Displays a list of Files and Folders.</td></tr><tr><td>7.</td><td>Jobs</td><td>Displays the combination of a Process and the Robot assigned to execute that Process.</td></tr><tr><td>8.</td><td>Queues</td><td>Allows grouping similar tasks, creating task flows, and adding tasks to Queues.</td></tr><tr><td>9.</td><td>Actions</td><td>Allows creating separate workspaces within the Orchestrator, created using the Actions screen. Also, within this screen, actions for tasks in the Queue can be created, as well as a form for task execution.</td></tr><tr><td>10.</td><td>Triggers</td><td>Describes conditions under which Jobs can be automatically created, subsequently launching Robots.</td></tr><tr><td>11.</td><td>Robot Messages</td><td>Contains information about messages that Robots send to the Orchestrator during the execution of Jobs.</td></tr><tr><td>12.</td><td>Accounts</td><td>Allows creating new Accounts as well as editing existing ones.</td></tr><tr><td>13.</td><td>Users</td><td>Allows creating new Users as well as editing existing ones.</td></tr><tr><td>14.</td><td>Roles</td><td>Allows defining a set of access rights to specific screens of the Orchestrator and functions within those screens.</td></tr><tr><td>15.</td><td>Object Folders</td><td>Allows creating and editing access folders that provide the ability to more precisely delineate access to Orchestrator objects for different User roles.</td></tr><tr><td>16.</td><td>Audit</td><td>Shows the Orchestrator's own events.</td></tr><tr><td>17.</td><td>Licenses</td><td>Displays all Orchestrator Licenses, as well as a set of tools for creating, activating, and managing them.</td></tr><tr><td>18.</td><td>API</td><td>Contains a set of tools for data exchange via API (reference for existing API methods, tools for obtaining a token for working with the API).</td></tr></tbody></table>


---

# 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.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.