You should really avoid making these sorts of changes to dnn - since they break when you try to upgrade the site.If you have pages that you only want the HOST to see - then the best option would be to move the modules over too pages on the HOST menu. This allow them to continue to operate after a DNN upgrade.I would make the same suggestion regarding alterations to default.aspx - again this is asking for problems. In this case I would suggest adding a custom SKIN OBJECT to your site's skin - and using this skin object to handle the display of any messages your want to display. This way your site remains up to date.With regard to your actual question ... where are you actually trying to add the "if (UserInfo.IsSuperUser)" code. It is making the assumption that UserInfo is populated with current user ... this most likely wont be the case.You should instead be looking at "PortalSettings.Current.UserInfo" this holds the current logged in user context.Westa

I came up with a solution (my issue was unfamiliarity with C#). Using a DIV with display:none around the content I want to hide, but using code to check IsSuperuser.

<% if (UserInfo.IsSuperUser) { %>