- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Workflow Analyzer
- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- Variables
- Arguments
- Imported Namespaces
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- Troubleshooting
- About troubleshooting
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- JxBrowser applications troubleshooting
- User Events Monitoring
- Citrix Troubleshooting
- Automating Applications Running Under a Different Windows User
About Licensing
You can activate Studio using a Community license or an Enterprise license.
A free Community license can be requested, lasting for a limited period of time, which is renewable. This option can only be activated online. The Robot that comes with the Community Edition Studio can only be connected to the UiPath Orchestrator Community Edition, under your own tenant. For more information, see Activating by Signing in to UiPath.
Activate your Studio with a license acquired from Orchestrator by either signing in to your account or connecting to Orchestrator with your client credentials or machine key. When the connection is established, a license is consumed from Orchestrator. For more information, see Licensing in the Orchestrator Guide.
Depending on the type of license selected, you can perform the following:
- Attended - UiPath Studio is used with an Attended license, which means that the user can only run or debug processes, and not edit workflows.
- Automation Developer / Citizen Developer - UiPath Studio is licensed with its native type of license, which means that the user can run, modify, and debug processes. Studio can also be licensed with RPA Developer, RPA Developer Pro, and Test Developer Pro licenses available in versions prior to 2021.10.
- Non-Production - UiPath Studio is used with a Non-Production license, meaning that the user can troubleshoot workflows.
- Unattended - UiPath Studio is used with an Unattended license, meaning that the user can troubleshoot workflows.
You can activate Studio with a stand-alone Enterprise trial or license key. This type of license activates the Enterprise Edition of Studio. This activation can be done both online or offline. For more information, see Activating with a License Key.
If you already have a local license for your Studio, but still want to connect it to Orchestrator, make sure to select the Stand-alone checkbox in Orchestrator when creating the Robot. This ensures that Orchestrator does not allocate a license from its pool of licenses, as your Studio defaults to the local one.
