You’ve procured the technology, and your staff are trained. It’s time to establish who only sees part of the system, and who gets full access as this will affect the licenses you require. But how do you make such decisions?
One Size Doesn’t Fit All
While some roles are easier to define – those in senior management may well benefit from full access rights, while those who have a disparate set of responsibilities may only require access to particular areas. Therefore, a one-size-fits-all policy is less than optimal. It’s crucial you make sure each user’s rights reflect their real-world responsibility and that those who shouldn’t have access to sensitive customer information, don’t.
Here you’ll get an overview of how to define your ERP user access requirements. This handy guide is a great starting point and covers:
* An overview of light v full licencing
* Who to meet with, what to ask and why
* Cost V Benefit analysis
* Documenting and testing your requirements
Before you get started, we just need a few details from you. Then you’ll be on your way to planning your ERP user requirements:
[contact-form-7 404 "Not Found"]