---
title: Use cases for users
description: "What users can do in Human Privilege: request access to resources, manage requests, manage devices, and view activity."
component: privilege
page_id: privilege:human-privilege:user-use-cases/index
canonical_url: https://docs.pingidentity.com/privilege/human-privilege/user-use-cases/index.html
llms_txt: https://docs.pingidentity.com/privilege/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: September 10, 2026
page_aliases: ["human-privilege:user-use-cases/request-access/cloud.adoc", "human-privilege:user-tasks/cloud/cloud.adoc", "privileged-access-management:user-tasks/cloud/cloud.adoc"]
section_ids:
  before-you-begin: Before you begin
  store-your-credentials: Store your credentials
  request-access-to-resources: Request access to resources
  manage-your-access-requests: Manage your access requests
  manage-your-devices: Manage your devices
  view-your-activity: View your activity
---

# Use cases for users

As a user, you use Human Privilege to reach the resources you need through the PingOne Privilege user console and the Endpoint Controller, with access granted just in time rather than standing permanently. Your work falls into four areas: requesting access, managing your requests, managing your devices, and viewing your activity.

## Before you begin

Ensure the following:

* An administrator has [granted you access to the user console](../getting-started-users/accessing-user-console.html).

* Your administrator onboarded you with a way to access the user console:

  * For Endpoint Controller-based deployments, the Endpoint Controller is installed on your device and connected.

  * For No Endpoint Controller-based deployments, you're able to sign on through PingOne single sign-on (SSO).

* The resources you need exist as targets in PingOne Privilege. If a resource you need isn't listed, ask your administrator to onboard it.

## Store your credentials

Users can use PingOne Privilege to store their own credentials for the backend systems they access with the [User Vault](user-vault.html).

## Request access to resources

Request just-in-time access to the resource types your organization manages with PingOne Privilege:

* [Cloud virtual servers](request-access/servers.html): AWS EC2, Google Compute, and Azure VMs.

* [Databases](request-access/databases.html): Discovered database targets.

* [Remote Desktop](request-access/remote-desktop.html): Windows servers over RDP.

* [AWS IAM roles](request-access/aws-role-cli.html): Access through the AWS CLI.

* [Kubernetes clusters](request-access/kubernetes-clusters.html): EKS, AKS, and GKE clusters.

* [Azure subscriptions](request-access/cloud-resources.html): Azure cloud resources.

* [On-premise applications](request-access/applications.html): Applications behind a gateway.

Prerequisite: access requests follow your organization's approval workflow. Some requests might be granted automatically by policy; others wait for an administrator to approve them.

## Manage your access requests

After you submit a request, you can [manage your access requests](access-request-management/access-requests.html) to track their approval status and view the details of your current grants. You can also [view policy details](access-request-management/policies.html) that apply to your requests.

## Manage your devices

[Manage your devices](devices.html): View the devices you sign on from, activate a new device, or remove one you no longer use.

## View your activity

[View your activity logs](activity-logs.html): See a record of your own access activity, including the resources you reached and when.