orchestrator
latest
false
- 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
- Account types
- Default roles
- Migrating from break inheritance to union of privileges
- Managing custom roles
- Configuring access for accounts
- Configuring automation capabilities
- Solutions
- Audit
- Settings
- Cloud robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Resource Catalog Service
- Integrations
- Troubleshooting
Migrating from break inheritance to union of privileges
Orchestrator user guide
Last updated Jan 15, 2025
Migrating from break inheritance to union of privileges
The union of privileges access model improves access control across all users. It grants users access levels by combining explicit and group-level access. As a result, each time you add or remove a privilege to or from a group, all users who are part of that group become subject to the updated privilege check.
Note: This change impacts the following set of privileges:
- UI Profile settings (No UI access, Personal Workspace only, Standard Interface)
- Update policy settings
- Enable user to run automations
- Create a personal workspaces for this user
Permissions already work in the union of privileges model.