Access Denied - Change Permissions required with User from Metadata

Question

Dear all, 
 We've noticed that when we're using "User from Metadata" to give that specific user some permissions, if this metadata is changed, the other users need to have the "Change Permissions" Allowed otherwise they get an access denied error message. Is that a normal behaviour ? We find that kinda weird, because we want to give them the rights to change a M-Files user through the Metadata card but deny them to change all the objects permissions. Thanks for your replies Claudio

Joonas Linkola · Accepted Answer

This is by design. The user needs the "Change permissions" rights to be able to perform any operation that affects the permissions of the object. This applies to both modifying them via the Permissions dialog or modifying a metadata value that is used in the object's access control lists.

dejan · Answer

This makes sense as your project property is driving permission on specific report object (using pseudo users or metadata-based security). In that case, your user effectively change permission on report when he/she assign new project. For that project's technician must have change permission rights. 
 We have similar case with drafters who need to add/remove certain approvers who are used to be assigned to have permissions on documents, so if drafter change approvers he/she effectively provides access to different users. For this change permissions rights are needed.

Access Denied - Change Permissions required with User from Metadata

Top Replies