Sounds good.

On Tue, Oct 4, 2011 at 11:10 AM, Josh Thompson <josh_thomp...@ncsu.edu> wrote:
> Hash: SHA1
> In 2.2.1, there is a problem with block allocations.  You have the option to
> set the managing user group to 'None'.  If you do that for a block allocation
> that was requested by a normal user, then no one will be able to manage the
> block allocation.
> In 2.3, there will be the option to grant any user group access to manage
> block allocations for just their affiliation.  I'm thinking with this option,
> there is no longer the need to select a managing user group for block
> allocations.  So, I'd like to just drop the managing user group altogether.
> In which case, if you are in a user group having the "Manage Block Allocations
> (affiliation only)" permission, on the Block Allocations page, you'd see all
> block allocations owned by people with the same affiliation you have.  If you
> are in a user group having the "Manage Block Allocations (global)" permission,
> you'd see all block allocations.
> Does this sound okay to everyone?  Is anyone using the managing user group in
> such a way that this change would cause a problem?
> Thanks,
> Josh
> - --
> - -------------------------------
> Josh Thompson
> VCL Developer
> North Carolina State University
> my GPG/PGP key can be found at pgp.mit.edu
> Version: GnuPG v2.0.17 (GNU/Linux)
> 2GIAn0sS05NdJEruBKEBektSgiS7Lo5j
> =UFdt

Aaron Peeler
Program Manager
Virtual Computing Lab
NC State University

All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.

Reply via email to