LBI Structure / Framework For Maximum End User Flexibility

I know lengthy posts often get glossed over so I tried to provide the quick, to the point post and then if needed, the background for the much appreciated person that responds.

THE PROBLEM:
Looking for guidance on setting up a framework or structure that will provide non-technical users flexible and "unmanaged" ability to add/edit/remove documents, spreadsheet, and reports. Looking for a high level "dashboard" to provide the structure / hyperlinks / relationships of more detailed documents. So more of an organized document repository than providing information. My first thought was to create "static" locations a file server that LBI could maintain persistent hyperlinks to as a way to guide the group to related information. The person would put the documents into the appropriate directories. So while the the files may seem disorganized, LBI would provide the organization as the front-end.

Does anyone have any suggestions or better approach?

Thanks for any help!



BACKGROUND for further clarification:
We have a management level group that comes together for monthly meeting to discuss their area of responsibility. Prior to their meeting, information and supporting documents are made available to the group to review so the meetings are to discuss the solutions and not the problems. Currently the group has a shared and secure directory and sub-directories on a file server that they put there documents in. As you could imagine there is not a structure on how documents are related to each other so except for the one that produced the items no one knows how everything is related. The content would be edited throughout the month by the various managers which eventually be reviewed by the group. Since files names and the number of documents would change each month, I wouldn't want to be continually maintaining LBI with rights, file names, etc.