Account groups | PRA Pathfinder

What are account groups?

Vault account groups are collections of user accounts within the Vault system, organized based on access permissions or roles. These groups are used to streamline the management of shared Vault accounts that enable Vault administrators to efficiently grant users access to multiple shared accounts. Account groups can also associate a group of shared Vault accounts with a specific group policy.

ℹ️

Shared Vault accounts can only belong to one group at a time, and personal Vault accounts cannot be added to an account group.

How are account groups useful to my organization?

Account groups help simplify credential management which allow administrators to assign access to multiple shared Vault accounts at once. This ensures efficient and controlled access for users. These groups also provide an effective way to apply policies to a collection of shared accounts which enhance security and compliance while reducing administrative overhead.

How do I access the Account Groups page?

  1. Sign into app.beyondtrust.io.
    The BeyondTrust Home page displays.
  2. From the main menu, click Privileged Remote Access > Vault.
    The Vault page opens and the Accounts tab displays by default.
  3. Click the Account Groups tab.
    The Account Groups tab displays.

The Account Groups page

Vault admins can use account groups to logically group credentials together, granting users access to multiple shared Vault accounts at one time. Account groups can also be associated to a group policy, allowing policy members to access that group of shared Vault accounts.

The image shows a user interface for managing account groups in a privileged remote access vault. The interface includes navigation elements, account group listings, and options to add or edit groups.
  1. Left menu: Easy access to all pages in Privilege Remote Access, including Status, Consoles & Downloads, My Account, Configuration, Asset Management, Vault, Console Settings, Users & Security, Reports, Management, and Appliance pages.
  2. Status: Opens the Status page.
  3. Header: Change your tenant site, manage your profile, and access documentation.
  1. Add: Add a new Account Group.

  2. Filter: Search on a Name or Description.

  3. Account Groups columns: The list of columns varies on what columns you choose to display.

    Account Groups columns
    • Name: Unique name of the account.
    • Description: A brief description of the Account Group.
    • Account Policy: Select an existing policy or specify a custom policy.
  4. Account Groups options: Edit an Account Group or delete an Account Group.

Add an Account Group

  1. Sign into app.beyondtrust.io.
    The BeyondTrust Home page displays.

  2. From the main menu, click Privileged Remote Access > Vault.

  3. The Vault page opens and the Accounts tab displays by default.

  4. Click the Account Groups tab.

  5. Click Add.
    The Add Account Group page displays.

  6. In the Name field, enter a name for the account.

  7. In the Description field, enter a useful description for the account.

  8. Select a specific policy for the account group or leave Account Policy set to the default value of Inherit Policy Settings. If Inherit Policy Settings is selected, the accounts in this account group inherit the policy settings set for the global default account policy on the Vault > Options page.

  9. Under Accounts, select the group from the Source Account Group list, and then select the accounts to add to this group.

    ℹ️

    The Default Group is a system generated group that contains all user accounts that do not belong to an account group. The Default Group is selected by default.

    You can filter the list of available accounts to add to the group by selecting a group from the Source Account Group list or by using the Search Selected Account Group box to search by Name, Endpoint, and Description.

  10. Click Add to move the accounts over to the Accounts in This Group list.

  11. In the Allowed Users section, add a user and select their Vault role from the New Member Role dropdown, and then click Add. Users can be assigned one of two member roles:

    • Inject: Users with this role can use this account in Secure Remote Access sessions (default value).
    • Inject and Checkout: Users with this role can use this account in Secure Remote Access sessions and can check out the account on Support for Admins. The Checkout permission has no effect on generic SSH accounts.
  12. Select the type of Asset Associations for the account. The Asset Associations setting determines which Assets the account is associated with, so the account is available only for relevant target computers in the console during credential injection attempts.

    Select one of the following types:

    Asset Association TypeDescription
    Inherited from the Account GroupAssociations for this account are determined by the associations defined in this account's Account Group.
    Any AssetsThis account can be injected within any session started from an Asset in which the account is applicable. The applicable accounts are the following:
    • Local Accounts- discovered on a Vault Endpoint are available for injection on Assets targeting the Endpoint.
    • Domain Accounts- are available for injection on Assets targeting Vault Endpoints on the Domain.
    • All Domain Accounts- are available for injection on Assets targeting remote systems that do not match a Vault Endpoint.
    • Shared Generic Username & Password Accounts- are available for injection into all Assets.
    • Shared Generic SSH Accounts- are available for injection into all Shell Assets.
    • Shared Generic Token Accounts- are available for injection into all Kubernetes Cluster Tunnel Assets.


    ℹ️ Personal Assets are not supported.
    No AssetsThis account cannot be injected into any session started from an Asset.
    Assets Matching CriteriaThis account can be injected only within sessions started from Assets that match the criteria you define, in which the account is applicable. The applicable accounts are the following:
    • Local Accounts- discovered on a Vault Endpoint are available for injection on Assets targeting the Endpoint.
    • Domain Accounts- are available for injection on Assets targeting Vault Endpoints on the Domain.
    • All Domain Accounts- are available for injection on Assets targeting remote systems that do not match a Vault Endpoint.
    • Shared Generic Username & Password Accounts- are available for injection into all Assets.
    • Shared Generic SSH Accounts- are available for injection into all Shell Assets.
    • Shared Generic Token Accounts- are available for injection into all Kubernetes Cluster Tunnel Assets.

    ℹ️ Personal Assets are not supported.

    If the Asset Attributes section is configured, this list combines with any Assets that match the criteria.

    The following Connection Types are supported:
    • Jump Client
    • Remote RDP
    • Remote Jump
    • SSH
    • Database Connection
    • Website

    Injection is not supported for the following items:
    • Personal Assets
    • TCP Tunnel Database Connections
    • IP Tunnel Database Connections
ℹ️

You can define a direct association between Vault accounts and specific Assets by selecting the Assets from the list and then click Add Asset.

If configured, the account is available for injection for any Assets that match the specified attribute criteria in addition to any specific Assets you added as matching criteria.

Local accounts are available for injection within the endpoints on which they were discovered.

You can further define the association between Vault accounts and Assets by specifying matching criteria. Each of the following values have a maximum length of 64 characters and can contain a maximum of 32 values.

The different Asset attributes are the following:

  • Name: This filter is matched against the value that appears in the Name column of the Asset in the console.

  • Hostname / IP: This filter is matched against the value that appears in the Hostname / IP column of the Asset in the console.

  • Tag: This filter is matched against the value that appears in the Tag column of the Asset in the console.

  • Comments: This filter is matched against the value that appears in the Comments column of the Asset in the console.

    For example, a list of filter criteria is:

CriteriaResult
valuematches the field exactly.
value*matches the field as a prefix.
*valuematches the field as a suffix.
**value**matches if the field contains the value
  1. Click Save at the top of the page.

Add an Account Group to an existing shared account

  1. Sign into app.beyondtrust.io.
    The BeyondTrust Home page displays.
  2. From the main menu, click Privileged Remote Access > Vault.
    The Vault page opens and the Accounts tab displays by default.
  3. From an existing shared account, click the ellipsis button, and then select Edit.
  4. Select the group from the Account Group list, and then click Save.

Import a discovered account

  1. Sign into app.beyondtrust.io.
    The BeyondTrust Home page displays.

  2. From the main menu, click Privileged Remote Access > Vault.
    The Vault page opens and the Accounts tab displays by default.

  3. Click the Discovery tab.

  4. From the Discovery Jobs section, select a Discovery Job.

  5. Click View Results for the job.

  6. Select the Local Accounts or Domain Accounts tab as applicable.

  7. From the list of accounts, select the account you wish to import.

  8. Click Import Selected.

  9. Select the group from the Account Group list.

  10. Click Start Import.

Add an account group to a group policy

  1. Sign into app.beyondtrust.io.
    The BeyondTrust Home page displays.

  2. From the main menu, click Privileged Remote Access > Users & Security.
    The User page opens and displays by default.

  3. Click the Group Policies tab

  4. From the list of existing group policies, click the pencil Image of the Edit icon to edit a policy.

  5. Scroll down to the Memberships section.

  6. Check the Add Vault Account Group Memberships checkbox.

  7. Select the Account Group from the list.

  8. Select the Vault Account Role from the list.
    Users can be assigned one of two member roles:

    • Inject: Users with this role can use this account in Secure Remote Access sessions (default value).
    • Inject and Checkout: Users with this role can use this account in Secure Remote Access sessions and can check out the account on Support for Admins. The Checkout permission has no effect on generic SSH accounts.
  9. Click Add.

  10. Click Save at the top of the page.

  11. The group policy and its Vault account role are now displayed under the Group Policies section for the account group that was added to the policy.

  12. The members of the group policy are now added under Allowed Users for the account group.

ℹ️

If a user was granted access individually from the account group edit page and also through a group policy, the group policy access is overridden by the explicitly granted individual access for this user.

Search Account Groups

You can filter the list of available account groups by using the Search Account Groups box. Based on the account type, you can use Name or Description as the criteria to search.

Edit an Account Group

  1. Sign into app.beyondtrust.io.
    The BeyondTrust Home page displays.

  2. From the main menu, click Privileged Remote Access > Vault.
    The Vault page opens and the Accounts tab displays by default.

  3. Click the Account Group tab.
    The Account Groups page displays.

  4. Select a group in the list.

  5. Click the pencil Image of the Edit icon to edit a group.

  6. Make the necessary changes, and then click Save.

Delete an Account Group

  1. Sign into app.beyondtrust.io.
    The BeyondTrust Home page displays.

  2. From the main menu, click Privileged Remote Access > Vault.
    The Vault page opens and the Accounts tab displays by default.

  3. Click the Account Group tab.
    The Account Groups page displays.

  4. Select a group in the list.

  5. Click the trash can Image of the Delete icon. to delete a group.

  6. Click Yes.


©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.