I don't think this would cause us any problems. The way we use block allocations, we always set admin@Local as the managing group.
Mike Waldron Systems Specialist ITS Research Computing University of North Carolina at Chapel Hill CB 3420, ITS Manning, Rm 2509 919-962-9778 -----Original Message----- From: Josh Thompson [mailto:josh_thomp...@ncsu.edu] Sent: Tuesday, October 04, 2011 11:11 AM To: vcl-...@incubator.apache.org; firstname.lastname@example.org Subject: VCL-427 managing user group for block allocations -----BEGIN PGP SIGNED MESSAGE----- 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk6LIfwACgkQV/LQcNdtPQPkrQCfU+opGZ0EHsDoFT1hqoU6daSX 2GIAn0sS05NdJEruBKEBektSgiS7Lo5j =UFdt -----END PGP SIGNATURE-----