Portal website for apartment owners

We need to develop a web portal in which we can manage homeowner associations (real estate properties) online. The web application will function as a portal for all members in a homeowner association. Users should be able to use a simple message board, send complaints about the building to the administrator. They will also see an agenda section about the next upcoming homeowner association meeting. All information, (except for pdf's) will come from several XML feeds generated from our accounting software. The feeds contain user accounts, general information of the building and upcoming meetings etc. We will have one administrator super-user, an investor user (owner of more than one apartments) and a normal user. (owner of one apartment). Maybe we will have more roles in the future, but not now. Normal web visitors will only see one page with login functionality. We should use some moderate protection to protect the content inside the portal. Not state of the art protection, but a bit more secure than just basic. When the administrator logs into the system, he first will see a dropdown field with all homeowner associations that exist in our accounting system. (this should be done with a simple xml file that pulls the current list of all associations into the dropdown field). If the association doesn't yet exist in the portal, the administrator will get a notice that a new webpage will be made. And all standard information, like address, phone numbers, upcoming meetings etc. will be imported from the xml files. Next, all members from that particular association will be imported into the system. If the import is successful the administrator will have the opportunity to send a notice by email to all users to validate / activate their e-mail address / accounts and choose a password. Users should be able to reset the password by filling in their e-mail address and member number. As stated we have (beside the administrator) an investor user account and a normal user account. The only difference between them is that the investor user will see a list of all owner associations where he has properties. So he can choose which one he wants to see. A normal user will go directly to the page of his homeowner association, since there is only one. The portal website of the association will consist of one panorama image on the top and below that 4 content blocks. The administrator should be able to upload a new panorama image. If no image is uploaded than a default image will be used. The first block will consist of standard information of the property (pulled from XML), like address, Google map and street view, and a list of several PDF files that will be uploaded by the administrator in de portal backend. The second block will consist of meetings; on top there will be the next upcoming meeting. If you click on a date you will get more information about that meeting (pulled from XML). The administrator will upload more information in PDF format in backend. Standard file upload functionality, with description and date is sufficient. It would be nice if other that PDF, also standard jpg and other file formats can be uploaded. The third block will have a form for making complaints, and a simple overview of complaints that already have been made. Users should be able to see what the status (pending, solved, etc.) of the complaint is. The last block is a simple message board where users can add and read miscellaneous messages about the building. This is the base were we want to build upon in the near future. So it is important that it works flawlessly. We will provide the design of the portal in PSD.