Hi Steffen, Steffen Gebert wrote: > Xavier Perseguers wrote: >> Does someone already experienced having to manage high number of groups >> (let's say you have 50+ non-overlapping sections in your website) that >> should be assignable to 50+ groups and for each of these sections, you >> have let's say 3 "roles" (read-only, editor, publisher). >> >> The problem I see with security management is that it is not possible >> (AFAIU) to combine group A (db and file mount points) with "role" X (ACL >> on records and plugins) to create a special "bundle" that is assignable >> to a user. As it seems not to be possible to give user Y read-only >> access on T1, but editor access on subtree T2 without having to create >> additional "logical" groups that contain both a group and a role, which >> leads to 150+ logical groups in the backend. > > I posted a similar question last week but got no answer. I'm really > interested in this, too! (although we don't have THAT much groups)
Oh, I did not notice your post, sorry! Well, in my case, I would have even more groups. I'm planning using extension "roles" which I guess could help a bit circumvent the lack of "bundle" ACL separation problem but I cannot imagine managing so many "dumb" groups in the backend... -- Xavier Perseguers http://xavier.perseguers.ch/en One contribution a day keeps the fork away _______________________________________________ TYPO3-english mailing list [email protected] http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english
