I would rather look at expanding ACP restrictions in IP.Board to not show stuff you don't have access to.
Like Charles said, it is silly to creating a second control panel that does everything the ACP already does - that isn't to say though that there is not room for improving how the ACP presents itself to restricted users.
I just gave this more thought.
If ACP restrictions work - like do not show
the stuff users don't have access to - then effectively, you have created a 'second control panel' for IP.Nexus only - one that only deals with store stuff for users that I give these permissions/restrictions to.
So this would solve all the above.
But it has to work
I don't even want the users to have dashboard access - and right now, when they login, they get an error on first page, before they even access the IP.Nexus App.
A suggestion to solve this, is also to add a little feature to the Manage ACP Restrictions setup for a group/user - Add a field where you can also enter link for the default "open container" for ACP login.
The admin can enter the startup place for the user logging into ACP. So if I have made ACP restrictions to only allow use of IP.Nexus, then I set the "opening container" field to be http://mysite.com/ad...2d709&app=nexus
(or whatever it should be).
And I have said this a few times before - you guys make fantastic products. Please see all my comments, gripes and suggestions as an effort to bring positive feedback with the hope to improve on a already great suite of products.