Folder permissions

[former_member709328]

Hi,

I know that is it not possible to restrict access to folders but how do others go about inexperienced authors that move around stuff in a workarea.

We have a problem where new inexperienced authors move stuff around in the WA. We have seperated our work area into three folders.

1. Development of new material (Sandbox for new authors)

2. Maintenance of published material

3. Published material.

Ideally we do not want the new authors to move stuff around between the folders untill they know what they are doing, but how can we prevent that?

Thought about creating another WA where they could play around and create their first simulations, but is it difficult to copy paste content between two workareas?

Best regards,

Thomas

[DirkManuel · Accepted solution]

Why do you have separate Dev, Maintenance, and Published Groups? SEN's version control coupled with the Publishing tag means that you can have all your content in one place, from creation through to delivery. If everything is created/maintained/delivered from the same place it is less likely to get moved to the wrong place...

But if that structure works for you then OK, you do you. If an author gets things wrong, re-educate them / make them take remedial training. If they continue to get things wrong, remove their access (possibly for a period - maybe until they have completed the remedial training), and point out that if they can't do their job correctly, maybe they should find another job. It's harsh, but you cannot have people making more work for everyone else because they are incapable of following simple instructions. If they can't get that right, how do you know they are getting the actual content of the training material right?

(No, not difficult to copy content between workareas, but it is extra effort.)

[peter_schirmer2]

The easiest way is to define one person who is responsible for the group "Published" or for any other folder that should not be deleted.

This person mark the folder, e. g. "Published" and then select "Server Bulk Actions", "Keep all Objects for Offline Editing".

Then only this person is allowed to make changes. But keep in mind when this person is on vacation the setting "Relese all Objects for Online Editing" has to be selected.

BR,

Peter

[former_member709328]

Hi Peter,

Thank you. Unfortunatly we have several people responsible for the folder "published" and our authors have publish permissions. Our problem is that we are working in a live environment and it only takes one author to mess everyting up :).

Best regards,

Thomas Nakai