Hi ustuntman, I believe albert is correct, but you might consider just using the FTP server instead of the Web File Server feature as a work around. In combination with a ddns account, you and your users would have both local and remote access but not access to the other applications on the 320.
The thing I am concerned about is what a user can do with access to those settings more than just seeing them. The real question I have is can the visible applications be modified by a user? It doesn't seem right to me from a security point of view to have these settings accessible by default and no administrator method of blocking this.
Maybe I am just ignorant, but I don't understand why the Web File Server feature should not be restricted to the user's network shares, just like the FTP server. For that matter, I don't understand why a user should be able by default to login to the 320 at all. I can understand situations in which this might be desirable, but only with administrator control. Perhaps some of you more knowledgable / experienced folks could enlighten me. Please and thank you.