If you get a new employee, your company's system administrator or IT pro has to add them to your Dynamics NAV. Then, you can assign them access to the relevant parts of the product based on their work area by assigning user groups and permissions.
Permission sets define which database objects, and thereby which UI elements, users have access to, and in which companies.
A permission set is a collection of permissions for specific objects in the database. All users must be assigned one or more permission sets before they can access Dynamics NAV. A number of predefined permission sets are provided by default. You can use these permission sets as already defined, modify the default permission sets, or create additional permission sets.
You can add users to user groups. This makes it easier to assign the same permission sets to multiple users.
Administrators can use the User Setup window to define periods of time during which specified users are able to post, and also specify if the system logs the amount of time users are logged on.
You can set up users groups to help you manage permission sets for groups of users in your company. You can use a function to copy all permission sets from an existing user group to your new user group. User group members are not copied.
In the New User Group Code field, specify the name of the new user group, and then choose the OK button.
As an alternative to copying, you can choose the New action to create a new line for an empty user group, which you then fill in manually.
If the default permission sets that are provided with Dynamics NAV are not sufficient or not appropriate for your organization, you can create new permission sets. And if the individual object permissions that define a permission set are not adequate, you can modify a permission set. You can create a permission set manually, or you can use a recording function that records your actions as you navigate through a scenario and then generates the required permission set.
On a new line, fill in the five fields for the different permission types as described in the following table.
Option | Description |
---|---|
Blank | Specifies that the permission type is not granted for the object. |
Yes | Specifies that the permission type is granted with direct access to the object. |
Indirect | Specifies that the permission type is granted with indirect access to the object. |
Indirect permission to a table means that you cannot open the table and read from it, but you can view the data in the table through another object, such as a page, that you have direct permission to access. For more information, see the “Example - Indirect Permission” section in this topic.
In the Security Filter field, enter a filter that you want to apply to the permission by selecting the field on which you want to limit a user's access.
For example, if you want to create a security filter so that a user can view only sales with a specific salesperson code, you choose the field number for the Salesperson Code field. Then, in the Field Filter field, you enter the value of the that you want to use to limit access. For example, to limit a user's access to only Annette Hill's sales, enter AH.
In the Permissions window, choose the Start action.
A recording process starts to capture all your actions in the user interface.
You can assign an indirect permission to use an object only through another object. For example, a user can have permission to run codeunit 80, Sales-Post. The Sales-Post codeunit performs many tasks, including modifying table 37, Sales Line. When the user posts a sales document, the Sales-Post codeunit, Dynamics NAV checks if the user has permission to modify the Sales Line table. If not, the codeunit cannot complete its tasks, and the user receives an error message. If so, the codeunit runs successfully.
However, the user does not need to have full access to the Sales Line table to run the codeunit. If the user has indirect permission to the Sales Line table, then the Sales-Post codeunit runs successfully. When a user has indirect permission, that user can only modify the Sales Line table by running the Sales-Post codeunit or another object that has permission to modify the Sales Line table. The user can only modify the Sales Line table when doing so from supported application areas. The user cannot run the feature inadvertently or maliciously by other methods.
Administrators can define periods of time during which specified users are able to post, and also specify if the system logs the amount of time users are logged on. Administrators can also assign responsibility centers to users.
Getting Ready for Doing Business
Setup and Administration in Dynamics NAV
Welcome to Dynamics NAV
Working with Dynamics NAV
Creating Microsoft Dynamics NAV Users
© 2017 Microsoft. All rights reserved.