I'm working on my first web application that will utilize a database. The basis for the application is a design approval system. I work for a company which mainly produces print and online marketing materials, most frequently magazines and websites. I'd like to have all communication run through the site and host all of our files there rather than work through email and various file delivery systems since most of them are too big to send through Outlook.
This is the schema as I've designed it so far (only the magazine part is included thus far):
The way I figure it should work is everyone is assigned a username and password. The
roleid indicates if they're a writer, editor, graphic designer, advertiser, or customer. If they're a designer, writer or editor they'll get to see all of the currently unapproved magazines and see what needs to be done as well as make posts and download/upload files.
Advertisers will be brought directly to the page regarding their advertisement and see any posts that our writers/designers have posted as well as download and upload files.
If they're a customer (owner of the magazine) they will get to see all of the editorial as their own section as well as a section for where we are in regards to layout/final product and respond to our writers/designers as well as upload/download files.
If y'all can point me in the right direction I'd be really appreciative.