A few quick questions...

Folder Locations are available to the administrator outside of their portal. A few good gueses could upload files to another site or anywhewre on the server it seems. This can create a nasty problem. Is there any way to restrict access to the module settings to the host?

Anyway to restirct folder locations to the portal?

Second question first. Only some of the templates use the summary (ie: NiftyToggle).

First question: Your attributes won't show up without changing the template that you're using. I've copied the following from an email that Steve originally sent the project team as I can't say it any better myself:

You can assign as many 'Attributes' to a repository as you like. Then for each Attribute you can define any number of valid 'Values'. On the Repository Settings page you'll see 2 new listboxes, Attributes and Values. You enter, edit and delete items from these 2 listboxes the same way as setting up Categories. The only think to keep in mind is that you have to highlight an Attribute first to add Values. When the Upload or Edit page is rendered, it will auto-generate checkboxes for each of the valid values for each attribute so that uploaders and editors can assign values to the files. There is a new skinning tag, [ATTRIBUTE:name] where name is the name of the Attribute.

Example: You setup an Attribute named 'Color' with 'Red', 'White' and 'Blue' as valid Values. In the 'header.html' of the skin you are using, add a tag that looks like [ATTRIBUTE:Color]. At runtime, the tag will be replaced with a drop down listbox that has 'ALL' and all the valid values for that Attribute as options. Selecting a value in the drop down list will 'filter' the files that are being displayed. You can have multiple Attributes for a Repository and having multiple [ATTRIBUTE:name] tags in the header.html file will allow users to do some pretty sofisticated filtering as the Attribute dropdown lists are cumulative.

Outside of DNN is not the issue, it's into other portals which is easy. If I see D:\webspace\install\portals\30\repository it does not take much to figure if I want to save on disk space why not try putting my stuff in portals\29.

I would think that configuring the "Settings" control to Type - Host would keep the admin out but that does not work for some reason.

This is a fairly significant problem when using the module on a multi-installation setup.