Security policies allow system administrators to apply access control to large numbers of documents without directly editing the ACL on each document.
Security policies, in conjunction with versioning states, allow a system administrator to configure the system to automatically modify ACLs on documents when their versioning state changes. For example, the administrator can configure the system to automatically grant access to a document to a wide audience when it is released.
Sequence tables detail the versioning states through which documents proceed following check in, check out, and other versioning actions.
To create a security policy, you run one of the security policy wizards provided by Administration Console for Content Platform Engine. The wizard creates a security policy that the system administrator can then customize by adding security templates. Once created, the security policy can be associated with documents, folders or custom objects. Alternatively, the administrator can make the security policy the default value for the security policy property for one or more classes. Making a specific security policy the default for a class ensures that all instances of the class are associated with that security policy unless the value is explicitly overridden.
Security policies can be exported and imported between object stores.