We have been working on a new safety feature for Tik Manager, focused on improving data security and version management. Many of you may have noticed that when versions and published files are deleted, they don’t disappear immediately. Instead, they move to a hidden .purgatory folder under the project root—like a recycle bin. However, if their parent tasks or sub-projects are deleted, they’re gone for good.

We are changing this behaviour. Now, when any database item is deleted (sub-project, task, work, version, or publish), instead of being removed from the database, it will simply be tagged as deleted and hidden from users. All related user-generated content (scenes, extracted elements) will still move to purgatory, but crucially, they can now be resurrected.

We are also implementing a Purgatory Mode, allowing users to review and recover deleted items when needed.

Why does this matter? Let’s consider a common scenario in remote work:
🔹 User A (Admin) creates a sub-project and task.
🔹 User B (Artist) starts working on it.
🔹 User A, unaware that work has started, deletes the sub-project and task to create a new one with a different name.
🔹 Due to slow sync, User B’s work database files aren’t updated yet.
🔹 User B logs in later—only to find that their task and versions are missing.

Even if scene files remain in project folders, this situation creates confusion and potential data loss. The new method ensures work isn’t lost and avoids these messy situations.

Excited to roll this out soon! Let me know your thoughts. 🚀