A consultant configures relationship insights so an account team can see which stakeholders are actively engaged on a strategic opportunity. After rollout, a rep on the account team reports that a stakeholder's title and engagement history are visible to some teammates but blank for others viewing the same opportunity record. What is the most likely cause?
Select an answer to reveal the explanation.
Short Explanation
When the exact same insight looks different depending on who's looking at it, that's a strong sign the underlying record has some fields locked down for certain people, not that the AI feature is behaving inconsistently. Relationship insights isn't computing something fresh and private for each person based on their own history with that stakeholder, it's presenting information drawn from a shared underlying contact record, and it plays by whatever field-level rules already apply to that record. So if someone's security profile blocks them from seeing a contact's title or engagement history directly, that same block carries over into what the insight shows them. It's not a sync delay that will fix itself overnight, and it's not tied to who owns the opportunity. It's simply the CRM's existing field-level permissions doing exactly what they were configured to do, just showing up somewhere the rep didn't expect to notice it.
Full Explanation
The correct answer is C. Relationship insights surfaces engagement patterns and contact details it derives from underlying Dataverse records, and it honors the same field-level security profiles applied to those records. If certain fields on the contact, such as title or engagement history, are restricted for some team members through field-level security, those fields will appear blank to them even though the insight itself was calculated correctly, while teammates with broader field access see the full picture. Option A is incorrect because relationship insights is not a personalized calculation per viewer's own call history; it draws on the account team's shared captured data, not a private view. Option B is incorrect because there is no indexing delay mechanism described here that would explain a permanent, consistent blank field for specific users rather than a temporary one for everyone. Option D is incorrect because visibility is not restricted to the opportunity owner; multiple account team members can see relationship insights, and ownership is not the access control at play, field-level security is.