- 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
- Test Suite - Orchestrator
- 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
- Azure Storage (WASB)
- Amazon S3
- MinIO
- S3 Compatible storage solutions
- FileSystem
Access to and control over storage buckets and their contents is governed by the following permissions:
Permission |
Description |
---|---|
Create |
|
Edit |
|
View |
|
Delete |
|