- 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
Folders
A folder is a storage area that helps keep your projects separate. They enable you to maintain fine-grained control over automations and their intrinsic entities, and personnel across the entire organization.
Folders have their own Orchestrator resources that reside within each specific folder. There are also global resources which are created at the tenant level and which are available across folders.
|
Tenant Resources |
Folder Resources |
|---|---|
|
|
These entities can be included in multiple folders of a hierarchical structure or be specific to each folder or subfolder. Only those available in the active folder are visible in Orchestrator. Switching the active folder will also update the entities and their contents, visible in Orchestrator.
Root folders can be configured with a dedicated package feed, in which case packages are a folder-specific resource, meaning they are kept separate and only available in the folder they have been published to.
Folders with a dedicated package feed are marked with a Folder Packages label below the Folder name.
Please note, in Studio, the folder feed might not show up immediately. It is necessary to refresh the Orchestrator connection to display it.
To manage the access an account has in a folder, assign one or several folder roles that include the necessary Folder Permissions for each of the folder-level resources listed in Tenant and Folder Resources .
Although some roles are Mixed roles by default, you can only use permissions of a single type - Tenant or Folder permissions - in any custom roles you create.
Depending on the access level you wish to grant, a combination of multiple roles is often required.
A folder hierarchy can be established with up to 7 levels. This structure includes the top-level folder and allows for 6 additional layers of subfolders beneath it. In terms of user access, it is inherited from the parent folders. This means if you are assigned access to a folder, you automatically gain access to all of its subfolders.
Orchestrator Folder Path parameter of the Orchestrator activities
such as Get Asset.
Orchestrator Folder Path parameter, as follows:
- Path starting with
/- starts from therootfolder of the tree the ambient folder is part of. - Path starting with
.- starts from the ambient folder. - Path starting with
..- starts one level up in the hierarchy of the ambient folder for each..in the path (e.g.../for one level up,../../for two levels up in the hierarchy).
../../../Finance path works, but the ../../../Accounting path fails.
Note that trailing slashes are not accepted.
Operations within folders are governed by two primary permission sets:
-
Folder Permissions: These permissions apply to the main or root folders of the hierarchy. They grant control over who can create, edit, or delete these folders.
-
Subfolder Permissions: These permissions apply to child folders, or subfolders. They grant control over who can create, edit, or delete subfolders.
