Restrict components in fixed layout

I'm trying to find a happy medium between the totally fixed components of a regular Template and the free-for-all of an optional Area in a template based on a Fixed Area Layout.

On a template based on a FAL, can we restrict which Components can be added to certain Areas, or restrict which components can be seen by certain users? In "The Definitive Guide To Interwoven TeamSite" figure 19-8 on page 441 shows a screenshot of 'LiveSite New Component entry form permissions' - but I can't find this sort of functionality in v7.2.

Apologies in advance for being a noob - but if anyone can offer advice, or direct me to any decent documentation I would be most grateful.

Find more posts tagged with

Comments

Bowker

I asked the same question a while back and got a response of "Nope, can't be done."

One thing you can do is play with classes and if a component appears in an unexpected spot it displays a big red X instead of the intended content. I have searched in vain for a way for a component to know which area it's in while it's being built but I've not succeeded.

interDev

i don't think there is a way to stop users from adding specific components to specific areas but as Dan mentioned, there are ways by which content in specific components can be hidden when added to specific areas.

Blair Mackintosh

Thanks for your feedback. What's really frustrating is that a colleague can remember this functionality being demoed a few years back - where components could be dragged into areas from a component 'palette' and they would only drop into areas that allowed them to be dropped into. We'll keep plugging away...

Rob76

I'm not sure it's designed the way you're describing, in the sense that you can prevent components from being dropped on a FAL.

You can prevent a user from removing components as a whole by defining this in their Role...

The name of the operation is “Remove Page Component”.

ReferSheet2fromSheet1_error.xlsx

ReferSheet2fromSheet1_error.rptdesign