@bionade24 & @wthess Thank you for your answers !
The problem is that it probably concerns several hundred files in our current file architecture. This means that we should rearrange the files of all users before using Seafile.
Moreover, such a feature could be useful in some cases,
I’ll give you an example:
If i want three users working on a project where files are stored in myfolder.
I want this rights to avoid users to write/delete files by mistake.
User01 to read/write on file1, and only read on file2 & file3.
User02 to read/write on file2, and only read on file1 & file3.
User03 to read/write on file3, and only read on file1 & file2.
I’ll have to create 3 subfolders in order to put the 3 files and put the good permissions, that’s not very practicable, moreover, in this case I only use 3 users/files, in a bigger project, it’ll be difficult to manage rights correctly.
That’s why I was asking this feature, for a company environment I think that it’ll be very useful !