You can use the Permission system table to define what different user roles are allowed to do. Permissions are specified for objects; so you can specify the exact set of permissions per table, form, codeunit, and so on. You can specify that a user role has no permissions (blank field), Full (Yes), or Indirect permissions to perform the following actions:
-
Read
-
Create/Insert
-
Modify
-
Delete
-
Execute
Setting the ObjectID to 0 applies the permissions for the role to all objects of the specified object type. For example, the ALL role in the Microsoft Dynamics NAV 2009 demo database company CRONUS has the permission Execute for the object type Codeunit and object ID 0. This means that the ALL role gives permission to execute all codeunits.
The Security Filter column is used to limit access by a role to fields in a table.
