Rights in FLC + check-out an attachment by script

[PLM-Sylvain.Bailly]

Hello,

I would like to know if it is possible to manage the access rights item by item in a Revision Controlled Workspace?

Normally, in FLC, to manage the rights we have 3 different places:

- First, we must define the roles, assign them to the different groups where users are in. This work give access to the workspace and all the tab of the items of the workspace.

- If the workspace has a workflow (which is not the case for a Revision Controlled Workspace), we can define who can do the action and have access in R/W to the item. For this we use the scripts and the lock in the workflow.

- In a section, it is also possible to define who can have access to the section (“View-Only” and “Edit”). But this configuration is valid for all the items contained in a workspace (see attachment “Rights in section.png”). It is a workspace configuration.

1/ Concerning my problem, as my workspace is a revision controlled workspace (no workflow), it is impossible to have a script which give the right to a specific group/user for each item if I’m not mistaking. Is it true?

1 bis/ We cannot use the field “Owner” of the item to give the right to the owner only to edit the item and to check out/check in the attachments?

2/ The rights in the workspace is the lowest granularity to give access rights (because the rights per section will not fit to our need). Is it true?

3/ Is it possible with a script to check out an attachment contained in an item for a specific user?

I have read the script reference but don’t see this feature: https://knowledge.autodesk.com/search-result/caas/CloudHelp/cloudhelp/ENU/PLM-360-Scripting/files/GU...

Thank you very much for your answers,

Best regards,

Sylvain

[tony.mandatori · Accepted solution]

Sylvain,

The only way I've seen to restrict access to a group is to use additional owners.  But this has some limitations.  Additional Owners determines whether a user is allowed to see the record; any permissions on the record are determined by the regular permissions.   For example, just because the user is an owner doesn't necessarily mean he can also edit the record. 

Section permissions will override workflow permissions.  if the system is configured to allow only promoters to update the record, and we additionally apply section permissions, users with section permissions will be able to update the section regardless of the workflow permissions.

I don't see a direct way to checkout the attachment.  Checking the attachment out for the user will sometimes confuse the user, so I wouldn't do this.  My suggestion would be to loosen the permissions on the system.  The system keeps track of updates (through the change log), so we can always see who updated the record.  After some training users will know when it's their turn to make updates.  And for those that forget, we can always remind since we know who they are.   Content will always be stored in the History, so we shouldn't lose any content from accidental updates.

[PLM-Sylvain.Bailly]

Thank you Tony.

From my point of view it is a training problem. We must communicate more with our users to explain them how FLC works.

I can understand that it is a little frustrated for them as some of them have used another PLM which gives access by project/folder. Like that they can define access as Windows Explorer does (folder by folder and sub folder by sub folder).

Thanks again Tony