Annotations are instances of the Annotation class. Therefore
they obtain initial security from the Default Instance Security ACL
of their class, like all objects do when first created.
Annotations have the following security characteristics:
- Each annotation is independently persistable and independently
secureable by its own ACL.
- Annotations are not versionable and are not automatically passed
from one version of an annotated document to the next version. In
order for the next version to include the same annotation as its previous
version, the annotation would have to be newly created for that document
version.
- The document or folder that has an annotation will be the security parent of the annotation if the
grantee has been set with an inheritable
depth. The permissions will appear on the annotation with a
source of inherited, which is normal in security parent
relationships.
- Just like document content, an annotation's content elements,
if there are any, are not independently securable and can only be
accessed through the annotation object itself. In effect, then, an
annotation's content has the same security as the annotation. In Administration Console for Content Platform Engine, an annotation's security
information appears on the Security page of its property sheet.
- If you are using Workplace or Workplace XT, be aware that these applications
limit permissions on annotations to the following simplified permission
levels: Owner Control, Modify Content, and View Content.
- Like other objects, annotations have an owner property.
An annotation owner need not be the same as the owner of the document
or folder that contains the annotation.
Table 1. Annotation access rights definedFull Control |
Modify Properties |
View Properties |
View Content |
All access rights listed in the columns to the right and: - Modify permissions
- Modify owner
- Delete
|
Modify property values |
View properties and security |
View content |