- 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)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- Audit
- Resource Catalog Service
- Automation Suite robots
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Identity Server
- Authentication
- Integrations
- Classic Robots
- Troubleshooting
![](https://docs.uipath.com/_next/static/media/grid.05ebd128.png?w=3840&%3Bq=100)
Classic Folders Vs Modern Folders
The Modern folders feature, used in conjunction with Active Directory integration functionality of Orchestrator, enables the quick and convenient management of your organization's attended automation deployment, no matter how large.
With Active Directory integration, the robot access and Orchestrator access for any individual directory user or directory group is managed by the group roles of your directory. There is no need to manually create each user or individually manage their permissions.
Using the hierarchical structure available with modern folders, you can organize and group Orchestrator entities to match your organizational structure and, using custom roles assignment, give any user/group access only to those resources needed.
This way, any user can log in from any available machine and immediately have a robot available to them ready to execute all processes to which they have been granted access. Any changes in your organization (e.g., new hires, departmental transfers, etc.) need only be updated in your directory.
Classic Folders |
Modern Folders | |
---|---|---|
1. AD is the central hub for user information |
|
|
2. SSO with AD Credentials |
|
|
3. Automatic Robot Management |
|
|
4. Automatic License Assignment |
|
|
5. Hierarchical Folder Structure |
|
|
6. Fine-Grained Permissions |
|
|
7. Job Restart |
|
|
8. Long-Running Workflows |
|
|
- Imported AD identities are checked directly against the directory database. There is no need to duplicate the directory in your Orchestrator instance.
- Use the set of credentials configured in AD to access Orchestrator.
- Automatically create a Robot/user for an imported AD group.
- Assign a license type for Robots created automatically (step 3).
- Better organize user layers in your Orchestrator instance from a functional standpoint.
- Better secure user layers in your instance by partitioning control in your system and granting access right granularly per folder level.
- Restart finalized jobs keeping the previous execution settings.
- Allow smooth execution of long-running workflows that require logical fragmentation or human intervention.