Do you think we should target to create a unique Customers and Employees application? Instead of having employees servicing applications that are different from the ones used by the customers, would it be a better idea to provide everyone with 'almost' the same application? For example, as a bank, we have an online banking application/website but branch advisors are using completely different tools. Any thoughts on this?
Sort By:
Oldest
IT Strategist in Governmenta year ago
It really depends on the industry and types of services provided by the application(s).. One size does not fit all here, in my opinion.Sr Director of Engineeringa year ago
If the concern is that employees won't be able to walk customers through a process because they see something different, then there can be a benefit to having a single application with perhaps some different menus or a toggle to allow employees to perform other actions. However, doing so means that your application RBAC and design will need to really focus on security because a bad actor now has access as a 'customer' and just has to figure out how to reveal the 'employee' version to do something malicious. Personally, I'd keep them separate and just train my employees on the customer version / and perhaps give them dummy accounts to practice with. That will keep the security concerns separate.