Abstract: A method is implemented by a controller executed on at least one processor. The method provides pre-authorized access to a robotic process automation for a resource associated with a job. The method includes causing, by the controller, the robotic process automation to assume a user identity during an authentication flow to enable access by the robotic process automation to a resource. The method includes issuing, by the controller, tokens to the robotic process automation during the authentication flow. The method includes enabling, by the controller via the tokens, the identity service that governs the resource to participate in operations of the controller to provide the pre-authorized access to the robotic process automation.

Abstract: Development and deployment of multi-platform automations for robotic process automation (RPA) are disclosed. Hardware level commands, driver level commands, and/or application programming interface (API) calls are automatically and seamlessly substituted within an automation and/or within an RPA workflow at design time. Development of an RPA automation may occur on a first operating system, and the automated reconfiguration and deployment of the RPA automation may occur in a second, distinct operating system. An automation including a first set of hardware level commands, driver level commands, and/or API calls native to a first operating system may be received, ingested, or retrieve and the automation may be automatically reconfigured to include a second set of hardware level commands, driver level commands, and/or API calls native to an operating system.

Abstract: Automation windows for robotic process automation (RPA) using multiple desktops are disclosed. One or more robot desktops are launched, and one or more RPA robots operate in the robot desktop(s). The robot desktops may not initially be the active desktop. When the robot(s) execute their automations, if an activity in the RPA robot workflow needs the robot desktop to be the active desktop, the active desktop is switched to the appropriate robot desktop when the appropriate robot desktop is not already active, and activit(ies) of the RPA workflow that require the robot desktop to be the active desktop are executed. In some embodiments, after RPA workflow execution finishes, the robot desktop, the RPA robot, or both, are automatically closed.