- 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
- SmartCard Authentication
- Configuring automation capabilities
- Audit
- Settings - Tenant Level
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Other Configurations
- Integrations
- Host administration
- Organization administration
- Troubleshooting
Orchestrator User Guide
Managing tenants
A tenant is a unique and separate division or department within an organization. Each tenant has its own resources, separated from other tenants. In the standalone model, an organization is restricted to having a single tenant. As a result, a one-to-one relationship ensues between an organization and tenant.
When creating a tenant, you also define the credentials for the administrator of the tenant.
Impact of changing the tenant name
Changing the name of any of your tenants greatly impacts your previous configurations:
- Robots configured at the tenant level are disconnected. Users must reconnect their robots, entering the new URL.
- The tenant URL previously bookmarked doesn't work anymore. Send your users the new URL.
- Mobile Orchestrator users are disconnected. Send them the new tenant URL to connect again.
To disable or enable a tenant: In the Tenants page, click More Actions and select Disable or Enable:
To disable or enable multiple tenants: Select the checkboxes at the left of the tenants and then click Disable/Enable the selected tenants: