- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Setup Samples
- Storing Robot Credentials in CyberArk
- Setting up Attended Robots
- Setting up Unattended Robots
- 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
- SmartCard Authentication
- Unattended Sessions
- User Sessions
- License
- Audit
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Other Configurations
- Integrations
- Classic Robots
- Host administration
- Organization administration
- Troubleshooting
User Sessions
This section offers an overview of all user sessions started from the Assistant and related information.
|
Column Name |
Description |
|---|---|
|
User |
The username of the user under whom the robot runs. |
|
Domain\Username |
The domain\username of the user under whom the robot runs. |
|
Hostname |
The name of the host machine on which the robot resides. |
|
Status |
The status of the attended robot. |
|
Type |
The robot type alongside the license type, in parentheses. Starting an Assistant session on a machine used for unattended purposes displays Unattended as the type. |
|
Version |
The Robot version. |
|
Version Status |
The auto-update policy of the Robot. |
There is a known issue on the Monitoring page when you filter the User sessions by Status. The filter returns all statuses instead of the one you have selected.
