However, if there is a specific need, there is nothing prohibiting someone from configuring each one differently. The security is applied to the two documents differently, even though the FPOS is common. Consider the case of a document on one ROS, declared as a record on an FPOS, versus a different document on a different ROS declared to the same FPOS. While you can have different security proxy types associated with different record object stores, this practice is not a suggested practice. The value is global to any one object store. The security proxy type is set on the document class definition of an ROS. If a record denies permissions to a user, this is ignored if that user is directly allowed that permission from the document security. If a hierarchical marking set is being used to limit access to a record, the document does not get that protection using inherited security proxy.Īlso, Content Engine security places a higher value on direct security than it does on inherited security.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |