Individual users belong to one or more user roles and share the same characteristics and permissions. For example, one user role may have read and write access to a particular field, while another role may only be able to view the same field. Another user role may not even be able to see the field.
All fields, menus and screens have security permission keys to protect the object. For example, a security key exists for accessing the security module itself. Another security key exists for the product menu item on the Administration screen. Another example is that a security key exists to control access to the description field. All of the fields that are visible can be turned on or off based on user role privileges. There are literally hundreds of security keys within ExtraView, and each time you create a new user-defined field, two new security keys are automatically created to allow you to protect the newly created object. These two keys allow you to control access to the field when adding a new item to the database and to control access to the field when either updating or reporting.
The Grant Security Privileges section controls all these accessibility features in your version of ExtraView. In a matrix view, the intersection of the security key and the user role is a read and write switch. Therefore, for every item that has a defined security key, you can allow or prohibit any user role to access that feature.