orchestrator
2.2510
false
- Getting started
- Best practices
- Organization Modeling in Orchestrator
- Managing Large Deployments
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Organizing Resources With Tags
- Orchestrator Read-only Replica
- Exporting grids in the background
- Enforcing user-level Integration Service connection governance
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- Configuring automation capabilities
- Solutions
- Audit
- Resource Catalog Service
- Automation Suite Robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Indexes
- About indexes
- Managing indexes
- Orchestrator testing
- Integrations
- Troubleshooting

Orchestrator user guide
Last updated Nov 11, 2025
Indexes are vector database folders organizing business data embeddings. They support retrieval augmented generation (RAG) for UiPath generative AI experiences, enabling efficient semantic searches. This helps overcome LLM limitations, reduces hallucinations, and provides AI applications access to specialized, current information.
In the UiPath platform, indexes are supported through the Context Grounding service. To use Context Grounding, you must configure a connection to an LLM, as described in Configuring LLMs for your product.