[Typo3] Backend usergroup with disabled 'Include Access Lists'

[Mathias Schreiber [wmdb]]

Georg Rehfeld wrote:
> Ahh, yes, which would require the group to include some other
> group(s) to have any influence (besides categorizing users, which
> might be usefull on it's own, e.g. assigning them to some department,
> but not enabling anything at all to them?).

correct.

>> Or grouping file or DB mounts.
> 
> Yes, sorry, I now recognize, that the long "access list" settings ai'nt
> the only settings made to group members. The "Mounts" ain't managed in
> the group really (only their availability to members), real access to
> them then can/must be managed for every user.

Not completely correct.
You CAN manage file mounts as well as DB mounts only via groups.
Example:
A client has a news page.
12 of his editors are allowed to work on that certain pagetree and are 
allowed to use files from /fileadmin/news_assets/.
I would set both DB and filemounts within a usergroup called 
"newsmounts" for easier maintainance.


> If you don't think so, _please_ correct me, before I'm going to enter
> my view of points into the german CSH.

done :)


-- 
No Subject - No Realname - No Service!
Respect the List/Newsgroup Rules!
  >> http://typo3.org/1438.0.html <<