> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/add-ons/teams/concepts/vault.md). # Vault The Vault concepts section covers the essentials behind the legacy Vault server repositories and their settlement process. ## Key Vault Concepts


Worklists & Commits	Understand how to manage and publish changes
Site	Learn about sites, which define how Teams files are mapped, tracked, and filtered
Teams UI	Overview of Teams UI: description of menu and widgets
Diffing and Merging	Learn about diff mode, merging steps and more
hvignore file	Specify what files should be ignored when adding to Teams server
Users' permissions	Manage user's permission
Merge Process	Check all details of the steps involved in the merge process

### --- # 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.hex-rays.com/add-ons/teams/concepts/vault.md?ask=&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.