File Permissions

Question

Hi 
 If M-Files does not support folder hierarchy. Could someone suggest a workaround to assign file permissions for a new added user. For eg. If I have 10000 files in M-Files all spread across the application in different locations. How can I select all those files and give access to the newly added user. Please this issue is a show stopper. Any suggestions would be highly appreciated. 
 Thank you

Wesley Weir · Accepted Answer

To get the permissions to work you need a property that points back to the users list. An ACL won't work for metadata driven properties. 
 Let's use 'Attendees' as the property. 
 
 Then in the class(es) set automatic permissions that pulls from that property. 
 
 You should now have a class(es) that will automatically set the permissions based on who is listed in the Attendees properties. 
 Now you just need to determine how/who to add to the attendees. You can leave it manual so that someone can just go add and remove users as needed from each object. 
 Or you can setup a configuration rule that can predefine which users should be in the list based on other criteria along with defining if the property should be hidden or read only. 
 https://www.m-files.com/user-guide/latest/eng/metadata_card_configuration.html 
 That last part would be outside the scope of this thread. Hopefully that answers how to set this up. 
 When done it should give a lot of flexibility.

Craig Hawker · Answer

Hi. 
 This sounds like a job for metadata-driven permissions and user groups. Using this approach would mean that the new user simply gets added to one or more user groups and they automatically get access to everything they need. 
 I recall from previous posts that you are not engaged with your reseller. That is unfortunate, as your reseller should be best placed to consult with you about what you want to achieve and the best way to structure M-Files to achieve it. You would probably save yourself a lot of stress by being guided by a good consultant. 
 That said, there is documentation on our user guide about how tk configure metadata driven permissions. What you effectively do is configure that certain elements of metadata (e.g. the object class) force a set of permissions onto the object; simply by selecting that this is an "HR Document", the document is automatically hidden from most users. 
 You use this approach to build a set of permissions for each type of object in the vault. 
 Regards, 
 Craig

File Permissions

Top Replies