Each third party can have several contacts, and the contact model allows more than one of them to be designated as primary. The firm requirement is that every third party must have at least one primary contact, since that person receives assessments, can manage the team of additional contacts and delegate work in the Third-party Portal. Without a primary contact, assessment assignment has no accountable recipient.
The statement requiring one designated internal third-party manager is incorrect; internal ownership is handled through other roles and fields and is not a constraint on the contact count. The statements limiting a third party to a single primary contact are also incorrect, because multiple primaries are supported. Requiring at least one non-primary contact is not a rule either, since a third party can operate with only one primary contact.
When multiple primary contacts exist, the behavior for assigning an assessment depends on the assessment engine in use, which means implementers should test how assignments are distributed before go-live. Primary contacts can invite further contacts through Manage Team, and good practice is to maintain at least two primaries so that an absence does not stall an assessment.
[Reference: Study Guide – Core Configuration: Third-party Contacts and Primary Contact Requirements.]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit