This tab is only visible if you are authorized to assign roles to users for the selected object.
Note
Be careful with assigning roles to users. As a rule of thumb, assign the minimum number of roles necessary at the highest level possible. This rule will make it easier to work out which permissions a user has for a project, folder, document or document revision.
To remove a user from a role, select the role concerned. Select in the pane "Users for <role name>" the user you want to remove and click the button .
This setting determines if changes made to the authorization of an objects also apply to its child objects. In other words, with this setting objects like folders and documents can be isolated from changes made to the authorization settings of the objects they reside in, be it folders or a project.
By default this setting is on which means that you only have to assign Roles on the project level to assign them for all objects inside that project. Switching this setting off by unchecking the check box blocks all changes to the authorization made in containing objects.
The settings and forms the inheritance mechanism of authorization.
By default both settings are on. When the setting is switched off changes to the authorization settings will only be applied to the project. Note that this setting cannot be used to isolate the child objects from the changes made to a containing object. If you have for example a folder inside a project and you do not want changes to the authorization settings made to the project to have an effect on the documents inside the folder you should use uncheck the settings on all documents inside the folder.
The setting is only used to effectuate changes made at that moment to any objects inside the object whose authorization settings have been changed.
Thesetting allows you to force the authorization settings of a project or folder on all folders and documents inside them. In this way authorization levels can be reset for an entire project or folder structure to the settings of the containing object.
For a more detailed explanation refer to the chapter Roles and Authorization in the ITP/MDK Repository Manual.