A number of people have asked for this ... I think because they are trying to use Expression Engines as a Content Management System. Many of the requests are of the nature ... “how do I externalize login and make sure my end users never ever see the control panel.”
We’ve implemented a series of hacks that will allow you to do this This is not a “module”... but impacts multiple modules. If you are interested, we’ve posted the hacks in the colophon section of our website ...
http://www.firewhite.com/site/colophon/index
Note that we don’t use Expression Engines to support weblogging at all and have therefore not testing the system with trackbacks and comments. That said, we have been using these hacks and modifications for about a month now and everything works as advertised with the possible exception of the modlog module which has yet to be stress tested.
Using this system we have about 100 members organized into 20 groups. Each member can login to the system and view content designed for them and only for them. Members in one group are not able to view content designed for another group and - in fact - are not even aware that the other group exists.
Access control is controlled by the regular mechanisms you’d expect within EE:
{if logged_in} at the top of the template and {/if} at the bottom of the template.
We’ve set the templates up to display a login box in the event the member is not logged in.
Finally, access to templates is controlled by setting template preferences. In this way, specific groups can access the content that is designated for them while other groups are barred from accessing that content.
