Access to requirement objects through ownership inheritance is available only if the parent object was configured to propagate access to its child objects when it was created, and if the child object was configured to inherit access from its parent object when it was created. Both sides of the relationship must allow access through ownership inheritance for it to be enabled when the child object is created. When enabled on both sides of the relationship, ownership inheritance allows you to access the child requirements objects of any parent requirements object to which you have access, even if those child objects were created in collaboration spaces to which you do not normally have access. You can specify the default access settings for each type of requirements object. These are the default access settings shown when you create that type of requirements object. You can override them when you create an individual requirements object. You cannot change a child object's setting for access through ownership inheritance after it is created. Since cloning and revising automatically create a requirements object, you do not have an opportunity to manually override your default settings for that requirements object type. You can specify whether you want propagated or inherited access through ownership inheritance to use the default values for that requirements object type when it is cloned or revised. If you do not specify the use of the default values for that requirements object type, the access through ownership inheritance values defined for source object are copied to the cloned or revised object. | ||||||||||