This all really depends on how you have structured you page, the session variable can be used anywhere in you site to validate the user and the operations they can perform.
For example you will have a link somewhere for users that says something like "Edit My Profile" and another link that the admin can see that says "Add New User".
When the links are pressed they both go to the same page in either an 'edit' mode or an 'add' mode based on your code. to prevent a user going to the page in 'add' mode hide the link from them based on the session variable and again test on the page itself.
eg
Code:
if (session("UserLevel") = "ADMIN") then
'show the link
response.write("<A HREF=""AddEditUser.asp?=MODE=ADD"">Add New User</A>")
end if
response.write("<A HREF=""AddEditUser.asp?=MODE=EDIT"">Edit My Profile</A>")
then on the AddEditUser.asp Page you can test again to ensure that the user does not just type in the URL into the browser to get the page in add mode.
eg.
Code:
IF (request("MODE") = "ADD") then
'Test to ensure the user is admin
if Session("UserLevel") <> "ADMIN" then
'the security level is to high redirect them to another page
response.redirect("Youdonthaveaccess.asp")
end if
end if
IN SHORT
You can use the session variables to make anything in you site available (or not) to anyone how you wish.
======================================
They say, best men are moulded out of faults,
And, for the most, become much more the better
For being a little bad.
======================================