Prevent a TS user creating content in the root of the workarea

Hi

Using 6.7.1 TS on windows platform.

Trying to figure out how I can prevent a user from creating content at the root level of the workarea, but still allow them to create content in the directories.

I have tried workarea permission set to read only for the user, and then changing templatedata for the user to have wirte permissions.

I have also set the iw.cfg mask_workarea_access=no

As soon as I change the workarea permisssion to read only the Generate button from a template is greyed out.

Any thoughts?

Thanks,

Find more posts tagged with

Comments

Adam Stoller

Hi

Using 6.7.1 TS on windows platform.

Trying to figure out how I can prevent a user from creating content at the root level of the workarea, but still allow them to create content in the directories.

I have tried workarea permission set to read only for the user, and then changing templatedata for the user to have wirte permissions.

I have also set the iw.cfg mask_workarea_access=no

As soon as I change the workarea permisssion to read only the Generate button from a template is greyed out.

Any thoughts?

Thanks,

In general: User Training
If specifically with regard to templated content: Utilize FormAPI, Workflows, and customizations to remove the ability for users to initiate Page Generation directly by themselves.

RonaldV

Branch/workarea/directory permissions are shaky and undocumented in Teamsite. :-)

And I think you have hit one of these cornercases where this shows.

I'm know you can set permissions on directories in a workarea (to readonly f.i.) but if you try this on the (wa-)root teamsite might/will think that the whole WA is readonly. Hence the disabled generate button.

All I can think of is a auto-generate-workflow that will take the generate-load of the users-shoulders.

gzevin

In general: User Training
If specifically with regard to templated content: Utilize FormAPI, Workflows, and customizations to remove the ability for users to initiate Page Generation directly by themselves.

user training does not always work. or this approach is acceptable to business.

I've seen workflows handle this. One can predefine what kind of file are allowed in the root, and the rest will be routinely removed.

ExpressionLogic.docx