- 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
- Audit
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Identity Server
- 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.
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.
Depending on the access level you wish to grant, a combination of multiple roles is often required.
Folders support a hierarchical structure where you can have up to six subfolders under each first-level folder. User access is inherited from parent folders such that you have access to any subfolder(s) of a folder to which you are assigned.
Orchestrator Folder Path
parameter of the Orchestrator activities such as Get Asset.
Orchestrator Folder Path
parameter, as follows:
- Path starting with
/
- starts from theroot
folder 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.
Two permission sets dictate the account abilities concerning folders: Folders and Subfolders.
Folders Permission |
Subfolders Permission |
---|---|
|
|
The Folder Packages permission set controls access to folder packages.