- 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
- Audit
- Settings - Tenant Level
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Orchestrator testing
- Other Configurations
- Integrations
- Classic Robots
- Host administration
- About the host level
- Managing system administrators
- Managing tenants
- Configuring system email notifications
- Customizing the Login page
- Session Policy
- Orchestrator Host Settings
- Audit logs for the host portal
- Maintenance Mode
- Organization administration
- Troubleshooting

Orchestrator user guide
Session Policy
linkSetting the idle timeout
linkThe value set for idle timeout represents the amount of time a user can be inactive before their session is disconnected and they are singed out.
To set the idle timeout:
- Go to Admin, at host level, and then select Security.The Security Settings page for the organization opens.
- Along the top, select the Session Policy tab.
- If not already enabled, select the toggle next to Enable Idle Timeout to enable this setting.
- Under Timeout settings, set the number of minutes, hours, or days.
- Select Save in the bottom right corner of the page.
A confirmation message appears in the top right after the change is applied.
Restrict or allow concurrent sessions
linkThis feature governs user sessions within web browsers. It determines whether a user can have more than one active session at the same time.
-
If the Limit Concurrent Sessions option is enabled, it restricts users to a single active session at any given time. If a user is already logged in and attempts to log in from another browser or device, the previous session is terminated.
-
If the Limit Concurrent Sessions option is disabled, users can log in from different browsers or devices simultaneously. Each login is treated as a separate session, and users can switch between them without being automatically disconnected from the previous sessions.
To change concurrent sessions settings:
- Go to Admin, select your organization, and then select Security.
The Security Settings page for the organization opens.
- Along the top, select the Session Policy tab.
- Select the toggle next to Limit Concurrent Sessions to enable or disable this setting.
- Select Save in the bottom right corner of the page.
A confirmation message appears in the top right after the change is applied.