About Autopilot

Autopilot™ is a set of AI-powered experiences designed to automate and streamline various day-to-day tasks. Its diverse functionalities handle both general productivity and department-specific tasks across an array of business areas.

Autopilot understands the context of various elements like documents, screens, communications, and processes, and performs actions accordingly.

Autopilot across the platform

Autopilot provides different experiences, tailored to the specific needs and requirements of different user personas:

• Autopilot for developers
• Autopilot for testers

Autopilot for developers is available in the following UiPath products:

• In Studio, StudioX, and Studio Web, where you can generate workflows and expressions by describing the desired outcome.
• In Apps, where you can enhance your low-code application development process.

Autopilot for testers is available in the following UiPath products:

• In Test Manager, where you can evaluate requirements such as user stories for quality aspects such as clarity, consistency, and completeness, generate manual test cases with step-by-step instructions, and gain actionable insights into failing test cases.
• In Studio, where you can automate manual test cases and generate synthetic test data.

Capabilities

Regardless of the particular Autopilot tool you are using or interacting with, there are some core features that persist across different use cases. Here are the main characteristics:

• AI-powered: Autopilot uses artificial intelligence to accurately interpret inputs and execute corresponding tasks. This enables you to interact with Autopilot using natural language.
• Automation generation: Autopilot can automate a wide range of tasks, from data extraction and paperwork processing, to more complex operations. It can interpret your requests, convert them to workflows or applications, and suggest fixes.
• Self-service and assisted experiences: Autopilot covers both self-service and assisted experiences:
  • If you have a clear understanding of your automation needs and you can describe it in natural language, you can use the Autopilot extensive self-service features, which include:
    • text to workflow,
    • text to coded workflows,
    • text to expressions,
    • text to test cases,
    • text to application.
  • If you find it challenging to convey complex tasks in natural language, you can use the many assisted experiences, which include:
    • summarizing blocks of automation,
    • suggested best practices and optimizations,
    • generating applications from .pdf files and images.
• Cross-application compatibility: Autopilot is designed to work seamlessly across both web-based and desktop applications, and it accepts inputs from various sources, and integrating with popular apps such as Word, Excel, PowerPoint, and many more.
• Comprehensive data processing: Autopilot can analyze large volumes of data, generate useful insights, and suggest actions based on analysis. Its ability to handle various data types from multiple sources can significantly impact your decision-making processes.
• Streamlining automation: Featuring a user-friendly and intuitive interface, Autopilot is accessible to everybody, irrespective of your technical proficiency.
• Contextually aware: Autopilot goes beyond just understanding prompts. It understands the context of your requests, and provides the basis for optimal results.
• Process optimization: Autopilot is not just designed to perform tasks, but to perform them optimally. It learns from experience, enhances efficiency, and consistently aims for the best possible output.
• Compliance: To ensure compliance with company policies, data governance and privacy controls are available to IT admins.

Enabling/disabling Autopilot

Autopilot is enabled by default for all users.

Autopilot capabilities in Studio Web can be controlled via Automation Ops policies. To define a Studio Web governance policy that disables some or all Autopilot capabilities:

1. Add a new Studio Web policy in Automation Ops (for more information, see Governance in the Automation Ops guide).
2. Inside the new policy, navigate to the StudioWeb.ai tab (for more information about each Autopilot settings, see Settings for Studio Web policies).
3. Disable some or all Autopilot capabilities, then save your policy.

Autopilot capabilities in Studio and StudioX can be controlled either via Automation Ops policies or via the file-based governance model (by editing the EnableGenerativeAiParam parameter).

To define a policy in Automation Ops that disables Autopilot capabilities for Studio or StudioX:

1. Make sure you are using the latest Studio or StudioX policy template.
2. Add a new Studio or StudioX policy.
3. Under the Design tab, disable the Enable generative AI setting, and then save your policy.

Autopilot capabilities in Test Manager and Apps are controlled by configuring the AI Trust Layer policy.

Licensing

Autopilot activities are measured and licensed through Autopilot actions. One such action is counted from the time you click a button or write a prompt, up until the time you receive a result from that click or prompt. An example of an action is Generate tests in Test Manager, or Generate code in Studio Desktop.

Important: To benefit from Autopilot actions, make sure that the User License Management option is enabled in your organization settings. Find out more about user license management.

Availability

Autopilot actions are consumed by all products where Autopilot is available, and are included by default in existing SKUs and plans, as follows:

• On the Enterprise plan, each of these licenses includes 600 Autopilot actions per user, per month:

  • Automation Developer - Named User
  • Citizen Developer - Named User
  • Tester - Named User
• On all available plans, each user is granted 5 Autopilot actions per day.

Consumption

Autopilot actions reset on the first day of each month.

If you use up the 600 actions before the end of the month, you start consuming from the daily pool.

For details on the number of Autopilot actions available for consumption, check out the Plan breakdown.

For details on how apps consume Autopilot actions, see the Autopilot licensing page in the Apps guide.

About this guide

This guide serves as a high-level overview of the Autopilot initiative, designed to help you familiarize yourself with the general aspects of the framework, its particular tools, and the benefits they bring.

Each tool involved in the initiative has specific functionalities and enhancements tailored to different user personas. To capture these intricate details, this guide points to individual product documentation, which contains complete and up-to-date information.

The progress and changes introduced by each Autopilot tool are captured in the product-specific release notes. Therefore, to keep track of Autopilot's development within a particular product, check the release notes of that specific product.