- Organization Modeling in Orchestrator
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Organizing Resources With Tags
- Orchestrator Read-only Replica
- Exporting grids in the background
- 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
- Elastic Robot Orchestration
- Automation Cloud™ Robots - VM
- Automation Cloud™ Robots - Serverless
- Configuring VPN for Cloud Robots
- Bulk Uploading Queue Items Using a CSV File
- Managing Queues in Orchestrator
- Managing Queues in Studio
- Review Requests
- Test Automation
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 that are part of solution packages are marked with the icon.
Tenant and Folder Resources
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.
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.
Although some roles are Mixed roles by default, you can only use permissions of a single type - Tenant or Folder permissions - in any role custom roles you create.
Depending on the access level you wish to grant, a combination of multiple roles is often required. Learn more about Orchestrator's access control model in About Managing User Access.
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.
Working Across Folders
Using modern folders, your automation workflow, executed from one folder, can access resources in another folder using the
Orchestrator Folder Path parameter of the Orchestrator activities such as Get Asset.
Relative folder paths are supported in the
Orchestrator Folder Path parameter, as follows:
- Path starting with
/- starts from the
rootfolder 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).
Going beyond the root folder takes you to the root folder if the folder name you are trying to reach is the root name, otherwise,
it fails. For example, if your root folder is called Finance and is 2 levels above the ambient folder then the
../../../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.
The Folder Packages permission set controls access to folder packages.