After enabling predictive lead scoring across the organization, a sales operations analyst notices that sellers in the EMEA business unit cannot see the AI-generated lead score field on the lead form, while sellers in the Americas business unit see it without issue. Every seller, regardless of region, holds the identical Salesperson security role. What should the analyst check?
Select an answer to reveal the explanation.
Short Explanation
When two groups of sellers hold the exact same security role but see different things on the same form, the role is not the place to keep looking, something else independent of the role must be doing the hiding. Field-level security works exactly like that: it sits on top of the regular role-based permissions and can lock down one specific field for one specific group of people, even while everyone shares an identical role everywhere else. That is the pattern here, where one region can see a predictive score and the other cannot, despite matching roles. The wrong turns all reach for settings that sound technical but do not actually govern field visibility, currency formatting, audit history retention, and mobile app versions are each real settings that live somewhere in the platform, but none of them make a specific field disappear from a form for one group of otherwise-identical users.
Full Explanation
The correct answer is A. Field security profiles operate on top of, and independently from, security roles: a field can be marked as secured, and then only users who are members of a field security profile granting access to that specific field can see or edit it. Because every seller shares the identical Salesperson security role, the role itself is not the differentiator; a field-level restriction on the predictive score field, applied only through the EMEA business unit's profile membership, explains why EMEA sellers cannot see a field their Americas counterparts see normally. Option B is incorrect because predictive lead scores are numeric confidence values, not currency-typed fields, so base currency configuration has no bearing on whether the field renders. Option C is incorrect because audit log retention controls how long historical change records are kept for auditing purposes; it has no relationship to whether a field displays on a form. Option D is incorrect because form rendering issues tied to outdated mobile clients would typically affect functionality broadly rather than selectively hiding one specific secured field, and field security is enforced at the platform level regardless of client version.