Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Yvonne Jury]

Hi everyone,

Wanted to get some thoughts on handling user permissions during a NAV upgrade.  We are upgrading from NAV2015 to NAV2018.  I was advised to assign Super permissions to all users during testing, then lock down permissions at go-live rather than work through permissions errors during testing.  What are the pros and cons of the different approaches?

——————————
Yvonne Jury
Business Systems Analyst
Scheid Family Wines
Salinas CA
——————————

[Lewis Rosenberg]

?Permission errors can be frustrating to users and also system admins.  Users can develop a belief that software is not working properly when they do not understand the error messages.  I prefer to learn and resolve ALL issues during testing.  My preference would be to keep permissions as is and if permissions issues do arise, let your users know that there are new program objects that previous security permissions did not cover. Explain the error message to the users and try to show them how to unerstand what the error message means.

If possible, have your IT implementation team test as many processes as possible with the permissions of the users who will be performing them before you have users begin testing,.

——————————
Lewis Rosenberg
IT Manager
Mars Fishcare
Chalfont PA
————————————————————————
BCUG/NAVUG All-Star
BCUG/NAVUG Board of Advisors, Chairperson
BCUG/NAVUG Programming Committee

Twitter: @RosenbergL
LinkedIn: https://www.linkedin.com/in/rosenbergl
————————————————————————

NAVUG/BCUG Summit (navugsummit.com)
Orlando, FL – October 15-18, 2019
——————————
——————————————-

[Amanda Mayer]

I agree that permissions should be done prior to Go-Live, preferably during Power User training and testing. It allows the users to get comfortable with reading errors and understanding them. It also helps prevent the average end-user from receiving all the frustrating stops and starts during a time when they are already typically on edge.

——————————
Amanda Mayer
New View Strategies
Milwaukee WI
——————————
——————————————-

[Joseph Flynn]

?We are in the middle of this as well and chose to lock down permissions during testing / training.
Yes the users do see the permission errors pop up, but they have been thoroughly trained on what those errors mean.
They inform us immediately when they see them, which gives us the opportunity to correct the issue in a timely matter.
We have also enticed them with gift cards to the user who finds the most issues during each testing / training session.
It turns the negative affect into a positive one.

——————————
Joseph Flynn
Sr. Dynamics NAV Developer
Gold Star Foods INC
Ontario CA
——————————
——————————————-

[Kim Dallefeld]

If you wait to lock down permissions after testing but before go live, you will undoubtedly have issues at go live. The less issues at go live the better the acceptance by the user community. I definitely recommend having permissions set at testing, after all isn’t this part of testing?

love, love, love your idea of gift cards. Building excitement really helps with user buy in…pun intended!
?

——————————
Kim Dallefeld
Kim@Dallefeld.com
Dallefeld Consulting, LLC
Member of Dynamics Consulting Group
Ft. Worth, TX
2019 NAVUG Board of Advisors
Past NAVUG Board Chairman
NAVUG Programming Committee
——————————
——————————————-

[Brian Stenglein]

?We upgraded from 2013 to 2017 last fall.  There are a lot of object changes that will cause permission problems.

Here is what we did, it worked pretty well.

We selected a group of power users, one from each functional area of the system to work on testing.  I got a list of all the new objects added between 2013 and 2017 from our partner and set up a permission set with those objects and full permissions to them.  On a test DB I gave each of them testers this new permission set.  Then we utilized the permission recording feature and I had them each try to perform every function that they needed to while recording the permissions.  I created a new permission set for each department/functional area and put those recorded permissions inside and added those permission sets to those users.  I took away their full permissions to the new objects and had them test with the recorded permissions.  Some users found a thing or two that they forgot to do during the recording, but it was pretty minimal compared to what I think we would’ve faced without the recordings.

I would not be giving users Super permissions, access to payroll and G/L data that they should see.  I would definitely not leave their permissions as Super throughout all of testing and leave the pain for go live.  Take care of that during testing, whether you use the recording or just deal with individual errors.  You don’t want to be swamped with permission errors the day you go live. 

HTH,

——————————
Brian Stenglein
Clow Stamping Company
Merrifield MN
——————————
——————————————-