> 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/introduction-to-version-control.md).

# Introduction to Version Control

The LogicNets Version Control functionality allows multiple Designer users to access and maintain content in the same project. It allows identified Designer users to check out a project from a repository, make changes to the project, and check those changes in while maintaining version control.

This section describes the principles and operation of the LogicNets version control functionality--how different users can check out a project to make changes that can be shared with other Designer users with access to the same Designer. It shows the steps needed to place a project under version control and how different users can check the project out to make changes that can be shared with other Designer users.

Within this category are other articles with detailed notes:

[Version Control](/release-9/platform-documentation/advanced-topics/version-control.md)

* How to place a project into version control, check it out for editing, and check in changes.
* How to view a project's revision history, including the check-out details when appropriate.
* How to make an uncontrolled copy of a project and/or remove a project from version control.


---

# 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/introduction-to-version-control.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.