> 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/user-guides/developer-center/property-file-record-type.md).

# Property File Record Type

Control access to developer properties for local tools and AI agents

Property File is a dedicated Keeper record type for the values that power an application or development workflow: environment variables, configuration values, and related secrets. A record can hold key/value pairs, file attachments, and one-time passcodes, alongside its title and notes. As a Keeper record, it can be organized and shared using the Vault's record and folder access controls.

{% hint style="info" %}
Property File record type 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 %}

### Property File record type

<figure><img src="https://914511346-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LSGVtOTYUIkVBoYtFvK%2Fuploads%2FVnJ4ofv0Xqrst9FIBZcH%2Fimage.png?alt=media&amp;token=0ad6d1f8-4ccc-4d81-acb7-26ec57d7485a" alt=""><figcaption></figcaption></figure>

#### Configuration, ready for development

Developers need configuration close at hand, but copying values between vaults, local files, and team members can create extra work and outdated copies. Property Files give teams one place in Keeper to manage project configuration, then make it available to the local tools that need it. That means fewer manual handoffs and a smoother path from securely managed values to everyday development work.

#### Import existing configuration

Property Files help bring project configuration into Keeper. Import a supported local configuration file to turn its key/value entries into fields in a **Keeper Property File** record. Supported formats include `.env`, `.json`, `.yaml`, `.toml`, and `.properties` files. Review the imported values before saving. Duplicates, unsupported, or unparseable entries may need to be corrected within the import wizard.

#### Virtual destination mounting

On supported desktop platforms, a Property File can define a destination path on the developer's computer. Keeper makes the record's configuration available at that location as a virtual file in a format inferred from the filename - for example, `.env`. A path can use user-specific variables so a shared record can map to an appropriate local location for each user.

{% columns %}
{% column width="50%" %}

<div data-with-frame="true"><figure><img src="https://914511346-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LSGVtOTYUIkVBoYtFvK%2Fuploads%2FO28Io2WueoS7CJzibuzF%2Fimage.png?alt=media&amp;token=fbbb5f82-65ac-4890-81f3-cfe04b371f1d" alt=""><figcaption></figcaption></figure></div>
{% endcolumn %}

{% column width="50%" %}

<div data-with-frame="true"><figure><img src="https://914511346-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LSGVtOTYUIkVBoYtFvK%2Fuploads%2FKHDWlGzcLcFrMSrzu1gG%2Fimage.png?alt=media&amp;token=6592af2b-231c-442d-8038-8fa135e21475" alt=""><figcaption></figcaption></figure></div>
{% endcolumn %}
{% endcolumns %}

{% hint style="warning" %}
When a local tool or AI agent requests access to a mounted file, Keeper asks the user to approve which files the tool may read.
{% endhint %}

Additional details regarding Developer Center, Property Files and AI Access can be found in our KeeperPAM user guide:

{% content-ref url="/spaces/-MJXOXEifAmpyvNVL1to/pages/cHlIEfnyXCbjxUskqLBt" %}
[Developer and MCP](https://docs.keeper.io/keeperpam/developer-and-mcp/developer-center.md)
{% endcontent-ref %}


---

# 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/user-guides/developer-center/property-file-record-type.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.
