Introduction › Protection › How Expansion Object Protection Works

How Expansion Object Protection Works

When you select a scoping object for a subset at default expansion, the subset includes not only the scoping object but also its components. Component objects are integral to the scoping object. There are two types of component expansion objects:

• Shared component-Is shared by other scoping objects.
• Non‑shared component-Belongs exclusively to the scoping object.

The protection implicitly requested for components is based on the protection explicitly requested for the related scoping object.

For shared components, protection is inherited from the scoped object. That is, whatever protection you explicitly request for the scoping object, that same protection is implicitly requested for all the shared components of that scoping object.

For non‑shared components, protection is automatically upgraded to delete if the protection requested for the scoping object is Modify. This lets you delete non‑shared components of an object scoped with Modify. Other implicit protections follow:

When you select a scoping object for a subset at full expansion, the subset includes not only the scoping object and its components, but also its shared companions. Companion objects are not integral to the scoping object, but add context.

The protection implicitly requested for companion objects is based on the protection explicitly requested for the related scoping object. A companion object is granted the requested protection unless another user already has this companion object checked out at a conflicting protection level.

The correlation between the scoping object and the expansion object is what determines the protection requested for the non-scoped expansion object. There are four correlations used in the expansion table:

• Shared Component
• Non‑Shared Component
• Shared Companion
• Special 1.

Special 1 refers to a Relationship Membership assigned the lesser of the source or target entity's protection