When a user is assigned a role for a project, by default he will have this role for all folders and documents in the project. He will also have this role for all newly created folders and documents within the project or within folders in the project. However, there are situations that roles assigned on one level should not be inherited by lower levels. Use the setting 'Propagate authorization to all child objects that allow propagation' (tab Authorization) to turn off this automatic mechanism of inheritance.
The setting 'Reset authorization on all child objects to these settings' allows you to override any authorization settings on child objects, and set authorization to the settings of the parent. In this case not the changes are propagated, but the exact authorization of the folder is copied verbatim to all containing objects.
The setting 'Allow authorization from parents to propagate to this object' allows you to create an exception for a folder. By switching it off for a folder, authorization from a parent folder is not automatically inherited by the folder. In that way, specific authorization can be set for that folder.
Refer to the Configuration Help for more information on these settings.
Note
Future changes to the authorization of the parent are propagated to the object. Assignments on child level will not be affected as long as the same assignment is not changed on parent level.
Note
Authorization is a property of an object. If an object is moved from one folder to another its authorization is moved with it as well. The authorization settings from the new folder or project where the object is moved to are not applied to the object, even if this folder or project has the setting Allow authorization from parents to propagate to this object activated. Only changes are propagated.