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?

The correct answer is to check whether the field security profile scoped to EMEA restricts read access to the predictive score field, since field-level security operates independently of the security role shared by both regions. Field security profiles operate on top of, and independently from, security roles: the field can be marked as secured, and then only users who are members of the 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; the field-level restriction on the predictive score field, applied only through the EMEA business unit's profile membership, explains why EMEA sellers cannot see the field their Americas counterparts see normally. The default currency configuration explanation 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. The Dataverse audit log retention explanation is incorrect because audit log retention controls how long historical change records are kept for auditing purposes; it has no relationship to whether the field displays on the form. The outdated Teams mobile app explanation is incorrect because form rendering issues tied to outdated mobile clients would typically affect functionality broadly rather than selectively hiding the specific secured field, and field security is enforced at the platform level regardless of client version.