How Scoping Object Protection Works

Introduction › Protection › How Scoping Object Protection Works

How Scoping Object Protection Works

During subset definition, you request protection on a scoping object.

During subset checkout, the protection level is granted according to the following table, assuming the scoping object is not in a subset that someone else is using and the expansion of the scoping object is complete.

If you request an available scoping object with this protection …	You will get the scoping object with this protection.
Delete	Delete Note: This is true only if your subset contains all references to the object you want to delete. Otherwise, protection may be downgraded to Modify.
Modify	Modify
Access	Access
Read	Read

If a scoping object in the subset you are checking out is included in a checked out subset, the protection level you request for that object is downgraded if there is a conflict between this protection level and that already granted to the object in the checked out subset. The six combinations causing conflict follow:

If you request a scoping object with this protection	But the object is checked out with this protection …	You get the object with this downgraded protection
Delete	Delete	Read
Delete	Modify	Access
Delete	Access	Modify
Modify	Delete	Read
Modify	Modify	Access
Access	Delete	Read

Object protection determines what you can do to the object and what others can do to the object while you have it checked out in a subset.

Objects are assigned protection based on three things:

The correlation of the object to the scoping object
The expansion option of the scoping object
The protection level requested of the scoping object