We have a variety of different users in our organisation and we net good security in NAV. Looking at the delivered User Groups and Permission Sets, it's not always apparent their purpose and there are some issues, for example, Basic Perm. Set gives Read access to Customer data, which not all staff should be able to do.
I am experimenting with the delivered Permission Sets but finding issues along the way -eg. the "D365 BASIC" combined with "D365 PURCH DOC, EDIT" does not allow you to modify a Purchase Order because TableData 1853 does not have read access! So then i created an addition Permission Set to start fixing whatever errors I find, but started to think is there a better way.
I wonder whether i should just start with a desired profile, eg. "Purchasing Agent" and build the permission sets from there, using the error messages i encounter along the way until i get the profile fully operational. Or keep going as i am using the delivered Permission Sets and incrementally adding whatever is missing to my own set. The only problem with this is if i find a table i don't want access to, i need to clone the NAV permission set and remove it from the clone. I don't want to modify the delivered Permission Sets.
Would love to hear from anyone whose been through this process and has any recommendations.
*This post is locked for comments
I have the same question (0)
