> 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/keeperpam/developer-and-mcp/overview.md).

# Property File Record Type

Secure local secret access for developers and AI agents

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FSh9dpvOeIGBXcv0AgHcR%2FKeeper%20-%20AI%20and%20Developer%20Tools.jpg?alt=media&amp;token=3405d91b-16f3-46c7-acf6-7d7220843ab7" alt=""><figcaption></figcaption></figure>

### Property File Record Type

**Property File** is a new vault record type for developer and agent workflows. It controls how vault data is exposed to local tools and AI agents.

{% hint style="info" %}
Developer Center is currently in [Preview](https://docs.keeper.io/release-notes/desktop/web-vault-+-desktop-app/preview-release.md) and goes live with Vault Version 18.7
{% endhint %}

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FG9rLaFVQa7ooipAXE0eM%2FScreenshot%202026-11-05%20at%201.50.34%E2%80%AFPM.png?alt=media&amp;token=7e0ad19e-23de-4def-a5de-d958286e003c" alt=""><figcaption></figcaption></figure>

A Property File stores any number of name/value pairs. You can mount the record as a virtual file on the local machine by clicking **Add Destination**. The file exists at the chosen path, but its contents stay protected until a process requests access.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FEd84JjI4aevb2BIFesrH%2FScreenshot%202026-11-05%20at%201.52.29%E2%80%AFPM.png?alt=media&amp;token=0e8104fe-1e32-4d81-9dd6-eb478c48e71f" alt=""><figcaption></figcaption></figure>

Property Files behave like other vault records. You can share them with users and teams. You can also use them with Keeper Secrets Manager workflows, CI/CD pipelines, and infrastructure automation. They also work for a single developer on a local workstation.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2Fiz7Q8xvG2iBd9qHf6BBh%2FScreenshot%202026-11-05%20at%201.55.19%E2%80%AFPM.png?alt=media&amp;token=658d4037-32a2-4c2f-8524-7d123c8e524e" alt=""><figcaption></figcaption></figure>

Developers can point local software or an AI agent to the mounted destination file. When a process requests access, Keeper prompts the user to approve or deny the request. Approval can be granted once or reused for future requests, similar to the Keeper SSH Agent workflow.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FjBy6HbP8kPaUnIrB3uSD%2FScreenshot%202026-11-05%20at%201.55.52%E2%80%AFPM.png?alt=media&amp;token=f152ec34-9d18-4f86-83d2-9fe77708ca24" alt=""><figcaption></figcaption></figure>

### Developer Benefits

Property Files improve local development without weakening secret controls.

* Secrets stay encrypted in the Keeper Vault instead of being copied into local files
* Approved local tools always read the latest record values
* Developers can switch between environments by changing which Property File they reference
* Teams can share the same workflow across local development, CI/CD, and Keeper Secrets Manager integrations


---

# 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/keeperpam/developer-and-mcp/overview.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.
