i feel silly posting since thought had handle on acls. have checked few tutorials joomla-acl-quick-sets-mg-12.png help. here scenario...
i have 6 main menus. have 2 drop down items in these main menus. if click on drop down item branchlisting, run split menu in left position. each left position branchname have either more submenus or articles. want able limit sees mainmenu or branchnames or specific articles.
i have many custom user groups. understand mainmenu custom groups child groups of registered group. understand branchname custom user groups child groups of mainmenu. understand departmentname user groups child groups of branchname. believe understand if assign user user group departmentname, inherit branchname, mainmenu, , registered permissions. user group layout looks below...
- registered
-- author
--- editor
---- publisher
-- mainmenu1 region1
--- branchname1
---- departmentname1
--- branchname
---- departmentname1
---- departmentname2
----- article1
-- mainmenu2 region2
--- article1 (welcome region2)
--- branchname1
---- department name
----- article1 (find department info here)
each viewing access level assigned corresponding usergroup. example: access level department1 has corresponding usergroup. access level have corresponding usergroup check mark.
my problem 1 of test users, testuser1 seeing way much. have added testuser1 usergroup mainmenu1. unfortunately, in drop down testuser1 can see other mainmenu2-6 in 1 dropdown. mainmenu items should either appear in navigation position or not appear @ based on permissions.
i had thought understood how assign viewingaccess usergroup, , assign testuser1 proper usergroup. advice appreciated.
i have 6 main menus. have 2 drop down items in these main menus. if click on drop down item branchlisting, run split menu in left position. each left position branchname have either more submenus or articles. want able limit sees mainmenu or branchnames or specific articles.
i have many custom user groups. understand mainmenu custom groups child groups of registered group. understand branchname custom user groups child groups of mainmenu. understand departmentname user groups child groups of branchname. believe understand if assign user user group departmentname, inherit branchname, mainmenu, , registered permissions. user group layout looks below...
- registered
-- author
--- editor
---- publisher
-- mainmenu1 region1
--- branchname1
---- departmentname1
--- branchname
---- departmentname1
---- departmentname2
----- article1
-- mainmenu2 region2
--- article1 (welcome region2)
--- branchname1
---- department name
----- article1 (find department info here)
each viewing access level assigned corresponding usergroup. example: access level department1 has corresponding usergroup. access level have corresponding usergroup check mark.
my problem 1 of test users, testuser1 seeing way much. have added testuser1 usergroup mainmenu1. unfortunately, in drop down testuser1 can see other mainmenu2-6 in 1 dropdown. mainmenu items should either appear in navigation position or not appear @ based on permissions.
i had thought understood how assign viewingaccess usergroup, , assign testuser1 proper usergroup. advice appreciated.
looks have lot going on, let me give quick answer first (instead of trying think through complete configuration).
modules hold menu assigned access level (to 1 , 1 access level). if want entire menu displayed or not depending upon group membership, create access level can assigned menu-holding module , set access level groups should see it.
each menu item assigned access level (to 1 , 1 access level). can menu module, can use custom access levels can selectively assigned each menu item. means menu can hold items each item can set independently can see item.
by creating custom access levels , applying them selectively menu modules , menu items, should able results want. keep in mind visibility , access managed access levels. neither menu items nor modules use permissions (although component behind menu item has permissions).
modules hold menu assigned access level (to 1 , 1 access level). if want entire menu displayed or not depending upon group membership, create access level can assigned menu-holding module , set access level groups should see it.
each menu item assigned access level (to 1 , 1 access level). can menu module, can use custom access levels can selectively assigned each menu item. means menu can hold items each item can set independently can see item.
by creating custom access levels , applying them selectively menu modules , menu items, should able results want. keep in mind visibility , access managed access levels. neither menu items nor modules use permissions (although component behind menu item has permissions).
Comments
Post a Comment