John, i was thinking the same thing. I will add that as enhancement suggestion in Gemini.

Right now, an option would be to add a request filter for the logon page and limit that to certain ip addresses. That will prevent public logon though...

DNN Blog | Twitter: @erikvb | LinkedIn:

>It would be handy if you could do a release which removed any of the more powerful accounts before moving the application to the Internet.

Out of the box that is not possible, you would need custom sql scripts / sync tools and file syncing to create a local content version and a locked down live version. In my humble opinion that is very impractical though. What you can do now is to create your own authentication provider that does the ip checking for you. That would be an almost exact copy of the dnn auth provider, but with extra code to check for ip ranges when a user belongs to certain roles

DNN Blog | Twitter: @erikvb | LinkedIn:

What about using oth DNN and AD security providers?  Only assign permission to those authenticating with AD.  Assuming external users don't authenticate with AD as well.

Jeff