Overview
How changing permissions to a large quantity of objects worksSpecifics
Changing permissions to a large number of objects at once is handled as a background task in M-Files server. A new task is created and executed when the previous task on the list has been completed.While this background task is running, no other background task will be run until earlier one has been finished.
In large environments, the permission change task can last a long time, as the system will go through every affected object and their history versions.
Adding new user to the named access control list vs. adding to a user group
When a new user is added to a document vault, it’s advisable to add a user to some user group which is included in named access control list (NACL), instead of adding the user as an individual user to the NACL.
This is recommended, because when the user is added to a user group, no new background task is created. In this kind of situation, the permission for the accessed object gets updated only when someone accesses the object.
If the user is added directly to the named access control list, a new background task will be created, which could cause latency to the other usage of the document vault.
