[BUG?] locking doesn’t stop changes or lock files

I locked some files expecting them to be protected, however, I was able to change tags and move items.

So I looked at the files, on an external folder on a SMB NAS, in finder and they didn’t have lock set on them.

I really think locked should mean locked protecting the item in the database and the file in the database or external folder. (Scripts can lock and unlock so scripts can still work when changes are needed via automation)

or is this a bug?

Locking prevents only editing the contents of the file, metadata can still be changed.

Could there be a complete lock option in the future?

We’ll consider this for future releases.


I would love to second this. My workflow involves a lot of custom metadata and it is really easy to accidentally change something (or the wrong thing) without noticing when looking through one’s files. In this kind of case, this is a significant vulnerability. Thank you for considering this option.