orchestrator

2.2510

false

Getting started
- Introduction
- Licensing
- User options
- Logging in to Orchestrator
- Resetting your password
- Robots
  - Robot Statuses
  - Robot Settings
- Auto Updating Client Components
- Orchestrator Configuration Checklist
Best practices
- Organization Modeling in Orchestrator
- Managing Large Deployments
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Unattended automation
- 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
- Robots
- Folders
- Monitoring
- Access control
- Configuring automation capabilities
- Machines
- Solutions
- Packages
- Audit
- Credential Stores
  - Integrating credential stores
  - Managing credential stores
- Webhooks
  - Types of Events
  - Managing Webhooks
- Licensing
  - Managing Your Licenses
- Settings - Tenant Level
Resource Catalog Service
- About Resource Catalog Service
Automation Suite Robots
- About Automation Suite Robots
- Prerequisites
- Executing Unattended Automations With Automation Suite Robots
- Regenerating Client Secrets
- Frequently Asked Questions
Folders Context
- About the Folders Context
- Home
Automations
- About Automations
Processes
- About Processes
- Managing Processes
- Managing Package Requirements
- Recording
- Live streaming and remote control
  - Live streaming and remote control via RealVNC
    - Error scenarios
  - Live streaming and remote control via TightVNC
    - Error scenarios
Jobs
- About Jobs
- Managing Jobs
- Job States
- Working with long-running workflows
- Running Personal Remote Automations
- Process Data Retention Policy
Apps
- About Apps
- Publishing an App to a Tenant
- Managing Apps
- Running a Deployed App from a Folder
Triggers
- About triggers
- Managing triggers
- Managing Non-Working Days
- Using Cron Expressions
  - Triggering jobs on the last day of the month
Logs
- About Logs
- Managing Logs in Orchestrator
- Logging Levels
Monitoring
- About Monitoring
- Machines
- Processes
- Queues
- Queues SLA
Queues
- About Queues and Transactions
- Bulk uploading Queue Items using a CSV file
- Managing Queues in Orchestrator
- Managing Queues in Studio
- Managing Transactions
  - Editing Transactions
  - Field Descriptions for the Transactions .csv File
- Review Requests
Assets
- About Assets
- Managing Assets in Orchestrator
- Managing Assets in Studio
- Storing Assets in Azure Key Vault (read only)
- Storing Assets in HashiCorp Vault (read only)
- Storing Assets in AWS Secrets Manager (read only)
- Storing Assets in Google Secret Manager (read only)
Storage Buckets
- About Storage Buckets
  - CORS/CSP Configuration
- Managing Storage Buckets
- Moving Bucket Data Between Storage Providers
Indexes
- About indexes
- Managing indexes
Orchestrator testing
- FAQ - Deprecating the testing module
  - FAQ - Migrating test artifacts to Test Manager
- Test Automation
- Test Cases
  - Field Descriptions for the Test Cases Page
- Test Sets
  - Field Descriptions for the Test Sets Page
- Test Executions
  - Field Descriptions for the Test Executions Page
- Test Schedules
  - Field Descriptions for the Test Schedules Page
- Test Data Queues
- Testing Data Retention Policy
Integrations
- About Input and Output Arguments
  - Example of Using Input and Output Arguments
Troubleshooting
- About Troubleshooting
- Alerts troubleshooting
- General troubleshooting
- Frequently Encountered Orchestrator Errors

Orchestrator user guide

DELIVERY:

Last updated Nov 11, 2025

Enforcing user-level Integration Service connection governance

Use this procedure to prevent regular users from creating shared Integration Service connections in team folders, while still allowing them to create and use private connections in their Personal Workspace.

Before you begin, make sure that the following prerequisites are met:

You have Orchestrator administrator permissions to manage roles, folders, and assignments. For more information, check the Access control page.
Integration Service is enabled on your tenant.
Personal Workspaces are enabled for end users. For more information, check the Personal Workspaces page.

Go to the shared folder where the attended automation is deployed.

This folder is used for shared attended processes. If you do not have a shared folder, create one.

Users can run processes from this folder. They cannot create new connections from here, but they can view and use shared connections deployed by an administrator. This ensures that end users cannot expose their personal connections in the shared folder, where others would gain access to them.

For more information on how to create folders, check the Managing folders page.
Assign the built-in Automation User role to the users running the attended automation in that folder via UiPath Assistant.

The Automation User role does not include the Connections.Create permission by default. With this action you make sure that users with the Automation User role assigned cannot create Connections in shared folders.

Alternatively, you can create a custom role at folder-level that does not have the Connections.Create permission and assign it to the users with the Automation User role.

For more information on how to create custom roles, check the Managing custom roles page.

For more information on default roles, check the Default roles page.
Create and make sure that users have a Personal Workspace.
By having a Personal Workspace, users will have a private space where they can create and manage their own connections without exposing them to other users.
For more information on Personal Workspaces, check the Personal Workspace page.

Was this page helpful?

PREVIOUSExporting grids in the background

NEXTAbout the Tenant Context

Support and Services

Get The Help You Need

Learning RPA - Automation Courses

UiPath Community Forum

Trust and Security

© 2005-2025 UiPath. All rights reserved.