Monday, September 29, 2014
Dynamics GP Support Debugging Tool’s Security Profiler
Posted by Katja Brinck
Who has access to that window? Learn how to use the Dynamics GP Support Debugging Tool Security Profiler to find out.Whether you are going through a security audit or just want to make sure certain key windows are restricted properly, it can be overwhelming to figure out who has access to a specific window. While the role-based security of Microsoft Dynamics GP makes setting up security more streamlined than the old method of adding/removing security one window at a time, it can still be challenging to use the out-of-the-box security reports to answer the question: “Who has access to that window?”
For example, if your company uses EFT and stores customer or vendor banking information in GP, the EFT Bank Maintenance window is one that should be restricted to only a few users, since this may include confidential banking information. If you wanted to run the security reports to determine who has access, you would probably need to run a combination of the Security Task Setup report, the Security Role Setup report, the Security Task Assignment report, and the Security Role Assignment report. Then after printing out pages and pages (depending on the number of users, companies and roles), you would have some idea of which tasks/roles include this window, and which users have these tasks/roles assigned to them. But it’s not an easy way to get the answer.
My favorite way to find out who has access to a specific window is to use the Support Debugging Tool, which is free and supported for GP versions 2013, 2010, and 10. It is available for download at the SupportDebuggingToolPortal (using your PartnerSource or CustomerSource credentials).
Here is how you can easily use the Support Debugging Tool to figure out the answer:
- Log in as an administrator, power user, or user with access to the window you would like to profile, since you need to access it in order to use this particular tool. (Also make sure this user has been granted the MBS DEBUGGER USER or MBS DEBUGGER ADMIN security role.)
- Go to Microsoft Dynamics GP > Tools > Support Debugging Tool
- Click the “Options – Select additional feature” dropdown, and then select “Security Profiler.”
- This will bring up a blank Security Profiler window.
- Minimize the window (don’t close it) and open up the window that you want to investigate to see who has access. In my example, I’m opening up the Customer EFT Bank Maintenance window. The window does not necessarily have to be populated for the Security Profiler to work.
- Return to the Security Profiler window; it should now show the windows that you have opened. Highlight the window you would like to view security for, and then click the “Security” button.
- The Security Information window will open. On the left-hand pane under “System Level,” expand the task(s) that contain the selected window. This will show which role(s) have this task assigned to them. On the right-hand pane, change the View option to “by Security Role.” Then you can expand the Security Role(s) to see which users are in that role and therefore have access to the window you just profiled.
- Now you can use this information to report back to your auditors or clean up security if you determine there are users who have access to this window that do not need it.
This is just one of the many features available in the Support Debugging Tool, which we recommend installing for all of our clients. For assistance with installing or using the tool, please feel free to reach out to Armanino! Stay tuned for future posts about other awesome features available in the Dynamics GP Support Debugging Tool.
Katja has over 12 years of consulting experience implementing and supporting Microsoft Dynamics GP, FRx, and Management Reporter. Her specialties include solution design, application build, reporting, integrations, user testing and documentation. Katja holds a Bachelor of Arts degree in Political Science from Colgate University.