A client's Dynamics 365 Sales administrator wants sellers to view the predictive score and grade on each lead, but wants only the sales operations team to be able to adjust the scoring model's configuration, such as which fields are included as predictors. A consultant is asked how to structure this. What should the consultant recommend?

The recommended approach is to give sellers a security role that includes read access to the lead entity and its insights, while reserving the AI model configuration privileges, which are customization-level access, for the sales operations team's role. Viewing a lead's predictive score and grade only requires read access to the lead record and its AI insights, while changing which fields the model uses as predictors is a configuration action that should be limited through security roles to the sales operations team, keeping day-to-day visibility separate from the ability to alter how the model itself works. The option granting every user the System Administrator role is incorrect because predictive scoring configuration privileges can and should be scoped through normal security roles; granting System Administrator to every user is unnecessary and removes any meaningful separation of duties. The option disabling predictive scoring for all sellers and re-enabling it only when sales operations needs to review a lead is incorrect because it would strip sellers of the score and grade they need for daily prioritization, which is the opposite of what the client wants. The option moving the scoring model settings into a separate Dynamics 365 environment that only sales operations can sign into is incorrect because it adds unnecessary complexity and would disconnect the model from the production lead data it needs to train and score against; environment separation is not how Dynamics 365 Sales scopes configuration access, security roles are.