# Executing UiPath CLI tasks

> Running tasks inside the UiPath CLI designed for Windows devices (**UiPath.CLI.Windows**) requires several tasks.

Running tasks inside the UiPath CLI designed for Windows devices (**UiPath.CLI.Windows**) requires several tasks.

The main differences between procedures for the **UiPath.CLI.Windows** and procedures for the **UiPath.CLI** (UiPath CLI designed for Linux devices), consist in additional arguments that you could pass with some tasks that are specific
to the type of device that you are running on.

:::important
When using UiPath CLI, you must ensure that the project is closed in Studio. Doing otherwise causes a conflict leading to
the following error message in CLI: `The action could not be performed because the project is already opened in another Studio instance. Please close it and try
again.`
:::

To know more about the specific tasks you can execute through the UiPath Command Line Interface (CLI), consider reviewing
the following topics:

* [Packing projects into a package](https://docs.uipath.com/cicd-integrations/standalone/2024.10/user-guide/packing-projects-into-a-package#packing-projects-into-a-package)
* [Analyzing a project](https://docs.uipath.com/cicd-integrations/standalone/2024.10/user-guide/analyzing-a-project#analyzing-a-project)
* [Deploying a package to Orchestrator](https://docs.uipath.com/cicd-integrations/standalone/2024.10/user-guide/deploying-a-package-to-orchestrator#deploying-a-package-to-orchestrator)
* [Running a job inside Orchestrator](https://docs.uipath.com/cicd-integrations/standalone/2024.10/user-guide/running-a-job-inside-orchestrator#running-a-job-inside-orchestrator)
* [Testing a package or running a test set](https://docs.uipath.com/cicd-integrations/standalone/2024.10/user-guide/testing-a-packagerunning-a-test-set#testing-a-package-or-running-a-test-set)
* [Testing multiple packages](https://docs.uipath.com/cicd-integrations/standalone/2024.10/user-guide/testing-multiple-packages#testing-multiple-packages)
* [Deploying assets to Orchestrator](https://docs.uipath.com/cicd-integrations/standalone/2024.10/user-guide/deploying-assets-to-orchestrator#deploying-assets-to-orchestrator)
* [Deleting assets from Orchestrator](https://docs.uipath.com/cicd-integrations/standalone/2024.10/user-guide/deleting-assets-from-orchestrator#deleting-assets-from-orchestrator)
* [Running tasks using JSON configuration](https://docs.uipath.com/cicd-integrations/standalone/2024.10/user-guide/running-tasks-using-json-configuration#running-tasks-using-json-configuration)
* [Restoring automation dependencies](https://docs.uipath.com/cicd-integrations/standalone/2024.10/user-guide/restoring-automation-dependencies#restoring-automation-dependencies)

## API access application scopes

The following table shows the required Orchestrator API Access Application Scopes for running any CLI task.

| Application Scope | Description |
| --- | --- |
| **OR.Assets** | Assets read and write access in Orchestrator. |
| **OR.BackgroundTasks** | BackgroundTasks read and write access in Orchestrator. |
| **OR.Execution** | Execution read and write access in Orchestrator. |
| **OR.Folders** | Folders read and write access in Orchestrator. |
| **OR.Jobs** | Jobs read and write access in Orchestrator. |
| **OR.Machines.Read** | Machines read access in Orchestrator. |
| **OR.Monitoring** | Monitoring read and write access in Orchestrator. |
| **OR.Robots.Read** | Robots read access in Orchestrator. |
| **OR.Settings.Read** | Settings read access in Orchestrator. |
| **OR.TestSets** | TestSets read and write access in Orchestrator. |
| **OR.TestSetExecutions** | TestSetExecutions read and write access in Orchestrator. |
| **OR.TestSetSchedules** | TestSetSchedules read and write access in Orchestrator. |
| **OR.Users.Read** | Users read access in Orchestrator. |

In addition to the listed scopes in the table, an important scope to highlight is **OR.Default**. The **OR.Default** scope acts as a wildcard. It offers fine-grained, role-specific access at both organization and folder levels. This gives
you the flexibility to have precise control over application permissions, beyond the predefined organization-wide scopes.
For more details, see [Declaring scopes](https://docs.uipath.com/automation-cloud/automation-cloud/latest/api-guide/accessing-uipath-resources-using-external-applications#declaring-scopes).

## Adding an external application

To register an external application so that it can use OAuth to access your UiPath resources, see [Managing external OAuth applications](https://docs.uipath.com/automation-cloud/automation-cloud/latest/admin-guide/managing-external-applications#adding-an-external-application).