Protect Scheme "order of precedence"

[binoclard]

I wonder if it could be a decent feature, that the protect scheme has some king of "order of precedence": Site > Collection > Entry So if a global protect scheme is set, it could still be overridden at a more specific level.

My question comes from my current project, where it makes sense to set up a site-wide protection with password, but I still would like to exclude some limited pages. Currently, if I understand things correctly, the only option is to define a protect scheme for each and all Collections/Entries, except the ones I would like to be less restricted.

So I think it could be nice to be able to specify "protect: null" at the entry level to exclude it, or to be able to set 'logged_in" as the default, but 'password' for selected items, or vice-versa.

Hope it makes sense, and that others might find it useful.