A consultant configures Sales Insights so that a 'Deal Health' predictive card should appear only on opportunity forms and not on lead forms, per the client's request. After publishing the change, the card appears on both entities. Reviewing the Sales Insights settings app, what did the consultant most likely leave unchanged?
Select an answer to reveal the explanation.
Short Explanation
Insight cards in Sales Insights come with a scope setting that decides which tables they are allowed to show up on, and out of the box that scope is set wide open to everything the card supports, not narrowed down to just one table. If someone wants a card to live only on opportunities, somebody has to go in and dial that scope down on purpose, otherwise the card keeps showing up everywhere it is technically allowed to, leads included. That is exactly what happened here, the restriction request went in, but the actual scope setting never got touched. The wrong paths people reach for are tempting because they sound like real levers somewhere in the system, a security role, a language setting, a navigation menu entry, but none of them are the lever that controls which entities a given card is allowed to appear on.
Full Explanation
The correct answer is C. Predictive insight cards configured through the Sales Insights settings app are scoped per entity, and that scope defaults to applying across every supported entity unless an administrator explicitly restricts it to a specific table such as opportunity. Leaving the default scope in place means the card continues rendering on lead forms as well as opportunity forms, exactly matching the behavior described. Option A is incorrect because security roles control what data a user can access, not which entities a given predictive card is configured to display on; restricting a role would not change the card's own scope setting. Option B is incorrect because language settings affect how card text and labels are localized, not which tables the card is permitted to appear on. Option D is incorrect because the sitemap controls navigation areas and entries within an app's menu structure; it has no role in determining which forms a Sales Insights card renders on, and cards appear based on form and entity configuration rather than sitemap entries.