studio
latest
false
UiPath logo, featuring letters U and I in white

Studio User Guide

Last updated Sep 25, 2025

Solutions

Solutions group everything needed to automate an end-to-end business process, offering you the capabilities to develop automation projects together with their dependencies and deploy them across tenants as a whole.

Solutions are cloud-level containers for modeling an end-to-end automation as a single, versioned unit. In a solution, you can create and orchestrate:

  • RPA workflows
  • API workflows
  • Agents
  • Agentic processes
  • Apps (with human-in-the-loop validations)

All these components share solution-scoped resources (assets, connections, queues, storage, etc.) that you manage centrally at the solution level. Solutions are also portable—package once and deploy across tenants and organizations with environment-specific configuration.

To learn more, refer to the Studio Web user guide.

The Project panel

The Project panel allows you to manage the projects in your solution, as well as the project files in each project.

Inside the Project panel, you can:

  • Use the docs image Add to Solution button to:
    • Create a new automation project and add it to your solution.
    • Import an existing automation project.
      Note: You can also access the Add to Solution window by right-clicking inside the Solution panel.
  • Use the docs image Search bar to find specific projects, files, pages, actions, variables, or arguments in your solution.
  • Right-click the solution to rename it or open it in Studio Web.
  • Right-click a project to:
    • Open the project in Studio and access the context menu for projects with project-specific options.
    • Open the project in Studio Web in a new browser tab.
    • Remove the project from the solution.

When you open a solution in Studio, you can only make changes to RPA projects. Other types of projects included in a solution cannot be modified from Studio and require you to continue editing the solution in Studio Web (this includes app projects, agentic processes, API projects, and agents).

Projects that cannot be modified in Studio are greyed out in the Solution panel. You can right-click a project that is not supported in Studio to either open it in Studio Web or remove it from the solution. When opening the project in Studio Web, changes are saved to cloud and the project is opened in a new browser tab.

The experience of designing and debugging RPA projects within a solution is the same as with standalone RPA projects.

Note: You cannot add or import Windows - Legacy projects into a solution.


The Defined Resources panel

The Defined Resources panel displays the resources included in your solution. The panel can be collapsed. Resources are automatically added to a solution as they are used by activities and are grouped under these categories:

  • Apps - User interfaces powered by automations that allow you to build custom business applications which connect to data.
  • Assets - Shared variables or credentials that you can use in different automation projects.
  • Business rules - Objects used to store and manage Decision Model and Notation (DMN) files.
  • Connections - Integration Service connections that help in establishing tasks between single users and external applications.
  • Context - Context Grounding indexes that give access to permissioned knowledge bases.
  • Processes - Package versions linked to a particular folder.
  • Queues - Containers that enable you to hold an unlimited number of items.
  • Storage buckets - Per-folder storage solutions leveraged in creating automation projects.
  • Task catalogs - Action containers where you can categorize your actions based on various criteria. The catalog that stores an action is set when an action is created, using action creation activities in Studio Web.
  • Dependencies - Activity categories contextually linked into a specific project.
Resources can be created, defined, or deleted both from Studio and Studio Web. To learn more, refer to Solution Resources in the Studio Web guide.

Activities are aware of the solution context. Inside activities that handle solution resources (for example, Add Queue Item), the resource picker widget displays all available resources (assets, queues, connections, etc.). You can also use the Open Orchestrator button to manage platform resources in Orchestrator.

Managing solutions in Studio and Studio Web

Changes made to a solution are always synced to the cloud, allowing you to seamlessly switch between Studio and Studio Web.

After you create a solution in Studio Web, you have the option to continue working in Studio. From the Workspace page in Studio Web, open the menu on the right side of a solution and select Open in Studio Desktop. Alternatively, open the solution in Studio Web, right-click the solution name in the Solution Explorer, and select Open in Studio Desktop.

After opening a solution created in Studio Web, select the Cloud Solution label in the status bar to open a drop-down menu with options that enable you to manage the solution:
  • Open in Browser - Open the solution in Studio Web. If the solution is locked by Studio Web, an error is displayed and the solution is opened in a new tab in read-only mode.
  • Sync with Cloud - Push the changes that you made in Studio and continue building your solution in Studio Web.

You can add a solution under Git version control by selecting the Add To Source Control label in the status bar. This allows you to manage commits and branches at solution level.

Note:
  • Studio detects when a project is part of a solution. Opening a local project that is part of a solution automatically opens the entire solution context.
  • When converting a cross-platform project to the Windows compatibility, the project is converted directly, without the option to create a copy of the original project.

Working with solutions in Studio and Studio Web

Keep in mind these differences when working with solutions in Studio and Studio Web:
  • New solutions can only be created in Studio Web. You can open and edit existing solutions in Studio, which is context-aware and allows you to enhance solutions with cross-platform and Windows RPA projects.
  • Renaming individual projects is currently supported only in Studio Web.
  • You can only publish the current RPA project from Studio.
  • Some project types (agentic processes, apps, API workflows, or agents) can only be opened and edited in Studio Web. You can use Studio for its powerful RPA design and debug experiences, and Studio Web to access agentic automation features.
  • Solution packaging and deployments occurs only in Studio Web. Support for solutions will be added to CI/CD integrations with UiPath CLI in the future.
  • You can view Windows projects in the Solution Explorer in Studio Web, but you can edit them only when you open the solution in Studio.
  • Only one user can work on a solution at a time. We introduced a solution-level lock to prevent unsolvable conflicts (for example, when one user builds an API workflow project in Studio Web while another edits an RPA project in Studio). Without this lock, a later sync to cloud could overwrite one set of changes. This limitation will be removed once Studio Web supports local workspaces (saving the entire solution to disk), allowing standard Git flows to safely resolve conflicts.
Tip:
  • Use Git at the solution level to version automation projects together with their configurations.
  • Deploy the solution for debugging in Studio Web before opening it in Studio. This ensures all solution resources and projects are deployed in Orchestrator and are ready for use in Studio.

Was this page helpful?

Support and Services
Get The Help You Need
UiPath Academy
Learning RPA - Automation Courses
UiPath Forum
UiPath Community Forum
Uipath Logo
Trust and Security
Terms of Use
Privacy Policy
Cookies Policy
© 2005-2025 UiPath. All rights reserved.