Hi Matt, I'm not totally clear on what you are trying to do. Assuming that you want to have the "user" view of the feature on one page, and the "admin" view on another, you can use module settings to specify a checkbox like "Use Admin View?". Based on the state of the checkbox, you can show/hide the appropriate controls. Your feature will need to inherit from SiteModuleControl, but if the module is showing the same data everywhere, you don't have to distinguish the feature instances by ModuleId in your code. There is nothing that forces you to use supporting pages.

Hope that helps. If I totally missed the point, feel free to expand a little on what your goal is.

Jamie

Hi Matt

I know where you are going with this and have a feature using similar requirements.  In fact I take it one level deeper to the mojoPortal site level using code like this...

private void LoadSettings()
{
     siteSettings = CacheHelper.GetCurrentSiteSettings();
     currencyCulture = ResourceHelper.GetCurrencyCulture(siteSettings.GetCurrency().Code);

     SiteUser siteUser = SiteUtils.GetCurrentSiteUser();
     if (siteUser != null) _gUser = siteUser.UserGuid;
     Module module = new Module(ModuleId);
     _gModule = module.ModuleGuid;
     _iModuleID = module.ModuleId;
     _gSite = siteSettings.SiteGuid;
     _sUser = Context.User.Identity.Name;

}

My stored procedures in MS SQL have a Where clause something like this...

WHERE  ([BPRGuid] = @BPRGuid) AND //  BPRGuid being table specific
             ([SiteGuid] = @SiteGuid) AND
             ([ModuleGuid] = @ModuleGuid)

Hope this helps

Rick Hubka