Vote to Fix Security for GP Self-Service user type!

There has been a few GPUG forum posts and discussion on the community regarding the GP security issues around the new user type SELF-SERVICE that was introduced with the release of GP 2015 R2 (there was only a FULL user type, and LIMITED was added in 2013R2).

Now, as Microsoft has been encouraging companies to use the Web Client and since the Self Service user license is much cheaper than a Full license, it makes sense to use them as much as possible, especially in combination with the new Workflow options that were added in recent releases for Requisitions and Purchase orders (aside of many others).

The big problem comes when a “Self Service” user is leaving for an absence and needs to put someone else in charge of approving his/her workflows, something that is done in the ‘User Preferences’ window in GP by clicking on the ad-hoc button at the bottom of the form:  Home >> User Preferences >> Workflow Delegation button

An error message would promptly come up to deny the user access to the User Preferences form, leaving them out of any other options to delegate someone their WF approvals.

ScreenCap 2018-11-01_191133

The problem has been acknowledged by Microsoft’s technical support, but there hasn’t been enough push to get this changed in the past, and the old suggestion ticket from the defunct ‘Connect’ site got lost in the transition to the new ‘Suggestion’ site that Microsoft put up this year after retiring MS-Connect..

I’ve put up a new suggestion ticket to get this GP security fixed so all types of users could access the ‘User Preferences’ form and by definition, the Workflow Delegation..

And while we are at it, the Self Service users are also prevented to do any changes in the menu bar of GP.. they can only show or hide existing menus, but if they try to click on ‘Customize.. ‘ to open the ‘Customize Toolbar’ form, they receive a similar access denial as above.

ScreenCap 2018-11-01_191143

So please go out and vote for this suggestion to raise awareness about this bug and have it fixed by an upcoming release..


Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Website Powered by

Up ↑

The personal blog of Mark Polino

Erik Svensen - Blog about Power BI, Power Apps, Power Query

Blog about Power BI, Power Apps and Flow

Freddys blog

Learn something new... - then Teach someone!

Life Hacks 365

Microsoft Dynamics & Microsoft Office Tips & Tricks

Vicky Rodgers - Microsoft Dynamics 365

Everything Microsoft Dynamics 365 for Customer Engagement


Stuff about the Microsoft Power Platform and Dynamics 365

The Dynamics Explorer

Exploring the World of Microsoft Dynamics ERP

Paul S. Randal

My contribution to the never ending Dynamics GP journey

%d bloggers like this: