> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/object-storage/details/versioning-and-immutability.md).

# Versioning and immutability

Versioning, immutability, and automatic deletion, as a reference.

These are the data protection and lifecycle functions.

The reason is in [Buckets and objects.](https://docs.plenit.com/docs-en/productos/object-storage/concepts/buckets-and-objects.md)

### Versioning

| Aspect         | Detail                                                    |
| -------------- | --------------------------------------------------------- |
| Activation     | It is enabled on the repository subscription              |
| What it does   | Keeps previous versions when an object is overwritten     |
| What is it for | Return to a good version after an overwrite or corruption |

### Immutability

> #### 🚧 Object Lock in progress
>
> Immutability locks objects against deletion or modification for a period of time, intended for retention and ransomware protection.
>
> We confirm scope and availability with the current platform before publishing the configuration details.

### Automatic deletion

| Aspect         | Detail                                                                |
| -------------- | --------------------------------------------------------------------- |
| What it does   | Deletes objects after a period of time, according to rules you define |
| What is it for | So the repository doesn't grow uncontrollably with expired data       |


---

# 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.plenit.com/docs-en/productos/object-storage/details/versioning-and-immutability.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.
