orchestrator
2020.10
false
- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Audit
- Actions
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Action Catalogs
- Profile
- System Administrator
- Identity Server
- Authentication
- Other Configurations
- Integrations
- Classic Robots
- Troubleshooting
About the Tenant Context
OUT OF SUPPORT
Orchestrator User Guide
Last updated Dec 12, 2023
About the Tenant Context
Multitenancy enables you to isolate data, with only one instance of Orchestrator. This feature facilitates automating different departments from your company and ensures the desired authorization of Orchestrator data per department. However, please note that all the data is stored in the same database.
The following Orchestrator components are separated by tenants:
- Processes
- Packages
- Assets
- Queues
- Triggers
- Robots
- Environments
- Jobs
- Logs
- Alerts
- Audit
- Settings (including licenses)
- Users
- Folders
- Machines
Select Tenant from the sidebar menu to view and manage tenant-level entities of your Orchestrator deployment and also manage your Orchestrator settings and licenses:
From this view you have the following options:
- Robots
- Folders
- Users
- Roles
- Machines
- Packages
- Audit
- Credential Stores
- Webhooks
- License
- Alerts
- Settings
Additionally, you can use the quick actions drop-down menu to perform the following actions: