For me it's a fundamental question regarding to the settings page or an additional page via the module menu. I researched a lot in the DNN papers, books or forums but i found no acceptble answer. Maybe can you help with your experience how to find an optimal way to design modules (for administrative data). Below you'll find a short expample wherein i describe my problem.
It's clear if a module has a feature which is controlled by a property (e.g. checkbox -> Yes/No the feature is running or not, ...) and is enumerated in the settings page. But why can't i (or better shouldn't) transfer a part of the business-logic and it's presentation-layer to the settings page. Here the short example: we've database in which unique items are stored (could be stocks). The item has a title and a daily price. The administrator or operator changes, deletes or inserts the items. The normal users (anonymous) should be able to create a simple report sheet (grid view) - they only can set what items the have and the number of items he owns (-> amount). My idea is, i want to seperate the logic what user can do and what the operators can do in one module. For the first version i created two modules - one for the users who define what the report looks like and another additional for the admins who manage the items. It works but i think it's not very comfortable for the admins. It would be a lots clearer to combine the logic in one module and the admin inserts or changes the data in the settings page or an additional page via the module menu?

What do you think? Is this a problem for the DNN engine or would i do a grave design error in the DNN framework. Any helpful suggestions are welcome!

guy