RE: [Dotproject-cvs] New user permissions

[John P. <ko...@dr...>]

Andrew and DP Team:

I like  the new interface, but it makes our older "permissions" screen
redundant and unnecessary. I recommend we replace links to "permissions"
(from userlist's "permissions button" and view user "edit permissions" to
link to the new "tabbed" permissions screen):

[New permission access model]
index.php?m=admin&a=viewuser&user_id={insert-id-number}&tab=usr_perms

This would mean that all calls we'd previously used to access "permissions"
would become deprecated:

[Deprecated permission access model]
index.php?m=admin&a=permissions&user_id={insert-id-number}

The drop-down list for permission "Item:"s is very slick... However, we
might want to look at increasing the "logic" tying projects with companies
(and possibly departments).

For example, it is easy to restrict a user from any given company or sets of
companies by choosing the "Companies" module and any relavent companies from
the "Item:" list.

However, our "Projects" module "Item:" list is simply a list of Project
Names without any indication or tie to "Companies". Hence, a user that may
be denied access about Company123 in the "Companies" module will still have
access to Company123 "Projects" unless the project name is selected and
specifically denied.

It would be nice if the "Item:" list for the Projects module could group
Projects by Company (and possibly Department) and provide the option to
apply permission levels to these larger "groups".  For example, imagine the
following "Project Selector Item List":

Misc Projects [all]
	Project ABC
	Project XYZ
	Project Alpha
Company: 123 [all]
	Project ZZZ
	Project SECRET
	Grocery List
Company: ACME [all]
	New Communication Strategy
	New Employee Training Initiative
	Company: ACME | Department: Marketing [all]
		Project Beta
		Product Yippie7 Testing
	Company: ACME | Department: Accounting [all]
		Downsizing Plans
		Promotion Plans

This would give us the ability to quickly apply permissions to "groups"
of Projects based on Company and/or Department... as well as fine-tune
control on individual projects (as we have now).

We may also want to consider adoption of a permission setting module for
"groups" of users also based on company/department. In this way we could
do bulk permission updates for many users simultaneously.

Just my thoughts. Really pleased with the changes.  Cheers, John

From ANDREW:
> Could you please test and comment on a change to the user permission
> handling.

> In the view user mode, the permissions tab can now update the user
> permissions.  The original permission page is currently unchanged.

> think this approach will be a little more portable across the different
> modules.  The structure could also be applied...