CyL's nOtE

A Relationship will inherits permission from its parent when ItemType uses "UseSrcAccess". Although using same permission, the background check logic is a little different. In general, system will check "CanAdd" from ItemType when user executes "add" action, and will check Permission's Access for "edit" and "delete" action. As long as an item is a Relationship with "UseSrcAccess", system will check if "can update" permission of its parent is available alternatively when executing "add" and "delete" action. I guess this kind of design aims for the data safety of adding/deleting Relationship due to user cannot only delete Relationship without editing parent Item in normal situation. But in some customization scenarios, operating Relationship directly is possible (e.g. using AML command).