It is possible to add an extra control as Mitchel says. The "gotcha" that I encountered was that as part of a WSP I added a standard web control and changed the base class to PortalModuleBase but it failed to render. I couldn't figure out if the call to NavigateURL() was at fault as it seemed to be retrieving a sensible URL. However, I'd added the new control's definition to the manifest which is only used when *installing* the module. No doubt, re-installing the module with the new control would have solved the issue but instead I just edited the module definition from the DNN host's Module Definitions option. I selected my module and added the new control using the "Add Module Control" button. I was then able to specify the type of control (View), the key name, title, source code, etc. My new control was then effectively "wired up" to my module and rendered fine.