https://www.webmaster-forums.net/crss/node/1013668 en https://www.webmaster-forums.net/serverside-scripting/help-preempt-head-scratching-will-work-ok#comment-1079092 <p>security...</p> <p>When they login and they are authorized, set a session cookie (like userID). Then on every page check for that session cookie (using an include works best), if it's not there, or it's null (cookie exists, but is blank), or guest (if you'll have a guest level), kick them out to the login page.</p> <p>If you have a page that only specific people are authorized for, use the session cookie to query your DB and check their permissions. If their authorized for that area, let them in, if not...</p> Thu, 08 Mar 2001 18:15:48 +0000 Mark Hensler comment 1079092 at https://www.webmaster-forums.net https://www.webmaster-forums.net/serverside-scripting/help-preempt-head-scratching-will-work-ok#comment-1079091 <p>I've written a few admins, and I like the framed layout...</p> <p>I like to put 'admin sections' on the left frame, and the actual table editing functions on the main (right) frame.</p> <p>I'm guessing you'll use radio buttons for those options in the left frame? One set of radio buttons for the actions and one set for the tables? I always used textual links for my nav stuff, but I like the idea of using radio buttons...</p> <p>Will all your users be able to perform all the functions? If not, you'll want to add fields to your username/password table... When they login, check the username/password as usuall, but now check the permissions too. If that user is not allowed a feature (like delete) or table don't print that option in the left nav frame.</p> Thu, 08 Mar 2001 18:09:14 +0000 Mark Hensler comment 1079091 at https://www.webmaster-forums.net