Overview
When using the Assign To option in Workflows, permissions can also be set around this property (see screenshot below).
This can be beneficial as it restricts the object to the user who is supposed to work with it.
But Assign To is a built-in special property inside of M-Files so comes with some caveats. In this instance, a user can have only Read/Edit permissions for an object but be able to remove themselves from the Assign To property effectively losing their access to the object.
Normally, what a user should see if they only have Read/Edit permissions for an object and they try to change the permissions on an object directly via the permissions menu or indirectly, via setting a metadata property that would change permissions is as follows:
Note: This only applies to the Assign To function from a workflow. If Assign To is being used in an Assignment object, we have control of that functionality from the Advanced Vault Settings à Configurations à Assignments menu (see screenshot below).
Solution
There is a workaround for this issue with Metadata Card Configuration where the Assign To property can be set as read-only with the following rule/JSON.
NOTE: This only effects non-Assignment objects. The Assign To property on Assignment objects should be controlled through the AVS settings provided and cannot be set to read-only on Assignment objects.
