Re: [Phpwebsite-developers] phpws 2 usergroup

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

-------- Original Message --------
Subject: Re: [Phpwebsite-developers] phpws 2 usergroup
From: "Matthew McNaney" <ma...@tu...>
To: <wi...@ce...>

> New DocumentI was browsing CVS today looking at phpws 2 trying to pick
> up on what the next version will be like. I noticed that there will be
> "usergroups" in the next version with varying levels of access.

> My question is, will the "usergroup permissions" be setup this way to
> have varying access levels to modules or will I have to do that
> separately?

Dude! Flash on the developers mail! ACK!

Anyway, this is how it works. There is one log in. Your permissions are
set on a module per module basis. In fact, the user/group script is a
module. So from there I can assign:
1) Who has admin privileges - this is a switch to turn everything on or
off. If it is off, you just get to see the modules that a registered user
gets to see. These are things like controlling your personal preferences.
2) Who can access what module. You can't see the module and trying to get
there via a get statement is a dead end as well. Also trying to crack
that way may also lead to a warning and possible automatic banning (in my
head not written yet).
3) You can control who gets access to which components of the module. For
example, in the user module you can control who can create, delete, or
modify users.

There will also be groups. If you assign permissions to a group, that
template will copy over to the user. You can still change their rights
but they will be assigned to that group. So someone writes a module that
allows conditions based on what group they are in, they have flexibility
on what that group member does/or sees. This could be a strict layer of
security per group if you programmed it that way.

The API of the user rights is such that the developer just creates a list
of rights per the module and tells the core where it is. The core
automatically handles the parsing of that table so you can change
permissions from one place, not module to module.

Matt

Matthew McNaney
Internet Systems Architect
Electronic Student Services
Email: ma...@tu...
URL: http://phpwebsite.appstate.edu
Phone: 828-262-6493
ICQ: 141057403