Currently we assign products on a per usergroup basis, however when dealing with customers, they may own any number of products. This would mean that I need a usergroup for every possible combination of these products. What would be very useful would be the ability to select (via checkbox) the products that the client owns from the user management screen. This would allow the management of products via the current usergroup method and also the way I suggested, making it much more flexible and reducing the need for many usergroups!

The problem I foresee with this is that it would add a large amount of complexity to the user screen as it wouldn't be a simple checkbox of "ownership" because each user would have to have individual permissions on each of the current usergroup permissions. I think that a better solution would be to enable a user to belong to multiple usergroups and their permission scheme would be a combination of multiple usergroups. I think this would make the most sense, be the easiest to implement, and the easiest to understand for administrators because it would use essentially the existing model for permissions.

Yeah I see what you mean, I should have thought that through more, the other problem that I see is the initial user registration, the moderator would need to select the products that the user owns before they have access. Though I do still think the issue of having to have a usergroup per product or product combinations overly complicated so your solution would certainly be helpful. The only suggestion if you decide to implement this would be to add the ability to clone usergroups. So that usergroup 'product x' (has product x assigned to it) can be cloned when creating usergroup 'product y'. This would remove the need to select all the same usergroup permissions for a usergroup this is essentially the same, just responsible for a different product.

Thanks for the quick response.

The ability to be in multiple usergroups is now done and will appear in Beta 2. I'll be adding cloning of usergroups, too, but for now the backbone of permissions is done.

--------------- AUTOMATIC RESPONSE ---------------
Thank you for your bug report. This issue has been closed and fixed in Subversion. This change will be available in a future release, but you can download the change at any time from the Subversion server.