Under 5.5.0 when logged in as an Admin on the Admin|Extensions page you can see every module installed on the DNN instance all with the edit icon next to them.  This includes modules that are classified as premium and those not allocated to the site being viewed.

From a usability standpoint this makes for frustrated users as they expect the modules that they see be available for use in the site but they can't find them in the control panel drop down. If they try to edit a module not available to the site on the extensions page to allow others to use the module (like they can with modules that are available) they are presented with a message in the settings section saying this is where you can set deploy permissions, but nowhere to enter these permissions.

The admin user also sees a 'Create Package' button which when clicked returns an Accessed denied message. Same happens if an Admin user clicks the 'Yes' in the 'In use' column

IMO the following changes should be made to the Extensions module.

• only show the edit icon next to those extensions the viewing user can edit otherwise show a 'more details' icon/link
• any extensions that are not available to the site should not be shown to Admin users
• if the user doesn't have the right to 'Create a package' don't show the button or disable it. 
• allow the admin user to view where the module is in use on their own site.

To a lesser degree I don't see the need to show an admin user the details of the framework, Library and Providers in use as they are Host level settings.

Before I submit something to Gemini I would like to see what others think.

Antony