I’ve been searching through the forums, existing apps, googling in general, etc. but have failed to find any satisfactory answers or solutions to this question.
What is the best way for the owner of a folder or file to make that folder or file read-only, including for themselves, ensuring that it is protected from modification regardless of access method (web UI, WebDAV, remote client, REST API, some app, etc.) and in the context of sharing permissions, etc. akin to “chmod a-w” such that when applied to a file in a folder that has been shared with some group where the group has edit rights to the folder, the file becomes read-only for all users, both the owner as well all users the file is shared with.
I’ve looked at the core sharing functionality, Workin2Gether, Group Folders, Tags + File Access Controls, WebDAV LOCK/UNLOCK, but feel I must be missing something obvious and straightforward, which has simply eluded my searching.
Is there some existing method to achieve this that I’m missing, or am I going to have to implement a solution myself, or hack the core or an existing app in some manner to do it?
have you tried sharing a file or directory with read-only rights?
meaning: you either need to have a special user how once uploads the unchangable files to his account and then share it to you and other “read-only” or you share it from your user to such a directory and share it from there to others, read-only. since you seem to exclude yourself from changing things conicidentially, i would suggest version 1 to you.
it’s a bit umcomfy but i think it would work.
It’s not just about sharing, but also making the folder or file immutable/protected from the owner’s own actions (apart from making it writable again). Also, having separate shared folders, one with read-write and one with read-only would require moving folders and files to the read-only space, and that brings a great many usability and practical issues by changing what is often a deliberate and specially structured organization of folders and files.
The need is simply to be able to make a particular folder (and its subtree) or specific file immutable, without changing anything else.
afaik there’s no app that would help you changing the rights on said folder (without knowing if an r/w folder would allow you to automatically make any file in it read-only - without changing every single file to read-only)…
so again. if you want to have a group being able to put files in directory make a group-account (set up an account and share the password to members of virtual group (aka give it to guy 1, guy 2, guy 3 etc))…
this groupaccount (GA) can share files to every member of your NC-instance marking it read-only. which means: even the guy who made a certain file won’t be able to access it (other than read-only) from its own account unless he’s logging in to GA to change it.
that doesn’t sound like being overly complicated. if you don’t wanna give out the password of GA you need to elect one person being in charge of GA. everyone should send (sharfe?) their files to the elected person how is obliged to put it into GA-account. so it would always be clear who is responsible.