Read and Review Automation Anywhere Documentation

Automation 360

Close Contents


Open Contents

Configure auto-login settings

  • Updated: 2022/09/26
    • Automation 360 v.x
    • Explore
    • RPA Workspace

Configure auto-login settings

Configure auto-login settings in the Control Room to either create user sessions or reuse existing user sessions to reduce the bot startup time.


Ensure that you are logged in to the Control Room as the administrator.

Auto-login enables you to deploy a bot for unattended Bot Runners after automatically logging on to a machine and restoring the machine to its original locked/unlocked state after completing the deployment.

Configure auto-login settings to either create new user sessions or reuse existing sessions in the following scenarios:

  • Before deploying a bot, some applications are kept running to accommodate a delay in the application launch.
  • When Windows updates or Active Directory policy updates are pushed after a user logs in, changes in the automation environment might affect bot execution.
  • Logging off from temporary or non-persistent devices stops bot execution.
  • You can reuse existing user sessions when your company's IT policy prevents you from providing device user password for auto-login credentials.
  • To bypass legal disclaimers on RDP-based deployments.


  1. Navigate to Administration > Settings > Devices.
  2. Edit the Auto login settings.
  3. Optional: External key vault setting.
    If an external key vault is used, and you want to retrieve Auto-login passwords from the external vault, click Enabled. If using AWS, you will only need to click Enabled. If using CyberArk, you will need to provide the Safe Name in CyberArk that contains the Auto-login credentials.
    Note: To see and use this feature, an administrator must have configured the external key vault connection first. For On-Premises users, the external key vault connection is either configured during installation or via the command line utility post install.
    Table 1. Auto-login external key vault mapping examplesFor Auto-login credentials it is expected that the secret name in the external vault contains "autologin_" as a prefix. Additionally, certain key vaults have restrictions on the usage of certain characters in the secret name such as "\" and "@". Auto-login credentials map to the login ID for the credential being retrieved so if the user ID has special characters "\" or "@" the secret name must be encoded using substitutions "\" → "--", "-" → "-2d-", "_" → "-5f-" and "@" → "-2e-". With the exception of the backslash being mapped to double dashes, the dash character, underscore, and at symbol characters are mapped using their ASCII code bracketed in dashes.
    Auto-login UserID AWS Azure CyberArk
    ACME\akshay autologin_ACME--akshay autologin_ACME--akshay autologin_ACME--akshay
    acme\rpa\bhavani autologin_acme--rpa--bhavani autologin_acme--rpa--bhavani autologin_acme--rpa--bhavani autologin_akshay@acme-2e-com autologin_akshay@acme-2e-com autologin_bhavani@rpa-2e-acme-2e-com autologin_bhavani@rpa-2e-acme-2e-com
  4. Choose how to run bots on user sessions by selecting one of the following options:
    • Always create a new session

      Select this option for desktop deployments where it is possible to create user sessions on devices.

    • Reuse an existing session
      Recommendation: Select this option for auto-login settings in the Control Room to use event triggers on unattended Bot Runners and to run bots when a device is locked or is in a disconnected state (such as RDP).

      Available options to lock or unlock the session are:

      • An existing locked session
      • An existing unlocked session
      • A disconnected session
      • Allow users to change these settings for each device

      Use this option for deployments on devices where it is not possible to create user sessions.

      Note: When you use the Reuse an existing session option, ensure user sessions are available. If there is no existing user session, triggers and bot deployments will fail.
    • Reuse an existing session, if available

      Use this option if you must create a new session or reuse an existing session. If a session does not exist, create a new session and leave it unlocked for next user session after bots complete their run from the following:

      • A new session
      • An existing locked session
      • An existing unlocked session
      • A disconnected session
  5. To allow a user to change the auto-login settings at the device level, go to Administration > My Devices and select Allow changes.
    The Do not allow changes option disables the user-level auto-login settings for user sessions.
  6. Save the settings.
Send Feedback
  • Related Content