Dynamics NAV Implementation in user security can be achieved by assigning different permission sets to users. Permissions can be assigned to the users according to their role.
A collection of database permissions for one or more objects in the Microsoft Dynamics NAV database that you can assign to one or more users is known as a Permission Set.
In this Dynamics NAV Implementation, we will be creating a user who will have access to Items, Customers and Sales Orders only. Everything is present in the UI will be hidden from this user.
Purpose of the Dynamics NAV Implementation in user Security Upgrade:
Our goal is to create the user with limited permissions. This user will have access to Items, the Customers and the Sales information.
- Create new permission sets which include access to only those objects i.e. tables, pages, reports, code units, etc. which the user has access to.
- A new user is created. The newly created permission sets are then assigned to this user.
- This will ensure the user does not have permissions to access any other tables, pages, reports or any other objects which are not specified in the above newly created permission sets.
- Now, the UI elements which the user does not have access to should not be visible to a user.
5. Microsoft Dynamics Navision can be configured to display and hide user interface elements based on the license or the user’s permissions to the underlying tables. All the elements, fields, actions, and the page parts can be removed from the user’s see of Microsoft Dynamics NAV.
6. License File And the User Permissions should be chosen for the UI Elements Removal field in the NAV Server Instance. This ensures the UI element is removed if the related object is not added in the license file and the user does not have permissions to the object as defined in the Access By Permission property for the related UI element.
7. To create the full use of the License File And the User Permissions option in the UI Elements Removal field, it is recommended that you assign a special permission set, Foundation, along with the relevant permission sets that define which app objects a user will access.
8. Access By the Permission property can be used to remove the element which should not be visible to a user. This Property Applies to Fields in tables, Fields on pages, Actions on pages, MenuSuite items, Page parts, such as a Lines FastTab.
9. To remove the UI element ‘Permission set’ from the visibility of the above-created sales user, go to MenuSuite. Navigate to the ‘Permission Sets’ under the General section of Administration in the MenuSuite.
10. Go to the properties of ‘Permission Sets’
11. Select the ‘Access By Permissions’ property. Choose the Assist-Edit button in the Value field.
The fields which are required to be selected are:
Object Type – Mention the type of object to which permission is required for the UI element to be visible.
Object ID – Mention the object to which permission is required for the UI element to be visible.
Read – Mention if Read permission is required for the UI element to be visible.
Insert – Mention if Insert permission is required for the UI element to be visible.
Modify – Mention if Modify permission is required for the UI element to be visible.
Delete – Mention if Delete permission is required for the UI element to be visible.
Execute – Mention if the Execute permission is required for the UI element to be visible.
Hence, The ‘Permission Sets’ will be visible to the user in the front end only if he has access to read the Permission Set table. In this scenario, the Permission sets will not be visible to the user.
In this Article, Dynamics NAV Implementation in user security is done by using UI elements removal feature and Access By Permissions property, UI elements can be hidden from the user’s visibility. Different permission sets can be created for the different users with limited permissions.