Enable Versioning of Pages etc

Update: Terminology.. I was looking too hard for “versioning”, but here it’s “history”.

never mind, n00b-flagging myself :wink:

WHAT DO YOU RECOMMEND?

Enable versioning for certain object-types, i.e. pages, to enable better collaboration / fixing unintentional deletion of document-parts.

HOW COULD IT BE DONE?

Needs to be configurable, because it would be individual to the spaces needs. How many versions of a page will be kept, maybe an internal copy with backlinks would already work?

REAL WORLD USE CASES

Like in other collaborative workspaces, versioning is mostly essential, when others access the content (or ai via MCP). Errors may produce unusable pages, hard to recover as of now. A versioning (i.e. keep the last 3 updates) would help a lot to easily roll back. or: a snapshot would work as well, but i

RECOMMENDED ALTERNATIVES

manual copy of information-critical pages, which is odd, once you’re in a flow this is the 1st thing that gets forgotten.

ADDITIONAL CONTEXT

RTFM. my bad.

But… There is already versioning :open_mouth:

For sure they can improve it but the post seems to say that there is no versioning at all ^^

Okay, maybe tell ur AI to look at this page first:

Anytype stores the history of changes for each object you’ve created.

This feature request is already implemented.

Maybe enable web search before entering your query?

thx… sorry, i was looking too hard for versions.. my bad.

The history in these docs can be difficult to locate because it doesn’t have a dedicated category, and the docs themselves aren’t directly linked within the Anytype app, which often leads to confusion for new users.

For beginners, the interface and concepts are not very intuitive, but once you grasp the basics, things start to make sense.

The documentation is a good starting point for learning Anytype, and I also highly recommend checking
out the Focused Curiosity YouTube channel for helpful tutorials.