Synergy issue with object access restriction

Background

Synergy provides for setting both read and write restrictions on all kinds of objects (projects, files, directories).

When the restrictions are applied only the members of the specific predefined security group are able to read or read and modify objects as appropriate.

If you get the "write restrictions" error during check out, you are probably not a member of the security group that owns an object.

Security restrictions are applied hierarchically top down, from the project level down to the individual files.

Access mode to the object can only be changed while the object is in the modifiable state (e.g. "working").

When the security restrictions are lifted from the project, non-modifiable members of it (files and directories) are still left with the original restrictions applied. Even when the objects subsequently become members of other projects, restrictions on objects are retained.

More on the subject is in the original vendor docs.

What to do?

Find out what group the object belongs to (GUI, Object Properties -> Security).

Find out the group owner (CLI, first user that appears in the list of group members).

Call the group owner to see if you should be added to this group to gain an access to the object.

If you create a new project version and wish to lift all the inherited access restrictions that may exist on your project objects, call CM admin to do the job.
(The ugly solution is to have the original group member or admin Check Out all the project members and change the security settings on the checked out versions without making any other modification to the objects. Then Check In all the objects back.)