I am currently working with a client to develop a rather large system for them, and we chose to use DNN as our base framework. I am having concerns about the settings for the new functionality however, because I'm not sure how to centralize them. When I develop a module and put it on a page, can I have settings for that module be centralized in one place? The application we are developing is a scheduling app that has several views, with settings and abilities being enabled per role. To simplify navigation, we have chosen to create a page for each role and put a schedule view module on each page. The module should recognize the users role sets and set display options accordingly. However, I don't want to have to set these settings on each and every module on each and every page.

Is there an easy way to centralize settings like this? Where one module - say on the administrator screen - has all settings for the rest of the modules to inherit?

you can create a specific settings module, available to admin only, that stores your settings or  you can use your own settings table, using portalID as part of the key, if you want to have settings once per portal.  Besides every other of your modules can have its own settings stored in ModuleSettings table and TabModuleSettings table.