- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Setup Samples
- Storing Robot Credentials in CyberArk
- Setting up Attended Robots
- Setting up Unattended Robots
- Storing Unattended Robot Passwords in Azure Key Vault (read-only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read-only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Audit
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Orchestrator testing
- Other Configurations
- Integrations
- Classic Robots
- Host administration
- Organization administration
- Troubleshooting

Orchestrator user guide
Setting up Attended Robots
linkLearn the fundamentals ofattended robots.
End-to-end Attended Setup
link- Create a machine template or a standard machine. For personal workspace accounts, a machine template is automatically created.
- Connect UiPath Assistant to Orchestrator using the key generated by the machine entity.
Where from?
UiPath Assistant > Orchestrator Settings
- Configure the account: set its role at the tenant level, enable automatic robot creation, select the license type, select the Stand-alone checkbox if your Studio/StudioX/StudioPro is locally licensed such that Orchestrator doesn't allocate a license from its licenses pool, set the username used to log on to the machine on which the UiPath Robot is installed, configure the execution settings of the UiPath Robot.
- Assign the account to one or multiple folders while choosing the appropriate roles at the folder level. Personal workspace
users can work in the context of their own workspace directly.Important: This gives access to that folder and makes the processes deployed there available and ready to get executed.
Where from?
Tenant > Folders
- Start a job.
Where from?
UiPath Assistant
In attended mode, the UiPath Assistant shows the processes across all the folders the account is assigned to.
These processes cannot be started or triggered in unattended mode from Orchestrator unless it's for debugging purposes. See Studio design and Orchestrator debugging.
Setting up Attended Robots for Groups
linkThis procedure walks admins through the steps for enabling attended robots for a group of users. Groups are used to simplify administration for accounts with similar access, robot configuration, and licensing needs, that are managed together.
- Reference a group in Orchestrator or edit an existing group and assign roles to it.
- On the Robot setup tab, enable the toggle for the attended robot.
- On the Robot settings tab, configure execution settings for the corresponding UiPath Robot.
- Click Add. The group is referenced/updated. One attended floating robot is provisioned for each group member that signs into Orchestrator. An attended license is consumed by each user. Licenses are allocated on a first-come-first-served basis. If you want a license assigned to a different user, you must manually free one up by deallocating it from an existing user.
Setting up Attended Robots for Individual Accounts
linkThis procedure walks admins through the steps for enabling attended robots for individual user accounts. This is recommended if group members require additional capabilities on top of those granted by group membership and it helps achieve granular control in terms of robot configuration.
- Add or edit a user account and assign roles to it.
- On the Robot setup tab, enable the toggle for the attended robot.
- On the Robot settings tab, configure execution settings for the corresponding UiPath Robot.
- Click Add. The user account is created/updated. One attended floating robot is created for the user.