FileNet P8 Platform, Version 5.2.1            

About templates

A security policy serves as a collection of security templates, each of which contains a predefined list of permissions, or Access Control Entries ACEs), that can be configured to apply to a document, custom object, or folder.

Except where specifically mentioned, this topic describes the association of security policies with documents and document classes. To fully understand this topic, you should be familiar with document versioning and the versioning states Released, In Process, Reservation, and Superseded.

Remember: Security policies are just one way to apply ACEs to an object's ACL. The other sources are the object's class, a security parent, direct edits to the object's security, and by programmatically setting the object's access rights.

There are two kinds of security templates:

A security template applies to a document version if (1) the document version has an associated security policy, and (2) the associated security policy has a template for the document's version state. For example, if the document goes into the Released versioning state, and the security policy has a Released template, then the permissions listed in the Released template apply.

Templates cannot be shared between security policies and cannot be independently loaded or saved apart from their security policy. Permissions on an object that originate from a security policy will appear on the object's ACL with a Source type of Template. As such they cannot be directly edited using the Administration Console for Content Platform Engine Access Control Editor or by using the FileNet P8 API.

Newly created security templates contain no default permissions placed on them by the Content Platform Engine. Administrators can add permissions at creation time while running the security policy wizard, or at any later time. Applying a template that contains no permissions to an object will have the effect of removing any existing permissions on that object that were previously applied by a security policy.



Last updated: October 2015
p8psa015.htm

© Copyright IBM Corporation 2015.