We addressed this for editor-level and fulfilment-level users by creating a standard DNN page/menu item that was a link to the pages we gave them rights to (such as the Orders) section. We instructed them to use those links to get to the Hotcakes admin sections that they had rights to.

By default, the control panel only shows to end users that have permissions for the control panel to be displayed. This is not a Hotcakes-specific feature, but a DNN one. The permissions you set in Hotcakes do work, but they don't have any effect on the control panel.

As Moore Creative pointed out, you'll need to implement a workaround for end users that don't have page/site edit permissions on the DNN side. This is most often achieved by adding a permission-based module on the site that has a link to the store administration.

We have the same issue on an upgraded site and the behaviour of the menu seems incorrect as HC v1.x used to work fine. It's hard to explain to the customer that they can't use the store admin area directly and instead have to use another page/menu with links directly to the store admin pages they use on a daily basis.

Is there a way we can change the menu behaviour?

[quote=Pure Systems;1245]We have the same issue on an upgraded site and the behaviour of the menu seems incorrect as HC v1.x used to work fine. It's hard to explain to the customer that they can't use the store admin area directly and instead have to use another page/menu with links directly to the store admin pages they use on a daily basis.

Is there a way we can change the menu behaviour?[/quote]

The change in behavior is not something that any developer can control. It's a fundamental change in how DNN is administrated overall. This will not be the only difference that some end-users will need to become acquainted with. There is little we can do to change the behavior of the persona bar to function like the control panel - unless we fork the persona bar, which we're not likely to do.

The most common workarounds we've seen and deployed ourselves include:

- Creating and adding a permission-aware theme object that's added to the theme
- Adding a permission-aware page to the menu that is only shown to end-users that have the appropriate permissions