A full security group redesign is happening either way. We’re multi-company, and each company was brought online years apart. Security evolved independently with very little coordination. I stepped in a few years ago and have been untangling it ever since. Thanks to y’all, I’ve got a structured plan for that.
What I’m really debating is the menu structure.
I’ve never been a fan of the base Epicor menu layout. It just isn’t aligned with how our companies actually operate. I’ve read plenty of things that suggest I’m not alone in that.
Moving to Cloud gives us a natural reset point. Users are going to be adapting anyway, so if there was ever a time to rethink it, this feels like it.
So the question is, is it worth the effort to rebuild the menu so it actually makes sense for how we run the business? What are the real pros and cons from those who’ve done it?
We went live on Kinetic cloud last year coming from E10. To prepare we had all department leads identify the menu options they currently use. Based on that we created Home Pages for each user account so most of the time they do not need to go to the Epicor menu. The homepages have multiple tabs/tiles that match the work flow process. We also adopted the practice of creating a new menu option for customizations so the base menu option remains available if there are any issues with the customization and especially after on-cadence upgrades.
A full menu security audit was also done at that time which included a test user account to test menu security that matched the security groups of active users. This approach worked for us.
That’s a really good point. I may be underestimating some of the context menu dependencies. My thought process was that we wouldn’t be recreating or deleting any Menu IDs, just reorganizing visibility and what users see in the main tree. The original menu items would still exist, just not necessarily exposed in the same layout.
Even with Quick Launch and favorites, I still see a lot of users navigating through the tree, so part of what I’m trying to do is clean up that. But it may not be worth it.
I think part of our challenge is that it’s been a bit of the wild, wild west over the years. With multiple locations and shared environment.
And like anywhere, people get used to having access to certain things, even if they don’t really need them anymore. So part of this effort is trying to bring some structure and clarity to that without disrupting operations.
Luckily we don’t have a ton of customizations yet, so that part will be easy, but this may be a better approach. Thank you.