Has anyone practical knowledge with collective_folderprotection?

Is this addon an alternative choice to protect folders and the content inside, if the editor is unwilling to manage Groups and Workflows?

We have used this add'on in the spring to create a 'protected' area on a Plone website for marketing purposes. It works ok and allows to set only a password on an item or a complete subsection (folder and everything below) with one password. (not different passwords).

The password is hashed/stored in a cookie, so when you enable this you have to mak sure any caching in front of the site respects this cookie just like an __ac one and doesn't cache the protected area. :wink:

Plone Foundation Code of Conduct