Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Simple security manager

Log in to subscribe to topics and get notified when content changes.

Simple security manager

The simple security manager protects fields via their dictionary entries.

Note: Functionality described here requires the Admin role.

To secure a field, bring up that field's dictionary entry and add read/write/delete roles to the field. Row level operations (like insert or delete) are implemented by putting roles on the table's sys_dictionary entry.

Since the simple security manager is based on fields themselves, it has no concept of, or interaction with, the system's table hierarchy. If a field is defined on task, it is secured identically whether that field is actually part of an incident, a change, or a problem.