> 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/jit-integrations.md).

# JIT Integrations

ITSM and ChatOps integrations for real-time access requests and approvals

## Overview

Keeper supports just-in-time access to secrets and credentials through direct integrations with common communications tools and ITSM platforms.

These integrations let users request access in the tools they already use. Admins can then review, approve, and fulfill access with full auditability.

## Available use cases

Use these integrations for request-based access to records, folders, one-time shares, and related approval workflows:

* [ServiceNow Workflow](/en/keeperpam/secrets-manager/integrations/jira-workflow.md) — Request and approve access through ServiceNow service workflows and catalog-driven processes.
* [Jira Workflow](/en/keeperpam/secrets-manager/integrations/servicenow-workflow.md) — Manage request-based access and approvals directly from Jira issues.
* [Slack App](/en/keeperpam/secrets-manager/integrations/slack-app.md) — Handle just-in-time access requests and approvals from Slack.
* [Teams App](/en/keeperpam/secrets-manager/integrations/teams-app.md) — Handle just-in-time access requests and approvals from Microsoft Teams.
* [Google Chat](/en/keeperpam/secrets-manager/integrations/google-chat-app.md) — Handle just-in-time access requests and approvals from Google Chat.
* [Freshservice](/en/keeperpam/secrets-manager/integrations/freshservice-workflow.md) — fulfill Keeper vault access and approval requests directly from the Freshservice ticket sidebar

[See all integrations](/en/keeperpam/secrets-manager/integrations.md)

## Common workflow

Most integrations follow the same pattern:

1. A user requests access to a secret, credential, or shared resource.
2. An approver reviews the request in the connected platform.
3. Keeper grants time-bound or task-specific access through the integration.


---

# 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/jit-integrations.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.