> For the complete documentation index, see [llms.txt](https://newdocs.keeper.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://newdocs.keeper.io/en/keeperpam/privileged-access-manager/just-in-time-access-jit/elevated-access-on-endpoints.md).

# Elevated Access on Endpoints

Control privilege elevation on end-user devices with Keeper Privilege Manager.

## **Overview**

Keeper Privilege Manager extends JIT capabilities to endpoints, allowing administrators to grant precise privilege elevation for specific processes, applications, or tasks — without giving users full administrative access. Users operate with standard, non-privileged accounts by default and request elevation only when needed.

**Key Features**

* Process-level privilege management across Windows, macOS, and Linux
* Policy-based elevation rules with granular controls
* User-initiated elevation requests with approval workflows
* Comprehensive auditing and reporting

**How It Works**

1. Users operate with standard, non-privileged accounts by default.
2. When administrative privileges are needed, users request elevation for a specific task.
3. Based on policy, requests are auto-approved or routed for manual approval.
4. Elevated privileges are granted only for the specified process or time window.
5. All elevation activity is captured in a full audit trail.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FN3gWraxTdAXjhJWah30w%2Fimage.png?alt=media&amp;token=02682396-59a9-4ca5-b975-c9e811823480" alt=""><figcaption></figcaption></figure>

### Where to go next

Endpoint JIT on user devices is delivered through **Keeper Endpoint Privilege Manager**.

If you want to understand the product and rollout model, start with the [Endpoint Privilege Manager overview](/en/keeperpam/endpoint-privilege-manager/overview.md).

If you are ready to enable and deploy it, continue to [Getting Started](/en/keeperpam/endpoint-privilege-manager/setup.md).

Common next steps:

* Review the product overview and policy model in [Endpoint Privilege Manager](/en/keeperpam/endpoint-privilege-manager/overview.md).
* Set up licensing, permissions, and agent deployment in [Getting Started](/en/keeperpam/endpoint-privilege-manager/setup.md).
* Learn how day-to-day approvals work in [Managing Requests](/en/keeperpam/endpoint-privilege-manager/managing-requests.md).


---

# 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://newdocs.keeper.io/en/keeperpam/privileged-access-manager/just-in-time-access-jit/elevated-access-on-endpoints.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.
