DocumentationAPI ReferenceRelease Notes
Documentation

Accounts tab | PS Cloud

What is the Accounts tab?

The Accounts tab lists the managed accounts for which you have permissions to request access to retrieve passwords and start sessions.

How is it useful?

From this grid, you can initiate an access request for the listed accounts, streamlining the request process. By populating the grid with managed accounts, users can easily see which accounts are available and take action without needing to navigate to other areas of the console You can populate the list of managed accounts in the grid using any one of the following options:

  • Click the Browse by Category buttons to filter the list by category.
  • Select filter criteria from the Filter by dropdown to filter by selected account properties.
  • Search for accounts using the Quick Filter option.
  • Click Load All Accounts to load all associated accounts.

How do I access the Accounts tab?

  1. Use a browser to sign in to your BeyondInsight/Password Safe URL.
    This URL is provided in the BeyondTrust welcome email and includes your site URL followed by /login.
  2. From the left menu, click Password Safe icon.
    The Password Safe home page displays.
  3. Click the Accounts tab.
    The Accounts grid displays.
ℹ️

  • For optimum efficiency, the web portal screen resolution should be no less than 1280 × 800 pixels.
  • When you first log in to the Password Safe web portal, no accounts are available in the Favorites grid. Click the star next to any account to add it to the Favorites grid. Click Refresh above the grid to update the listed accounts.

The Accounts grid

Password Saffe Cloud Accounts tab
  1. Browse by different categories to filter results in the grid.
  2. Select Filter by to further filter results.
  3. Accounts grid.

Request a password release

To request a password release:

  1. Click Access icon to the right of the managed account.
    The Access panel displays.
  2. Select the Start Session tab.
  3. Enter a Reason for the password release.
  4. Select a ticket system and provide a ticket number if required.
  5. Check required options under Advanced Request Options.
  6. Click Start RDP Session. An RDP connection file downloads with a one-time use token that expires based on the Session Initialization timeout settings.
  7. Run the file to establish a connection to the target system.
  8. Enter the password that you use to authenticate into Password Safe.
  9. Click Access for the managed account for which you wish to request a password.
  10. From the Submit Request tab:
    • Set a start date and time for the password to be made available.
    • Set the length of time for the password to be available.
    • Check Password for the type of access you need.
    • Provide a reason for the request. The maximum allowed length is 200 characters.
    • Select a ticket system and provide a ticket number.
ℹ️

Reason, Ticket System, and Ticket Number fields might be optional or required, depending upon options configured in the access policy by your Password Safe administrator. Also, if your Password Safe administrator has set a specific ticket system in the access policy, you cannot select a different ticket system with your request.

  1. Click Submit Request. An email is sent to the approver if email notification is configured. You can view the status of your request from the Requests tab.

Retrieve a password

To retrieve a password:

  1. Click Access icon to the right of the managed account.
    The Access panel displays.
  2. Select the Start Session tab.
  3. Enter a Reason for the password retrieval.
  4. Select a ticket system and provide a ticket number if required.
  5. Check required options under Advanced Request Options.
  6. Click Retrieve Password to display the system account password.
  7. The password displays in a separate window. The visibility of the password might be limited, with a timer showing remaining time. Click Close Window to close the windows before the timeout.
  8. Click Copy icon to copy the password to the clipboard.
  9. Use the password to log in to the system within the password release time period.

Retrieve a password using Quick Launch

If your access policy is configured for auto-approval for the managed system account you are accessing, Quick Launch is available and allows you to quickly retrieve the password for the managed account, bypassing the approval process. To use Quick Launch:

  1. Click Access icon to the right of the managed account.

  2. From the Quick Launch tab, click Retrieve Password.

  3. Click Show to display the password or click Copy icon to copy it to the clipboard.

Account tags

You can now create and assign tags directly from the Accounts tab.

Tags help you organize and quickly identify managed account and system pairs using customizable labels. Each tag includes a user-defined name and a color selected from a predefined set, making it easier to visually group related resources.

Users with access to the Accounts tab can create, edit, delete, and assign tags to any accounts they can view. When filtering, tags use OR logic, so any account or managed system pair that includes at least one selected tag appears in the results.

Tags are associated with specific Managed Account and Managed System pairs and do not support column sorting.

ℹ️

Tags are visible to all users. If multiple users have requestor access to the same account, all of them can view and access any tags assigned to that account.

Add a tag

  1. From the left menu, click Password Safe icon.
    The Password Safe home page displays.
    When opened, the Password Safe page displays the Accounts tab.
  2. Click Manage Tags.
    The Manage Tags dialog box displays.
  3. Click Create Tag.
  4. For Tag Label, provide a unique name. For example, Production.
  5. For Tag Color, accept the default color or click the dropdown box to select a specific color.
  6. Click Create Tag.

Edit a tag

  1. From the left menu, click Password Safe icon.
    The Password Safe home page displays.
    When opened, the Password Safe page displays the Accounts tab.

  2. Click Manage Tags.
    The Manage Tags dialog box displays.

  3. Select a tag from the list and click the pencil icon to edit.
    The Edit Tag dialog box displays.

  4. Make the necessary changes and click Save Changes.

Delete a tag

  1. From the left menu, click Password Safe icon.
    The Password Safe home page displays.
    When opened, the Password Safe page displays the Accounts tab.

  2. Click Manage Tags.
    The Manage Tags dialog box displays.

  3. Select a tag from the list and click the trash can icon to delete.
    The Edit Tag dialog box displays.

  4. Click Delete from the confirmation dialog box.

✅

Example

This example displays how to create, edit, and delete a tag.


Assign a tag to an account

Tags are applied to a local account or managed system pair. To assign a tag to an account do the following:

  1. From the left menu, click Password Safe icon.
    The Password Safe home page displays.
    When opened, the Password Safe page displays the Accounts tab.
  2. Click the Local Accounts tab.
  3. Click Load All Accounts.
  4. From the table, select one or more accounts to assign a tag.
  5. Click Assign Tags.
    The Assign Tags dialog box displays.
  6. Click the appropriate tag to assign.
  7. Click Save.

The tag is assigned to the account and displays in the Tags column of the table.

ℹ️

The maximum number of tags you can create is 32. Once the limit is met, the following error message displays: The maximum number of tags exist.

Request SSH or RDP Sessions

When configured by your Password Safe administrator, you can request access to a managed system using a remote session. Using the Password Safe request and approval system, you can request remote sessions that use RDP and SSH connection types.

Password Safe acts as a proxy, providing session management to target systems. No passwords are transmitted, allowing inherently secure session management. The below sections detail how to request and start sessions in Password Safe.

Request an RDP session

  1. Click Access icon to the right of the managed account.
    The Access panel displays.
  2. Select the Start Session tab.
  3. Enter a Reason for the RDP session.
  4. Select a ticket system and provide a ticket number if required.
  5. Check required options under Advanced Request Options.
  6. Click Start RDP Session. An RDP connection file downloads with a one-time use token that expires based on the Session Initialization timeout settings. Run the file to establish a connection to the target system.
  7. Enter the password that you use to authenticate into Password Safe.
  8. Click Access to the right of the managed account to request a session.
  9. From the Submit Request tab:
    • Set a session start date and time that corresponds with the access policy and is outside of a scheduled maintenance window.
    • Set the length of time for the session.
    • Check RDP Session for the type of access you need.
    • Provide a reason for the request. The maximum allowed length is 200 characters.
    • Select a ticket system and provide a ticket number.
ℹ️

Reason, Ticket System, and Ticket Number fields may be optional or required, depending upon options configured in the access policy by your Password Safe administrator. Also, if your Password Safe administrator has set a specific ticket system in the access policy, you cannot select a different ticket system with your request.

  1. Click Submit Request. An email is sent to the approver if email notification is configured.

Use Direct Connect for RDP session

You can also use the Direct Connect feature to initiate an RDP session. As the requester, you can access the system without ever viewing the managed account's credentials.

To use Direct Connect, you must download the RDP file from the Password Safe web portal. This is a one-time download. Each account and system combination requires that you download the unique RDP file associated with it.

If the requestor is granted approval for RDP sessions, a message displays, stating, Request requires approval. If the request is not approved within 5 minutes, this connection will close. After five minutes, the RDP client disconnects, and then you can send another connection request. When the request is approved, you are automatically connected.

To initiate a Direct Connect RDP session:

  1. Click Access icon to the right of the managed account.
    The Access panel displays.
  2. Select the Start Session tab.
  3. Enter a Reason for the direct connect session.
  4. Select a ticket system and provide a ticket number if required.
  5. Check required options under Advanced Request Options.
  6. Click Start RDP Session. An RDP connection file downloads with a one-time use token that expires based on the Session Initialization timeout settings. Run the file to establish a connection to the target system.
  7. Run the file to establish a connection to the target system.
  8. Enter the password that you use to authenticate into Password Safe.
  9. Find the account in the list. Click Access to the right of the managed account to request a session.
  10. From the Direct Connect tab, click Download RDP File.
  11. Run the file to establish a connection to the target system.
  12. Enter your password that you use to authenticate into Password Safe.
ℹ️

  • RDP Direct Connect supports only push two-factor authentication. An access-challenge response is not supported.
  • LDAP users that use the mail account naming attribute cannot use RDP Direct Connect.

Start an RDP session without submitting a request

Users who have permissions to bypass the request and approval process for accessing the managed system and Password Safe administrators are able to start sessions and retrieve passwords immediately from the Start Session tab. The Start Session tab does not display for users who do not have permissions to bypass the request and approval process. To start the session:

  1. Click Access icon to the right of the managed account.
    The Access panel displays.
  2. Select the Start Session tab.
  3. Enter a Reason for the RDP session.
  4. Select a ticket system and provide a ticket number if required.
  5. Check required options under Advanced Request Options.
  6. Click Start RDP Session. An RDP connection file downloads with a one-time use token that expires based on the Session Initialization timeout settings. Run the file to establish a connection to the target system.
  7. Run the file to establish a connection to the target system.
  8. Enter the password that you use to authenticate into Password Safe.

SSH Direct Connect

Using an SSH client, a user can use the Password Safe Request and Approval system for SSH remote connections. The requester's information, including the Reason and the Request Duration, are auto-populated with default Password Safe settings.

To access a managed account or application using Direct Connect, the requester has to connect to Password Safe's SSH Proxy using a custom SSH connection string with one of the following formats:

  • For UPN credentials:
    <Requester>+<Username@Domain>+<System Name>@<Password Safe>
  • For down-level logon names\non-domain credentials:
    <Requester>@<Domain\\Username>@<System Name>@<Password Safe>

You can override the default SSH port and enter port 4422. The requester is then prompted to enter their password, which they use to authenticate with Password Safe.

  • For UPN credentials:
    ssh -p 4422 <Requester>+<Username@Domain>+<System Name>@<Password Safe>
  • For down-level logon names\non-domain credentials:
    ssh -p 4422 <Requester>@<Domain\\Username>@<System Name>@<Password Safe>
  • For an SSH application:
    ssh -p 4422 <Requester>@<Account name>:<Application alias>@<System name>@<Password Safe>

Once the requester is authenticated, they are immediately connected to the desired machine.

Direct Connect in Pathfinder

Direct Connect lets you open an SSH or RDP session from the tools you already use, such as PuTTY, a terminal, or Remote Desktop. You don't need to open the Password Safe web portal first.

Here is what happens when you connect:

  1. You connect to the Password Safe session proxy instead of the target system.
  2. Password Safe checks who you are.
  3. Password Safe checks the access policy and creates a request for you.
  4. If the request is approved, Password Safe signs you in to the target system with the managed account.

You never see the managed account's password. Password Safe records and monitors the session based on your access policy.

Direct Connect is part of the BeyondTrust Total Privileged Account and Session Management (Total PASM) solution. Total PASM brings together credential management and session management, so your team controls both the password and the session.

Key concepts

TermWhat it means
RequesterYou. The person who asks for access.
Managed accountThe privileged account Password Safe controls, such as a local admin or root account.
Managed systemThe server or device you want to reach.
Session proxyThe Password Safe service that sits between you and the target system. It injects the credentials and records the session.
Connection stringThe text you enter in your SSH client. It tells Password Safe who you are, which account you want, and which system you want to reach.
Access policyThe rules your administrator sets. Policies decide when you can connect, for how long, and whether someone must approve.
Personal access token (PAT)A secret value you create in your profile. In Pathfinder, you enter your PAT instead of a password when you use Direct Connect.
Auto-approvalA policy setting that approves your request right away. Without it, an approver must act within 5 minutes.

What is Direct Connect?

Direct Connect works the same way in Pathfinder as before. The biggest change is how you prove who you are.

AreaBefore Pathfinder (on-premises and Cloud)Pathfinder
Where you sign inThe Password Safe web portal for your instance.app.beyondtrust.io, through your organization's identity provider.
What you enter at the Direct Connect promptYour Password Safe password. A PAT is optional.Your PAT. Your password does not work.
Multi-factor authentication (MFA)Supported. For RDP, enter password, token, or approve a push request. For SSH, Password Safe prompts for a token after your password.Not available with Direct Connect. The PAT replaces both the password and the MFA step.
Credential you manageYour directory or Password Safe password. It changes on your password schedule.A token you create, name, and revoke yourself. It expires on the date you choose, up to your administrator's limit.
SSH connection stringssh -p 4422 <Requester>+<Username@Domain>+<System Name>@<Password Safe>Same format. Enter your PAT when prompted.
RDP fileFor convenience, download a one-time RDP file from the portal, then enter your password. Conversely, you can use this syntax:
<Requester>+<Managed Account>+<Managed System>@<Password Safe>:4489
For convenience, download a one-time RDP file from the portal, then enter your PAT.
Conversely, you can use this syntax:
<Requester>+<Managed Account>+<Managed System>@<Password Safe>:4489
Approval flowAuto-approval connects you right away. Otherwise, an approver has 5 minutes.Same.
Session recording and monitoringBased on your access policy.Same.

Before you begin

  • Your administrator turns on personal access tokens. For more information, see Configure PAT tokens.
  • Your administrator gives you access to the managed account through an access policy.
  • For SSH, install an SSH client, such as PuTTY or OpenSSH.
  • Create a personal access token and save it somewhere safe.

Use Direct Connect for SSH

  1. Open your SSH client.
  2. Connect to the Password Safe SSH proxy on port 4422. Use the format that matches the account:
    • UPN credentials:

      ssh -p 4422 <Requester>+<Username@Domain>+<System Name>@<Password Safe>
    • Down-level logon names or non-domain credentials:

      ssh -p 4422 <Requester>@<Domain\\Username>@<System Name>@<Password Safe>
    • SSH application:

      ssh -p 4422 <Requester>@<Account name>:<Application alias>@<System name>@<Password Safe>
  3. When prompted for a password, paste your PAT.
  4. If your request needs approval, a message displays: Request requires approval. Wait for the approver. If no one approves within 5 minutes, the connection closes. You can try again.
  5. After approval, Password Safe connects you to the target system.
✅

Example

Jordan needs root access on a Linux server named web01.

  1. Jordan runs the following syntax:

    ssh -p 4422 jordan+root+web01@<Password Safe>

  2. Jordan pastes a PAT at the prompt. The policy auto-approves the request, and Jordan lands on web01 as root. Jordan never sees the root password.

Use Direct Connect for RDP

  1. Go to ☰ > Password Safe > Password Safe Accounts.

  2. Click the download arrow next to the managed account to download the RDP Direct Connect file. Each account and system pair has its own file.

  3. Run the RDP file.

    ℹ️

    The Direct Connect file is intended to be saved and re-used (that is, you do not have to continually log back in to the Web console to download the RDP file for the same account & system every time you want to use it.

  4. When prompted for a password, paste your PAT.

  5. If your request needs approval, wait for the approver. After approval, Password Safe connects you to the target system.

Important

  • Direct Connect does not support MFA when you use a PAT.
  • Direct Connect does not work with Microsoft Entra ID accounts.
  • LDAP users whose naming attribute is the mail account cannot use RDP Direct Connect.

Tips for using Direct Connect

  • Reuse requests. If you already have an open request for the same account and system, Password Safe reuses it.
  • Use short token lifetimes. Create a PAT that lasts only as long as you need it.
  • Use one token per purpose. For example, use one PAT for Direct Connect and a different one for scripts. If one leaks, revoke it without breaking the other.
  • Revoke tokens you no longer use. A revoked token stops working right away.

Personal access tokens

A personal access token (PAT) is a secret value that proves who you are. You use it instead of your password for Direct Connect and the public API. You create and manage your own tokens. Administrators view token details and revoke tokens when needed.

Important

  • Pathfinder requires a PAT for Direct Connect. You cannot use your password to authenticate.
  • MFA is not available when you use Direct Connect with a PAT.
ℹ️

Personal access tokens work in on-premises, Cloud, and Pathfinder deployments. On-premises and Cloud deployments still accept passwords for backward compatibility.

Create a Personal Access Token

To create and manage personal access tokens is performed from your profile settings.

  1. Click Profile and preferences in the upper-right hand corner.

  2. Click Account Settings.

  3. Navigate to Personal Access Tokens.

  4. Select Create Token.

    Create Token
  5. Configure the token settings, such as expiration (for example, one day).

  6. Copy the token value for immediate use.

    Copy the personal access token
  7. Click Close.

Important

Password Safe shows the token value only once, when you create it. Save it in a secure place, such as a password manager.

View and manage tokens

You can view existing tokens, including expiration details as well revoke tokens at any time.

To view token metadata for an existing token, do the following:

  1. Click Profile and preferences in the upper-right hand corner.
  2. Click Account Settings.
  3. From My Account pane, select Personal Access Token.

    The Personal Access Token table displays with metadata (that is, Token Description, Issued Date, Expiry Date, etc.)

Revoke a token

To revoke tokens, do the following:

  1. Click Profile and preferences in the upper-right hand corner.

  2. Click Account Settings.

  3. From My Account pane, select Personal Access Token.

    The Personal Access Token table displays.

  4. Select an existing token from the table.

  5. Click Revoke.

    Revoke a token
  6. The following confirmation dialog box displays:

    Revoke token confirmation dialog
  7. Click Revoke Token.

Important

When you revoke a token, it immediately invalidates them. Any connection attempt using the revoked token fails.

Authenticate using a Personal Access Token

Users can authenticate with a personal access token instead of a password. They can use the token for Direct Connect authentication or for Public API authentication.

The platform continues to support password-based authentication, ensuring full backward compatibility across on-premises and cloud environments.

✅

Best practice

Use personal access tokens instead of passwords. Tokens lower the risk of exposing your main sign in credentials.

Administrator capabilities

Administrators manage personal access tokens at both the system and user levels.

View and revoke tokens (System level)

Administrators can review system-wide token metadata across all users. They can also review token metadata for suspicious or unused tokens and select tokens and revoke them as needed.

View and revoke tokens (User level)

Administrators can also manage tokens for individual users by viewing the user's profile and associated PATs. They can also revoke tokens directly from the user account.

Configuration

Enable or disable Personal Access Tokens

To configure the global settings for PAT, go to Configuration > Authentication Management > Authentication Options.

To allow token creation and usage, click Enabled. To disable the feature entirely, unselect the Enabled check box.

Personal Access Tokens authentication options

Important

Pathfinder users need a PAT to use Direct Connect. If you turn off personal access tokens, Pathfinder users cannot use Direct Connect.

Set token policies

To define usage limits and security controls, set either of these settings:

  • Maximum Token Lifetime (days) (default: 90 days)
  • Maximum Active Tokens per user (default: 5 tokens)
ℹ️

These settings help enforce security and limit the number of active tokens.

Require tokens for API authentication

To require personal access tokens for public API authentication, you need to select the Personal access token required checkbox. This applies rules that enforce token-based authentication.

Personal access token required for API

Security tips

  • Use tokens instead of passwords for scripts and repeated access.
  • Keep token lifetimes short.
  • Revoke tokens that are unused or look suspicious.
  • Require tokens for API sign in when you can.

©2003-2026 BeyondTrust Corporation. All Rights Reserved. Other trademarks identified on this page are owned by their respective owners. BeyondTrust is not a chartered bank or trust company, or depository institution. It is not authorized to accept deposits or trust accounts and is not licensed or regulated by any state or federal banking authority.