Shared entry point for Delegate and Cartographer, covering what each profile does, what makes both different from a typical desktop assistant, and how to extend either.

UiPath Delegate and Cartographer are AI agents that run on your desktop and do the work you would otherwise do by hand. You describe what you need in plain language: Delegate, the general-purpose profile, drives your applications, documents, and business systems directly; Cartographer, the business-analyst profile, turns that same kind of access into governed process documentation.

Unlike a typical general-purpose desktop assistant, Delegate and Cartographer run under the controls your UiPath organization already has and operate the enterprise systems your work actually happens in.

Delegate installs alongside UiPath Assistant, and you can move between Assistant, Delegate, and Cartographer inside the same application. What experience you see depends on what your admin has enabled.

Delegate operates them directly: direct connections are available for many of the systems you already use — see Working with external data and applications — and for systems without one, such as legacy or specialized applications, Delegate works through Computer Use, driving the application the way a person would. Delegate runs natively on Windows, and draws on UiPath's existing automation for the systems enterprises run on, including SAP, Oracle, Citrix, and mainframes.

Cartographer works from what you give it — transcripts, interviews, SOPs, recordings — and from existing automations you point it at, and it can delegate a hands-on step to Delegate for in-context help. See Delegating a task.

Delegate and Cartographer act with your access, on your machine, inside your systems. There is no separate governance layer built just for either — both operate under the same automation platform governance your organization already runs everything else through, configured through Automation Ops.

Your administrator controls which applications and tools they can use, which models they run on, and which systems they can connect to, using the same central policies that govern the rest of your UiPath estate. Independently of that, you control how much either does before checking with you, within whatever your organization allows. Model calls route through the UiPath AI Trust Layer, so both are covered by the same platform controls as everything else rather than needing a separate review. See Security overview and Local security configuration.

Delegate and Cartographer are not built around a single model from a single vendor. By default, both use whatever models your organization has made available through the UiPath AI Trust Layer — either UiPath's default models, or your own configuration if your organization brings its own.

Your organization can decide which models are acceptable and supply its own where a contract, a regulator, or a data residency requirement demands it. Whichever model is used, calls route through the AI Trust Layer, so the controls and the audit trail do not change.

If your organization already runs UiPath, Delegate and Cartographer use that work rather than duplicating it. Delegate can call the automations already published in your tenant, and Cartographer can start from those same automations instead of a blank process — see Working with existing automations. Your queues, assets, and permissions carry over either way, so there is no second set of entitlements to maintain.

Connectors reach into your existing systems the same way the rest of the UiPath platform does; Skills and Plugins are ways of adding capabilities to either.

Beyond the general-purpose experience, Delegate includes specialized profiles for particular roles. Which profiles you have access to is configured by your organization administrator.

The default experience. Delegate works across your applications, files, and web services on whatever you ask. See Delegate overview to get started.

Cartographer is a specialized experience for business analysts. Its long-term goal is the Map of Work: a single, versioned, governed definition of how the business runs. Specifications, sign-off, and audit are generated from one source of truth, instead of drifting documents that disagree with reality.

Today, Cartographer helps document a process from whatever data is available — transcripts, interviews, SOPs, recordings. It then drafts a future design that takes into account business goals, pain points, aspirational benchmarks, and constraints. Once confirmed, it produces a Process Design Document (PDD), followed by a Specification Design Document (SDD) for coding agents.

Switch to it from the product switcher in the title bar, the same way you switch between Assistant and Delegate.

Cartographer has its own dedicated section later in this guide. See Cartographer overview to get started.

Testing is a specialized Delegate experience tuned for reviewing test results, triaging failures, and other quality-assurance workflows across your testing tools. It runs today inside the general-purpose experience rather than as its own separate profile, but it has its own dedicated section later in this guide. See Delegate for Testing overview to get started.

Delegate and Cartographer are powered by large language models, and their plans, explanations, and the content they produce may occasionally be inaccurate, incomplete, or based on a misunderstanding of your request. This is a known limitation of LLMs, sometimes called "hallucination."

For example:

Always review the plan and output before relying on it, especially for production workflows, data handling, or actions that are hard to undo:

Delegate and Cartographer work best as collaborators, not unsupervised decision-makers. Your review and judgment remain essential, particularly for workflows that touch production systems or external stakeholders.

Continue through the documentation in order, or jump to the section that matches your current need: