AnsweredAssumed Answered

Issue with workflows and permissions

Question asked by Heather Nelson on Jul 7, 2008
Latest reply on Jul 15, 2008 by Heather Nelson
Some background first:
We have two workflows. One workflow is for part/asm/drws going through development release. The second workflow is for part/asm/drws going through a production release. We have our file structure set up with a project template that includes a design folder and a tooling folder. The design group are the only ones with read/write access to the design folder and the tooling group are the only ones with read/write access to the tooling folder. Designers have read only access to the tooling folder and tooling has read only access to the design folder.

The problem we discovered is a tooling engineer had some design files in his assembly and when he went to release his files at a production release it dragged along the design files. The tooling group does not have the permission Increment revision of a file set for the design folder. When he released his files it took design files that were already released at a development release and rereleased them to a production release. Both the tooling group and the design group have the same workflow permissions. It seems that the workflow permissions are trumping the folder settings. This seems completely backwards to me. Has anyone else run into this problem? So far the only answers I've gotten from our VAR is people do have permission to change the state of a read only file and that tooling should be more careful with what they change.

Outcomes