> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/advanced-topics/version-control/when-to-use-version-control.md). # When to Use Version Control This article outlines the key benefits of version control and highlights when/how it might be useful. ### Version Control The Version Control feature allows multiple Designer users within the same installation, company, and workspace to collaborate on a project. The system keeps track of who checked out the project and may be editing it. It also allows you to check in any changes and add revision notes that detail for others the changes you made. LogicNets recommends you use version control under the following circumstances: * You have multiple Designer users who collaborate on content. * The Designer users all need to build or maintain content in the same project. * Collaborating Designer users all have access to the same shared content, so there are no security concerns or content restrictions between users. --- # 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://community-test.logicnets.com/release-9/platform-documentation/advanced-topics/version-control/when-to-use-version-control.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.