Permission System Table
[This topic is prerelease documentation and is subject to change in future releases. Blank topics are included as placeholders. There may be some display and formatting issues until the look and feel is finalized.]
You can use the Permission system table to define what different user permission sets are allowed to do. Permissions are specified for objects; so you can specify the exact set of permissions per table, page, codeunit, and so on. You can specify that a user permission set has no permissions (blank field), Full (Yes), or Indirect permissions to perform the following actions:
Read
Create/Insert
Modify
Delete
Execute
The following illustration shows the Permission system table.
.jpg "Dd338714.b263412c-f1ea-4775-b1dd-192f3985fba1(en-us,NAV.70).jpg")
Setting the ObjectID to 0 applies the permissions for the permission set to all objects of the specified object type. For example, the ALL permission set in the Microsoft Dynamics NAV 2013 demo database company CRONUS has the permission Execute for the object type Codeunit and object ID 0. This means that the ALL permission set gives permission to execute all codeunits.
The Security Filter column is used to limit access by a permission set to fields in a table.