The following example illustrates how to set up a superuser. You can use the same procedure to create database logins for other users. Users that have been given a database login must use database authentication to gain access to the database.
Click Tools, Security, Database Logins and the Database Logins window appears.
In the User ID field, enter the user ID - in this case SUPERUSER. You can type uppercase and lowercase letters as you like - the program will convert all letters to uppercase. You can later change the user ID in this field.
In the Name field, enter the name of the user to whom this ID belongs.
In the Password field, you must enter a password. It is encrypted as you type. It is important to remember where you have used uppercase and lowercase letters because passwords are case-sensitive.
In the Expiration Date: You can enter a final date on which a user will be able to log on to the program. As a security precaution, superusers should not be given a date limitation.
The password can be used for as long as you want. In a multiuser installation, however, where a system manager has set up all the user IDs, each user should change his or her own password immediately after logging on for the first time so that no one else knows the password. Your password cannot be seen anywhere in the system.
The Microsoft Dynamics NAV security system is initiated when you create the first login. The first login should therefore be for a superuser who is given the SUPER role in Microsoft Dynamics NAV. The superuser then owns and administers all access to this database from within Microsoft Dynamics NAV. Until you create a superuser, any user with access to the system can carry out any transactions they want to in a Microsoft Dynamics NAV database.
One of the first things that the superuser should do is create user IDs for the other people who will have access to the database and assign roles to these users. Permissions are allocated at company level in Microsoft Dynamics NAV.
Creating Database Logins on SQL Server
Creating Windows Logins
Giving Database Logins a Role