Shared workarea issue

I created a workarea shared by a group of users. After I create one dcr in the workarea, other users in the same group cannot edit it. I noticed that the file's group property is "staff", not the one sharing the workarea.

Does anyone know how to fix the problem?

Find more posts tagged with

Comments

Migrateduser

Is this on Windows or on unix? The answer differs depending.

The first thing I would suggest would be to use submit.cfg to set ownership and permissions, but since this is a shared workarea, I assume you are experiencing the problem before the file is ever submitted.

On unix, you need to look into the umask command. It will set the permissions masking, so at least you can make sure it is editable. As far as the ownership, I believe unix sets the group to be whatever the primary group of the individual who created the file is.

In windows, files inherit their ACLs from the directory in which they are placed - so if the directory is

User Bob - full control
Group peons - Readonly
Group workers - Change

Then any file created there will be full control by Bob, and peons will have only read permissions; workers will have change.

Cheers
Rob Huffstedtler
rob@bagpipe.com

pdf.JPG

HarryH

Thanks for your reply.

It is on Unix.

I tried submit.cfg. It seems that submit.cfg only set the owner, group and permissions on the files in the staging area and the files being generated through the "Generate" GUI in workarea. But what I want is sharing the DCRs between all group users in the shared workarea. My problem is the DCRs and files created by using "New File" menu in the shared workarea do not have the same group name of the shared workarea. So any other group users cannot edit the DCR in the shared workarea.

I probably cannot use umask or chmod here because all group users are at business side. They don't have terminal access to the CM server. What I am looking for is a configuration that automatically set group name to all files (including DCRs) in the shared workarea.

Any suggestions?

Bowker

The submit.cfg file will also set the owner/permissions on the files in workareas at submit time. One would assume that you have locking turned on and that you probably don't want one user modifying another's work until it has been submitted anyway.

If you are using workflows you could put in an external task to chmod on the file.

If not you could build a custom menu item that runs a perl script that issues the chmod command.