HP System Dictionary/XL General Reference Manual Vol 1 (32256-90004)

5- 52
Sensitivity
Sensitivity is an attribute of an occurrence. It is set to one of three values when you create the occurrence,
and can be changed only by its owner scope or the DA scope. The three values are:
1 0 = Private sensitivity: Only the DA scope or the scope that owns the occurrence is allowed access
to it, unless the scope assigns access to other scopes through occurrence/scope associations.
2 1 = Public Read sensitivity: Any scope with at least read capability may read the occurrence. The
DA scope or owner scope can assign other scopes modify access to the occurrence through occur-
rence/scope associations.
3 2 = Public Modify sensitivity: Any scope with read capability may read the occurrence. Any scope
with at least create capability may read and modify the occurrence.
You should determine the sensitivity of an occurrence carefully. If you do not specify the sensitivity when
you create the occurrence, it defaults to the value specified in its attribute edit, or to private, if no attribute
edit exists. If you change the sensitivity from public to private, all scopes that previously had access to this
occurrence will no longer have access, unless that occurrence is explicitly associated with them.
Specific Restrictions
System Dictionary provides security that is specific to entities and security that is specific to relationships.
These are discussed here.
Only the DA scope or the owner scope can create or delete a synonym for an entity. Any scope with at least
read access to an entity can list all of an entity’s synonyms.
Only the DA scope or the owner scope can change the scope-owner and sensitivity attribute values of an
occurrence, even if other scopes have modify access to the occurrence.
NOTE Ifa scope deletes an entity it owns, thenall relationships involvingthat entity are also
deleted, even if the scope does not own or have access to all those relationships.
Example of Entity Security
The next two pages provide an example of how you could set up security for specific scopes and entities in
System Dictionary, and then modify them to increase the access of each scope.
You define Scope1 and Scope2 in the dictionary with create and read capability. You define Scope3 in the
dictionary with read capability. A user opens the dictionary with the scope Scope1. This user creates the
file File1 and the record Record1, both with sensitivity set to private, and element Element1 with
sensitivity set to public modify. Scope1 is the owner of these three entities. Only Scope1 or the DA scope
can delete these entities.
Another user opens the dictionary with Scope2. This user creates element Element2 with sensitivity set to
public read and element Element3 with sensitivity set to private. Scope2 is the owner of these entities.
Only Scope2 or the DA scope can delete these entities.
The table below lists each of the entities the scopes have access to at this point. Note that neither Scope2
nor Scope3 have access to File 1 or Record 1, and that Scope3 has at most have read access to an entity