Permissons to webpages..

[Abdar]

If we are going to have say 100 web pages.. and with each page there is a process (say one is a form that can send an email)

With every page/process you want to make sure the user has the proper permissions to use it.

It would be ideal to know what pages/processes the user has before requesting the page (say you wanted to generate links (and it's sublinks)to pages the person has access to).

Some pages/processes may be children of other pages/processes and some may not. An example of a parent/child relationship in this case may be a data entry page.. followed by a confirmation of data page.

You may not need to have permissions to a parent to use a child though.

The processing of this information would be done on the webserver with initial credentials checked through Active Directory (to get into the secure site) but the actual page/process permission information will be stored on a SQL server.

Hopefully I was kinda clear.. any insite on the subject would be great..

Thanks all..

Ab.

[Zaphod Beeblebrox]

Why don't you let users log in at first, and assign a security level based on that. Store it in a Session variable, and use it on the pages to determine what they can or cannot see and access.

[Abdar]

A security level requires that permissions to pages be grouped in a sense.

I basically want it so for any given user to have a set of pages (don't have to be related to each other)that they can access.

Just wondering if anyone had done something similar to that..

Ab