- Getting started
- Best practices
- 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
- Audit
- Cloud robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Resource Catalog Service
- Authentication
- Integrations
- Classic Robots
- Troubleshooting
About Storage Buckets
.pdf
file used across multiple business processes or data sets used for your machine learning models). For details on using storage
buckets in your automation projects read about Orchestrator activities in the Activities guide.
As storage buckets are created within the scope of a given folder, this enables you to use the fine-grained permissions and role assignment models of the Folders feature to control access to these storage buckets and their contents only to those accounts that need it. Users with the required permissions can browse the contents of any configured storage bucket, and upload or download files as desired.
The Storage Buckets page displays your currently configured buckets and enables you to create as many additional storage buckets as needed.
Storage Buckets can be configured using any of the following providers:
- Orchestrator - the same storage location where Orchestrator feed packages are kept (see the Deployment section of the UiPath.Orchestrator.dll.config topic)
- Azure Storage (WASB)
Access to and control over storage buckets and their contents is governed by the following permissions:
Permission |
Description |
---|---|
Create |
|
Edit |
|
View |
|
Delete |
|