Note:
Bidirectional inheritance breaks "exception" configurations:
Base profile (gives full access to a folder except for a special subfolder):
1. /foo (all perms+inheritance)
2. /foo/bar (list files)
Other profile (gives full access to the same folder except for another special subfolder)
1. /foo (all perms+inheritance)
2. /foo/baz (list files)
Bidirectional merge will make /foo/bar fully accessible which contradicts the base profile configuration.
I think there is no perfect merging strategy that covers all cases.
This probably happens because of the incorrect order of your user roles.
Users with multiple roles get the bottom most profile
The heaviest profile is used as the base profile and merging is done on top of it. Other profiles inherit permissions from the base profile. Not the other way.
I guess this role ordering is not something that users pay much attention to and that's why I decided to make folder merging bidirectional in DFM 2.1.1
Unfortunately, folder operations are not available in the lite version.
Fixed on v2.0.9
Fixed in 2.0.6
Thanks