Custom modules question

[twhiting9275]

Ok, so it's now time to convert my additions into "modules", perhaps for future release, but for now, not so much.

 

Right now, I've got a number of additions, spread out everywhere, dealing with two categories:

 

A> Servers (information, logs, who has what, where, adding them, etc)

B> Monitoring

 

Ideally (note: this is just an ideal situation), things would be split up as that, where I would have one server module, one monitoring module. However, a few restrictions would need to be placed. For example:

 

I want all linux techs able to access server info (client login properties, etc), but I only want site admins (myself) able to ADD server information.

 

Theoretically, the way to do this (again, I'm just grasping here) is this

create modules/admin/server directory

add modules/admin/server/server.php with the permissions as follows:

$adminlevel = "2";

And then add modules/server/newserver.php with the permissions as follows

$adminlevel = "3";

 

Since I lump support/sales staff into "1", tech staff into "2", and master users into "3", this should work, at least theoretically.

 

The problem comes in that my "theory" may or may not work. Since newserver.php resides in server, does it take it's permissions from server.php, or wha?

 

Yes, I know, I have to link to newserver.php, and do all that fantastic jazz. That's not an issue, the issue is controlling who can see newserver.php and who can not.