Restric User from Opening other Databases

najja
Member Posts: 67
Hello There,
This implementation has multiple databases and we would like to restrict the users to use only the database they are allocated for. We are providing the shortcut to users to open NAV which will have the database, company and other details supplied as command-line parameter. We do not want the user to use 'File --> Database --> Open' at all though they cannot open any database for which they do not have permission. Is there a way to enable/disable items on the Menu (not the Menu Suite, the usualy Menu which has File, Edit, View etc). I agree that smart users can modify the command line parameters if they know the exact name and details of the database.
Please let me know
Najja
This implementation has multiple databases and we would like to restrict the users to use only the database they are allocated for. We are providing the shortcut to users to open NAV which will have the database, company and other details supplied as command-line parameter. We do not want the user to use 'File --> Database --> Open' at all though they cannot open any database for which they do not have permission. Is there a way to enable/disable items on the Menu (not the Menu Suite, the usualy Menu which has File, Edit, View etc). I agree that smart users can modify the command line parameters if they know the exact name and details of the database.
Please let me know
Najja
0
Comments
-
Hi,
If you don't grant permission for the user to access other databases that they are not supposed to access, they won't be able to open it. They can only use the File-->Database-->Open to change database or comapany that they have permission to access.0 -
Hello Hawwa,
I totally agree here too when you said that. Infact I'd mentioned that in my query, atleast I'd thought of mentioning that. But my logic is not show the users any options which they cannot use, which will definitely make some of the curious users to dig into that. I was just wondering whether there is any workarounds
Najja0 -
It's been my experience that users don't go searching for what the program can do. They learn how to do their job and stick to the script. You'll always have a curious user or two, but when they see they don't have permission to go somewhere they'll stop trying to go there.
As far as I know the only way to limit the options in the File menu are through the System permissions for your roles, and there is not one for File --> Database --> Open. Probably because the same routine runs when you open your first database (the one the icon defaults to) and if you didn't have this permission you couldn't even do that.0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions