Hmm, your right. We are a small student corporation, so we don't need many groups (though we have quite some commissions, about 26 for 230 members).

Now I've thought about this system for some time, and my cms has a modular structure. It's build only with plugins, so I thought the relation domains -> plugins isn't that hard.
Another thing is the object relation. Each plugin can have several objects, but I don't want to store all the objects from all plugins into one table. Then my modular system is going to be completely messed up.
Is there a solution to have a table for every plugin? E.g. my gallery has tables plugin_gallery_categories, plugin_gallery_albums, plugin_gallery_photos and plugin_gallery_reactions.

Do you think, is it alright to create an additional table "plugin_gallery_objects", which replaces the complete rbac_objects and rbac_domain_has_objects table structure?
I think the queries are harder to create with this solution, but couldn't think of another. Of course, it is still possible to store the objects into a seperate object table and create a plugin_has_object table, but don't think that is a clean solution. What do you think?

Thanks for your (previous and upcoming) advice!