Limited Users in NAV 2016

I suppose the most of you have already used Limited Users. It is pretty good possibility to save some money for users who have not a lot different processes to work in NAV. But limitation was a big; you could insert in only 3 tables by your need and in 80 additional by default. It was enough for some basics processes (creating contacts, HR, warehouse and similar).

But from NAV 2016, we have a pretty greater possibilities. That means we can use for inserting even 151 default tables; you can find completely list here. Some of the most important default tables for insert are:

  • Customers and Vendors
  • Customer and Vendor Invoice Discounts
  • Sales and Purchase Headers and Lines
  • Deferrals
  • Sales/Puchase Price and Line Discount
  • Assembly Order Headers and Lines
  • Incoming Documents
  • Workflow tables

You can see that with these tables in combination with three additional by your needs, we can use Limited Users for a lot different processes. It can decrease project cost and improve quality.



12 thoughts on “Limited Users in NAV 2016

    • You are in right about this, but system works on other way. System counts the first three tables you inserted in them. After you log out from NAV, you can log in again and use some other three tables for inserting. System counts these three tables per session.


      • Yes, I know this is how the system currently works, and I find it potentially alarming, because with this user driven randomness the administrator has insufficient control with the write permissions in the system. An organization may have a host of Limited Users running lose and writing to whichever tables they choose, excluding, of course, those that are “Excluded”. Do you agree that this is a deficiency and that it is very important to fix it?

        Liked by 1 person

      • I’m not sure. You can add read rights to all these user, but insert and modify to only three tables you want. This will solve your needs.

        Liked by 1 person

      • You would then also have to add even the large collection of “included tables” in the permission set, and it is exactly this task that should be automated by the program, offering a simple setup where the admin could specify the three extra tables only. (The admin should not have to maintain this permission set as the collection of included tables changes.)


      • I can agree with you. But everything is based on someone perception. You have workaround solution and I’m not sure that MS will change something as this. This was not their initial idea.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.