I'd like to have this project written in ASP.NET, preferrably VB instead of C#. I will need a mild database too...a modified ASPUSERS database is fine.
I'll need 3 levels of users. One for the site-wide management, me. When I log in I want to be able to create a user ID, so just the ASP.NET Login Control. I want to be able to disable users and see who I have. If there is a way upon registration to enter a group name, that would be great, that way when I see the active users I can see them separated by groups, such as technical, processing, management, etc. This doesn't need to be in the database or populated by a drop down, a simple textbox would be sufficient.
From my login I also need to be able to create pages with fields on them. For example I could create a form for the technical group and it would ask for a label name, I could type in First Name and hit plus and if I wanted to enter more I could type Last Name and hit plus. When I am finished I could hit submit. This form should now be available for the technical supervisor (next level I am going to discuss) and the technical workers (the last level). These forms should save the data in the database. These forms may be entered multiple times from the same user.
The supervisor level of each group should have the ability to see the forms available and see the form data that each user has submitted by date and title that the user saves it as...the title can default to some fields of the entered data, extending the example above...[url removed, login to view], could be the default title. The user (described next) should be able to change the populated default text in the textbox for the title is they would like. When the supervisor clicks on the title they would like to view, it could show up on a viewable page, pulling the data from the database....or a possibility is to have the system create a PDF of the information they submit and save that on the system (iTextSharp) and the supervisor can pull up the PDFs when they view. This is optional (depends on how much extra you would charge).
The user level should have the available forms to fill out. The user can click on Form A, for example, go to the page with fields to fill out for that particular form and click submit. Save to the database, or as discussed - a possibility of saving the info to a PDF using iTextSharp, but that depends on the extra cost.
I may have made this sound more difficult than it is. Let me know if you need clarification. Do not worry about any graphics or design, you can literally throw it together, having white screens and Time New Roman as the font...that's fine.