Description for Objects in Setting Permissions

grapes123ca
Member Posts: 2
I am looking for descriptions/explanations of Objects, as we assign permissions for Table Data, so that we
don't inadvertently allow someone access to Table Data that shouldn't have that access. At the same time, we also don't want people bumping their heads on Permission barriers that frustrate them as the try to perform their job. For example, when we contemplate Object ID 79, Company Information, how do we determine what other objects require direct or indirect use of this Object in order to function? For Object ID 98, General Ledger Setup, which is included in the Basic User permissions, do non-financial employees really need this permission?
Is there a database somewhere that explains how each of the objects, as they relate to Table Data, work? Any help would be appreciated.
Thanks,
Craig
don't inadvertently allow someone access to Table Data that shouldn't have that access. At the same time, we also don't want people bumping their heads on Permission barriers that frustrate them as the try to perform their job. For example, when we contemplate Object ID 79, Company Information, how do we determine what other objects require direct or indirect use of this Object in order to function? For Object ID 98, General Ledger Setup, which is included in the Basic User permissions, do non-financial employees really need this permission?
Is there a database somewhere that explains how each of the objects, as they relate to Table Data, work? Any help would be appreciated.
Thanks,
Craig
0
Comments
-
There is a nice tool you can look at in the download section:
Navutilus AutoPermissions Demo v2.00
http://www.mibuso.com/dlinfo.asp?FileID=1196
Search the download section for "Role" or "Permission" for others0 -
If you will look how many tables are in NAV and e.g. you will take a look on the graph of relations between them (search for Big Picture of NAV), you will understand that describing something like this is too much. Setting permissions for this is hard too. You can go in two way - top-down or bottom-up. You can assign wider permissions and cut them up to the point you need, or assign tight permissions and add needed tables during the process when someone need some. You will never have accurate permissions on the first shot.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