This is why I mentioned OWS, as it sounds like what you're wanting to do would be quite easy with it and it can take advantage of DNN Roles etc for you to include your own security within it.

Having used OWS for a couple of years now I still think it is well suited to this problem, and not sure what would make it difficult.

One example of how I used it was in the setup of 4 different languages across 4 separate portals but for the same company.  Many pages were for the same thing but content was to be different and also the people able to edit it.

With OWS I had control over who could edit which parts and it could be done for multiple languages in any of the portals although they were separate. If they had edit capabilities it would show them an edit button for the content on any of the portals for that content (I used a table to match the different tabs across portals) and they could see any languages they could edit for that set of tabs. Due to the languages I didn't have it actually sharing content but it did all appeared integrated to the user.

If others have similar requirements and need a solution I strongly recommend considering OWS as it is certainly up to the task, only limited by the user.

David, to be frank, I'm not convinced by the idea of using OWS. The information that is available about it is vague and makes it seem more of a solution for presentation issues rather than content management. It's also described as a framework, which is what DNN is and I can't see the benefit of shoe-horning one framework into another, but I can see plenty of risk. OWS is described as having a "wrapper" for DNN which gives me the impression that it is intended for use in entirely different context, and that DNN has been added as an afterthought in an attempt to broaden its market.

---

Paul Taylor

DotNetNuke, ASP.NET and SQL Server Development