> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/fabricate/projects/project-versions/project-versions-about.md).

# About project versions

Project versioning allows you to use a preserved snapshot of a project configuration while you continue to work on the project.

## Types of project versions <a href="#version-types" id="version-types"></a>

When project versioning is enabled, every project can have:

* One or more draft versions.
* One published version.
* One or more prior versions. A prior version was previously published.

Draft versions are always fully editable.

For published and prior versions:

* The mock APIs and workflows are all read-only.
* You configure whether to write-protect the data in the local databases.

## Write protection - local databases versus data connections <a href="#version-write-protection" id="version-write-protection"></a>

### Local databases

When a published or prior version write-protects the data, the data in local databases never changes.

Any changes to the data configuration or to the generated data in other versions have no effect on the data in the published or prior versions.

### Database connections

However, because a Live Connect data connection connects to a specific external database, it only has one set of data, which is the same across all of the versions - draft, published, and prior.

For example, when you add data to a database connection in any project version, the new data is present in all of the project versions.


---

# 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.tonic.ai/fabricate/projects/project-versions/project-versions-about.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.