During a Financial Services Cloud implementation at an insurance company, a consultant needs to design...

The broker organization should be represented by an Account, while each individual broker is represented as a Contact associated with that organization. This preserves the distinction between the business entity and the individual professionals who operate within it and allows each broker to receive individually controlled portal access.

The assistant should likewise be modeled as a Contact. Where an assistant works across multiple broker relationships, Salesforce ' s Contacts to Multiple Accounts architecture provides a scalable way to represent those associations without duplicating the Contact record. The model maintains one Contact as the authoritative individual record while using relationship records to connect that Contact to additional relevant Account relationships.

This structure is preferable to creating separate Account-and-Contact pairs for every individual broker because it would unnecessarily duplicate business entities and complicate relationship management. A Contact-to-Contact relationship can describe interpersonal relationships but does not provide the same account-based affiliation model required where one person participates across multiple broker organizations or account contexts.

Record access for portal users is handled separately through Experience Cloud sharing and security controls. Modeling brokers individually as Contacts does not require brokers to see one another ' s information. The sharing architecture can restrict users to their own records and specifically authorized relationships.

The Account-plus-Contact approach therefore best satisfies the required broker and assistant data model.