> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/keeper-security/troubleshooting/keeperpam.md).

# KeeperPAM

Troubleshooting and support for KeeperPAM

### Keeper Secrets Manager (KSM)

Please see the Keeper Secrets Manager [troubleshooting page](/keeperpam/secrets-manager/troubleshooting.md).

***

### Keeper Connection Manager (KCM)

Please see the Keeper Secrets Manager [troubleshooting page](/keeper-connection-manager/troubleshooting.md).

***

### Contact Us

If you need help, please [open a support ticket](https://keepersecurity.servicenowservices.com/csm?id=csm_index) in our ServiceNow system.

If you need to speak to our support team, simply make the request and we will schedule it during enterprise hours. Please be patient as we coordinate the call.

***

### Emergency Support

If you're a enterprise customer having an emergency and need urgent support, use our [ServiceNow support portal](https://keepersecurity.servicenowservices.com/csm?id=csm_index). On the support form, select the option "**This is an emergency, outage, or other time-sensitive issue which requires immediate assistance**".

***

### Feature Requests

We love hearing from Enterprise customers. Send your feature requests to: **<feedback@keepersecurity.com>**.

***

### Join our Slack Workspace

[Join our Slack Workspace](/release-notes/keeper-security/troubleshooting/join-the-slack-workspace.md) to post questions, feedback or receive new beta versions.


---

# 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.keeper.io/release-notes/keeper-security/troubleshooting/keeperpam.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.
