Role Based Security Model in Dynamics GP 10.0

May 11
08:54

2010

Andrew Karasev

Andrew Karasev

  • Share this article on Facebook
  • Share this article on Twitter
  • Share this article on Linkedin

Microsoft Dynamics GP Security Model, Introduced In Version 10.0

mediaimage
There was and probably still is some confuse among Dynamics GP consultants (especially with old Great Plains certifications) about new GP Security Model,Role Based Security Model in Dynamics GP 10.0 Articles introduced with version 10.0.  New model also should be understood by Great Plains Dexterity programmer, coding add-ons in Dex for Dynamics GP, as in order to enable customization for non Power User GP role, they have to follow new security setup procedures.  You should refer to Dynamics GP Administrator Guide for detailed procedures, and this publication for introduction session only:
1. Power User role.  If you have to just begin using Dynamics GP 10 or 2010 within small group of GP users, where real security is not a concern, you can mark each user as having Power User role in Dynamics GP -> Setup -> System -> User Roles, then pick the user, company and mark POWERUSER checkbox.  Power User will have access to everything in GP, including Dexterity compliant Dynamics ISV add-ons windows
2. Alternate Modified Forms and Reports.  This is where you control the type ID to have access to Modified Reports (Report Writer, such as Modified SOP Blank Invoice form with your company logo), Modifier with VBA and Dexterity New and Alternate Forms (for Dynamics GP Add-ons).  If all your users should have similar access to modified forms and reports, you may just alter DEFAULTUSER ID, if not – ad new IDs for specific user groups
3. How to add non Power User access to Dynamics ISV Add-on product?  Here you first create one or several tasks, where you select your Custom Product, Series and then mark appropriate Windows, Reports and Files for access in this specific task (this part is very similar to old security model in Great Plains Dynamics up to version 9.0 inclusively).  Second you either add the task or tasks created on the first step to one or several Security Roles, or create new Security Role(s).  And finally, if you decided to create new Security Roles, assign them to appropriate user in Dynamics GP
4. Upgrading Dynamics GP to version 10 or 2010 and security.  What upgrade does (assuming that you are following upgrade path and applying recommended service packs) – it creates separate Security Role for each user in new version 10.0 or 11 (looks like it is renamed into Dynamics GP 2010).  Obviously this is Ok for begin working in new version, however for new Users you would like to use standard roles, such as AP Clerk, Accounting Manager, etc.
5. If you feel that Security is still a concern and you need training and help with Security model rehaul, feel free to call us 1-866-528-0577, 1-630-961-5918 or email us help@albaspectrum.com  One consultants speak English, Spanish, Arabic, Portuguese, Russian, Chinese to facilitate implementation in the international environment