I prefer the latter idiea; "having a property on the folder for read-only access in combination with the read-only privilege".

Thank you for posting this idea. Opening the whole repository as read-only for users might give too much access, customers may want to restrict users to folders / departments.

Maybe a better option could be to allow changing owner / Grant read access to in the future or having a property on the folder for read-only access in combination with the read-only privilege?

Hi again,

Actually, you cannot change the Owner and the Type of the folder after it is created. However, you can change the groups which have read access to it (at least in TDX 13 and TDX 14).

Anyway, your ideas which I've seen here are great and I definitely support them!

Regards,
Alex V.

Hi Alex,

Thank you for letting me know the alternative method. This method works when creating a new folder. However, we've alread created hundred of folders that have hierarchy. As you know, it's not possible to change access priviledge of a folder after creating it.

Thanks,

Naoki

Hi Naoki,
If you add those users in a new User group which has only read access to all of your documentation folders, then you should be able to achieve your goal. Please test this on your side as our setup might be different from yours.
Regards