yep. there are two ways to do it that we have found: 1) use role merging - problem with role merging is that if you change the KSC pane you will run into problems since the role merging is only done on initial account login. With some creative use of references you can sorta alleviate problem but then you have problems with the top level panes being updated (i.e. if you want to add a new mandatory top level pane, etc...) 2) use references and some extra accounts
We choose option two. The following is a description of the process. For example, HQ is the select pane. it consists of sub panes that are mandatory. The only pane a user can change is MyArea __HQ__ | Helpdesk | MyArea Home | Ops | Plans | Logistics We create a the following users for each pane HQ = _hq Home = _hq_home Ops = _hq_ops Plans = _hq_plans Logistics = _hq_logistics Helpdesk = _helpdesk no user is created for MyArea since that is owned by the user. create a security group called KM create a security ID using the Security Browser called user-view_km-control with the perms: View Role User, * Role KM add all the _* users to the KM group Then, we create a new user called _newuser than "owns" the top level page. Each pane is created as a reference so the _newuser and _hq users need to be in the Jetspeed Admin role so they can use the Add Reference function. login as each _hq_* and _helpdesk user and create a page for them. make sure the page and portlet perms are set to user-view_km-control login as _hq and create a menu pane, and add references to the _hq_* users' panes. login as _newuser and add a menu pane and then add references to _HQ, _Helpdesk, and create a MyArea pane for the user with the "Owner" permssion set. _HQ and _Helpdesk should have the user-view_km-control perm set. login as turbine and delete everything and create a reference to the _newuser psml file. then if you have your users inherit turbine's config on login you should be good to go. The user can edit the MyArea but nothing else. If you chane any pane the contents are updated for each affected user as soon as the page is reloaded/redisplayed. I can send you copy of our .psml files if you are interested. boyd > -----Original Message----- > From: Dalton-1, Michael [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 14, 2003 12:33 PM > To: 'Jetspeed Users List' > Subject: Mandatory Tab / Portlets > > > We are attempting to use the Jetspeed framework for an > internal portal. > > I have a requirement to have a mandatory Tab with portlets > that can not be customized. > > For example, > > KSC | myKSC | myProject > > In the above tabbed arrangement I want to "lock" the KSC tab > so that it (and all of the portlets it contains) can not be > modified. The user will be able to create other tabs and > modify the "myKSC" and "myProject" tabs. > > Can this be easily configured in Jetspeed 1.4b4? > > If not, any ideas where in the code to look? > > Thanks for any help, > > [EMAIL PROTECTED] > Internet Business Manager > Computing Systems Services Branch > Information Technology Directorate > IT-D3-A / CIF 394B > Kennedy Space Center, FL 32899 > (W) 321-861-2207 (F) 321-867-7133 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
