I love DNN but one HUGE issue that I bump my head on every day (and I've spoken with other DNN'ers that have also wrestled with this) is that you can set security to ALLOW content (e.g., a module) to display, but you can't set security to DISALLOW content to display.

For example, I'd like to display some "Subscribe Now" content to all users that DO NOT belong to a certain security role...and would like to hide the same content to those users that DO belong to that same role...

It would be nice to see a future DNN security offer an option to DISALLOW content display by security role. That's my biggest wish for DNN...

This has always made sense to me, too ... would be similar to Windows OS permissions or MS SQL permissions.

Could, however, get thorny real fast for many folks. Say person A is in two roles, one permitted, one denied ... if following the Windows analogy, deny would trump permit ... lots of folks would be scratching their heads, our non-techy clients with admin role. Permissions can be tricky.

I remember that this was discussed long ago in the old asp.net forums. Don't remember what was said about it but do remember it was discussed.

Well, I would think you need to be able to apply it to roles as well as individuals.

I just mention the complexity so that it's not lost in the discussion, but not because I think that settles it. All said and done, I'm for a deny view as well as a deny edit setting applicable to roles.

Just something that folks have to learn to understand. It's only confusing until you understand ... :)