Overview
If common user authentication is used and a user without vault admin permissions can only access the network folder's top level, not the subfolders, the NACL settings might shed light on the matter.Symptoms
A user, who doesn't have vault admin permissions, logins to M-Files Desktop and accesses some network folder. The top level is visible, but when the user tries to access a subfolder, an error message like the one below is shown:Not found. (No access to the folder with the ID "D:folderNameHere".)
Cause and Reason
This can be caused by incorrect NACL settings.Solution
In the M-Files Admin's Configurations > External Repositories > Network Folder > selectConnection:Please try setting "Use M-Files NACL" to "Always" at least for testing purposes if it is not already set. Note: Make sure that enabling this doesn't grant unwanted permissions to any M-Files user. Use M-Files NACL which surely has enough permissions to access the network folder. One example below:
If the issue concerns all users who don't have vault admin permissions, one possibility is to create a test user and reproduce the issue within M-Files Desktop with that test user. After that, create a new M-Files NACL for this test and add only that test user to the M-Files NACL. Select that new M-Files NACL in the Network Folder permissions (as the Full control for all internal users in the example screenshot) and try navigating the subfolders with that test user.
