Hello,

I am creating a module, and I am not very experienced at it, but I seem to understand it except for one aspect.

When I am creating the module, do I need to control the module visibility by checking if the user is in a role, or is that handled by the PortalModuleBase?

If I am supposed to manage that, what is the best practice for that, and where can I find a sample? Some tutorials hard code checking for admin, but that seems counter to the way DNN allows the admin or host to specify visibility based on role. Other tutorials don't handle it at all. That leaves me asking, "What is the right way?"

Thank you for your help.

Ben

Thank you very much for your reply.

For clarification, if I do nothing in my module it will still have the default permission verification that comes with the "built in" modules, correct?

Ben

Thank you for that information. That is a very good resource. That site has helped me a lot. However, maybe I am a little dense in this situation. This statement from the site says, "The Portal administrator will ultimately decide which users actually have access to the control." This implies that I don't need to control view permissions in the module ( I am referring to the view control, not the link to the edit control). Is it safe for me to assume that what I am inferring from that statement is correct?