Security Labels and the Copy, Save As, Revise, and Move Actions
This section describes how security labels behave during the copy, save as, revise, and move actions.
|
Action
|
Description
|
||
|---|---|---|---|
|
Copy
|
When an object is copied, the security label values on the original object are copied to the new object. Object initialization rules are not applied to the new object. The new object does not carry forward any associations to agreements.
|
||
|
Save As
|
When a “save as” action is performed an object, the new object has the same security label values as the original object. Object initialization rules are not applied to the new object. The new object does not carry forward any associations to agreements. If a user is cleared to access the object by an authorizing agreement:
• a “save as” action performed within a workspace fails.
• a “save as” action performed outside a workspace succeeds, but the user cannot see the new object.
|
||
|
Revise
|
When a user revises, creates a new view version, or a new one-off version of an object, the security label values from the previous version are carried forward to the new object. Object initialization rules are not applied to the revised object. If a user is cleared to access the object by an authorizing agreement, a revise action within a workspace fails.
|
||
|
Move
|
If an object is moved, the security labels on the object remain the same. If the object was subject to an agreement before the move and if it is moved outside of the scope of the agreement, then it is no longer subject to the agreement. For more information, see Scope of an Agreement.
|
