> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/cyberark-system-safe-filtering.md).

# CyberArk system safe filtering

Hide CyberArk system safes in Remote Desktop Manager by enabling the Hide system safes option to filter internal vault safes from lists.

CyberArk safes do not have flags to indicate if they are for system or for general use. That being said, we can find in various CyberArk information sources that certain safes are indeed for the internal working of the vault exclusively. The following safes will be considered “system” safes, and by checking the appropriate option (typically labeled ***Hide system safes***), they will be hidden from lists.

{% hint style="success" %}
Go to ***File*** – ***Settings*** – ***Entry types*** – ***Credentials*** – ***CyberArk*** to add or delete ***Excluded safes***.
{% endhint %}

* System
* VaultInternal
* Notification Engine
* PVWAConfig
* PVWAPrivateUserPrefs
* PVWAPublicData
* PVWAReports
* PVWATaskDefinitions
* PVWATicketingSystem
* PVWAUserPrefs
* PasswordManager
* PasswordManager\_ADInternal
* PasswordManager\_info
* PasswordManager\_workspace
* PasswordManagerShared
* PasswordManager\_Pending


---

# 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.devolutions.net/rdm/knowledge-base/knowledge-base-articles/cyberark-system-safe-filtering.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.