> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell-universal/powershell-commands/get-psuusersession.md).

# Get-PSUUserSession

Query connected PowerShell Universal user sessions by ID, source, user, or computer.

## SYNOPSIS

Gets PowerShell Universal user sessions.

## SYNTAX

```powershell
Get-PSUUserSession -Id <Int64> [<ConnectionOptions>] [<CommonParameters>]
Get-PSUUserSession [-Source <String>] [-UserName <String>] [-ComputerName <String>] [<ConnectionOptions>] [<CommonParameters>]
```

`<ConnectionOptions>`: `[-AppToken <String>] [-Credential <PSCredential>] [-UseDefaultCredentials] [-Integrated] [-TrustCertificate] [-Cookies]`. For this command, `-ComputerName` in the listing parameter set filters sessions by the computer that owns them; it is not a Management API target. Connect to the desired PSU server first with `Connect-PSUServer`.

## DESCRIPTION

Retrieves user-session records. Use the singular command name; it replaces the formerly exported `Get-PSUUserSessions` command. The listing filters support wildcards. Use `-Id` to retrieve a single session instead of combining it with list filters.

## EXAMPLES

```powershell
Get-PSUUserSession
Get-PSUUserSession -Id 10
Get-PSUUserSession -UserName 'admin'
Get-PSUUserSession -Source 'Dashboard'
Get-PSUUserSession -ComputerName 'server01'
```

## PARAMETERS

| Parameter                | Description                                                                                       |
| ------------------------ | ------------------------------------------------------------------------------------------------- |
| `-Id`                    | Required numeric ID of one session (Id parameter set).                                            |
| `-Source`                | Source filter; supports wildcards (All parameter set).                                            |
| `-UserName`              | Username filter; supports wildcards (All parameter set).                                          |
| `-ComputerName`          | Computer owning the session; supports wildcards (All parameter set), not a target PSU server URL. |
| `-AppToken`              | Management API app token.                                                                         |
| `-Credential`            | Management API credentials.                                                                       |
| `-UseDefaultCredentials` | Uses current Windows credentials.                                                                 |
| `-Integrated`            | Uses the in-process management client.                                                            |
| `-TrustCertificate`      | Ignores certificate validation errors.                                                            |
| `-Cookies`               | Reuses session authentication cookies.                                                            |

## OUTPUTS

`PowerShellUniversal.UserSession`.

## PERMISSIONS

The access token requires `platform.usersessions/read` to run this cmdlet remotely.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/powershell-universal/powershell-commands/get-psuusersession.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
