For future reference, I was wondering...
Given Example:
Site that allows workers to hook up with employers
-workers fill out resumes
-employers can browse resumes
-administrators can edit worker/employer account settings
Question:
What is the best way to structure the directories and tables to keep one group from getting access to anther groups files? I was thinking of three folders, one for each group, then a check_login.cfm include that is specific for each group. I would have 3 different db's just for safety's sake as well as to house dif info for each group...ie the workers would have their resume info, employers would have their account info, etc.
I was curious what others have done to maintain internal security between the different groups that have access to a site.
Given Example:
Site that allows workers to hook up with employers
-workers fill out resumes
-employers can browse resumes
-administrators can edit worker/employer account settings
Question:
What is the best way to structure the directories and tables to keep one group from getting access to anther groups files? I was thinking of three folders, one for each group, then a check_login.cfm include that is specific for each group. I would have 3 different db's just for safety's sake as well as to house dif info for each group...ie the workers would have their resume info, employers would have their account info, etc.
I was curious what others have done to maintain internal security between the different groups that have access to a site.