Answer
A useful exercise is walking through a single customer interaction end to end: a sales rep quotes a job, a service technician later handles a warranty claim on the same account, and a collections person follows up on an overdue invoice. Each of those people touches the same customer record but needs a different slice of it. The sales rep may not need to see internal service notes, the technician may not need pricing history, and collections may need visibility into both without edit rights to either. Licensing every user for the same full-access seat because it is simpler to configure usually costs more and creates unnecessary exposure to sensitive account data.
Buyers should also think about this alongside IBM i security practice rather than as a separate CRM-only decision. If the CRM pulls from Db2 for i tables or connects through an exit point, access on the CRM side should mirror the same principle of least privilege the team already applies to green-screen menu security and object authorities. Reviewing CRM roles annually, alongside the normal user profile and authority review, catches both stale access and mismatches between what a team was granted and what their current workflow actually requires.