---
title: Use cases for administrators
description: "What administrators can do in Human Privilege: manage the directory, control access to resources, and monitor activity."
component: privilege
page_id: privilege:human-privilege:admin-use-cases/index
canonical_url: https://docs.pingidentity.com/privilege/human-privilege/admin-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
section_ids:
  before-you-begin: Before you begin
  store-your-credentials: Store your credentials
  directory-management: Directory management
  privileged-access-management: Privileged access management
  activity-monitoring: Activity monitoring
---

# Use cases for administrators

As an administrator, you use Human Privilege to control and monitor how people in your organization reach privileged resources. Your work falls into three areas: directory management, privileged access management, and activity monitoring.

## Before you begin

Ensure the foundational setup for Human Privilege is complete:

* You can [access the admin console](../../getting-started/accessing-admin-console.html).

* You followed the [Configuration guide](../configuration/index.html) to set up cloud accounts, gateways, and access protocols and onboarded resources your users can request access to.

* Tenant-wide options, such as session logging and MFA enforcement, are set in [Tenant settings](../getting-started-admin/tenant-settings.html).

## Store your credentials

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

## Directory management

The directory holds the users, groups, devices, and service accounts that can reach privileged resources. You can:

* [Manage users](directory-management/users.html): Onboard and manage the people who request access.

* [Manage groups](directory-management/groups.html): Organize users for policy assignment.

* [Manage devices](directory-management/devices.html): Onboard and manage the devices users sign on from.

* [Manage service accounts](directory-management/service-accounts.html): Provide credential-based access for non-human consumers such as internal applications.

## Privileged access management

This is where you decide who can reach what, and when:

* [Manage access policies](access-management/policies.html): Grant access automatically based on criteria, with time-bound windows.

* [Manage passwordless access](access-management/passwordless-access.html): Configure access that requires no static credentials.

* [Manage access requests](access-management/access-requests.html): Approve, reject, or revoke the JIT requests users submit, and set up auto-approval policies.

* [Manage targets and resources](access-management/cloud-accounts.html): Onboard cloud accounts and bring their resources into PingOne Privilege as targets users can request.

## Activity monitoring

Every request, session, and approval is logged. You can:

* [Manage activity logs](activity/activity-logs.html): Review what actions were performed on resources and by whom.

* [Manage session logs](activity/session-logs.html): Review and mark audited the sessions opened through PingOne Privilege.

* [Manage access request approval logs](activity/access-request-approval-logs.html): Trace who approved which access requests and when.