The Super User Account

DNN differs from other CMS systems because it enables you to host multiple websites (portals) out of the same set of files and a single database. This flexibility is what causes the need for super user and administrator accounts. The super user, or Host, account has the ability to create new portals within a DNN instance. This account has access to everything within a DNN instance; it can manage all the content and users of a website, as well as add new extensions. This chapter will cover a majority of the information you need to know about the super user account. The important thing to remember is that a super user can do anything on any portal.

The Administrator Account

So, if the super user account has the ability to manage everything with an instance of DNN, what does an administrator have the rights to do? An administrator account is tied to one portal within a collection of portals in a DNN instance. An administrator can manage all the content and users within a single portal,

as well as utilize the modules installed within that portal, but he or she cannot install modules or skins. The reasoning for this is twofold. First, because a Host/super user account is set up to be the manager of everything, he or she is likely to be the person who set up and configured the database, the website in IIS, and other hosting-specific information. The Host account is generally someone who will be doing the upfront homework of investigating modules and skins before they are installed to ensure that they are from a trusted source. The second reason is that when a module or skin is installed, it can impact all portals in a DNN installation. Because modules and skins can, and most likely do, contain computer code that is executed on the server, it is possible for code to be malicious. Even if a module or skin is not malicious, changing the functionality that a skin or module provides can easily impact more than just an individual website. For this fact alone, the super user account is the account that has the ability to install modules and skins. This is a little different from previous DNN versions. In prior versions of DNN, it was possible to allow administrators to install skins for their portal. Because of the potential for code to live in the skins, however, DotNetNuke 5 restricts this to only super user accounts. It is possible for a DNN instance to have multiple super users and multiple administrator accounts for a portal. In general, it is recommended that you use the administrator accounts when logging in to a website and managing the content. You should use super user accounts only when you need to access the extended information provided to them. We’ll cover some of that super user information after we talk about logging in to a DNN website.

本文转自xwdreamer博客园博客，原文链接：http://www.cnblogs.com/xwdreamer/archive/2009/12/26/2297190.html，如需转载请自行联系原作者