[AgileWiki] delegating access by groups

[Bill la F. <bil...@su...>]

The missing piece of access control, for both AW2 and AW3 has been the 
ability for any but AdMin to add users to groups.

I've just finished the addUser command, which is scoped to Cabinets. It 
requires only that you be the administrator of that cabinet. And what it 
does is create a row under the /Users LSec.

This means that users, after doing a "home", can do an "addUser" to add 
users to groups named in their own cabinet. Oh, and the addUser command 
also displays the rows relating to the current cabinet--it tries to be nice.

Unfortunately, I still need a way to remove a user. I expect this will 
be done by navigating to the offending row under /Users (which can be 
done via the addUser command) and then doing a remove. To this end, the 
rows under /Users are UsersRowRolons, not RowRolons. This way the remove 
command can be scoped to the rows of the Users lsec.

All this is a bit awkward, because only AdMin has write access to /Users 
and its rows. And that's vital, because this is a big part of the 
AgileWiki's security system.

Bill