Interest Tags enable Financial Services users to categorize customer interests and associate those interests with supported records, including Interaction Summaries. Access is controlled through specific Financial Services permissions rather than being universally included in every Financial Services permission set.

Salesforce identifies Financial Services Cloud Extension and Financial Services Cloud Foundations as permission sets that provide the relevant Interest Tags capabilities. Current Salesforce documentation lists these permission sets among those used in Financial Services for access to Interest Tags functionality.

Salesforce also states that users who add Interest Tags to Interaction Summaries require appropriate Financial Services access, including Financial Services Cloud Extension or Financial Services Cloud Foundations, depending on the product configuration. Before users can work with the feature, administrators must also enable Topics and Interest Tags and configure the relevant object for Topics.

Cloning one of these permission sets provides an appropriate baseline when an organization needs a specialized permission set while retaining the required Interest Tags permission. The Financial Services Cloud Standard and Basic permission sets serve other user-access patterns and do not constitute the specified source permission sets for this capability. Therefore, Extension and Foundations are the appropriate permission-set templates.

The appropriate configuration point is the Role field on the Financial Account Role object. Financial Account Role represents the relationship between a financial account and a person, contact, or account. Examples include primary owner, joint owner, beneficiary, trustee, or another organization-specific participation role.

Salesforce ' s Financial Services data model represents these relationships through the Financial Account Role structure. Current standard data-model mapping carries the same concept into Financial Account Party, where the managed-package Role field maps directly to the standard Role picklist. This confirms that role classification belongs on the relationship record rather than on the Financial Account itself.

A Joint Owner or Primary Owner relationship should therefore not be modeled by creating new values or fields directly on Financial Account. The relationship object is specifically designed to support multiple parties and multiple relationship types for the same financial account. Account-Account Relationship addresses relationships between accounts or business entities and is unrelated to financial-account ownership or participation.

Accordingly, when additional customer-to-financial-account relationship categories are required, administrators should extend the Role picklist on Financial Account Role. This preserves the Financial Services relationship model and supports consistent ownership, reporting, rollups, and financial-account relationship processing.

Agentforce Financial Services allows administrators to replace the default icons used for specific Life Event and Business Milestone types with organization-specific icons. The configuration is performed from the dedicated Financial Services icon-management setup area for Events and Milestones.

From that setup experience, the administrator selects the event or milestone icon that needs to be changed, chooses the appropriate change-icon action, and uploads the replacement SVG file. This allows the visual representation of events and milestones to align with the institution ' s terminology and user-experience standards.

The icon is not configured directly within Lightning App Builder or the Lightning page layout. Those interfaces control where the Events and Milestones component appears but do not maintain the icon assigned to each event or milestone type. Likewise, administrators do not simply upload an icon as a generic Static Resource and expect the Events and Milestones component to associate it automatically.

Custom icons improve rapid visual recognition when advisors review a customer ' s timeline—for example, distinguishing a marriage, home purchase, retirement event, business expansion, acquisition, or another milestone. Therefore, the appropriate location is the dedicated Financial Services Icons area for Life Events and Business Milestones.

Financial Account Management provides the Agentforce Financial Services data model and user experience used to represent and manage customers ' financial-product relationships. A Financial Account can represent a checking or savings account, investment account, credit card, mortgage, loan, or another financial product. Related objects can represent account parties, balances, addresses, transactions, and associated information.

Salesforce ' s Financial Services architecture provides Financial Account and associated objects specifically to model financial accounts and their related information. Administrators provide appropriate permissions to advisors, personal bankers, integration users, or other personas that require access.

Financial Services also provides Financial Account Summary experiences on the customer ' s Account page. Advisors can use them to view financial account details and related information in the context of the client relationship. This creates the consolidated account-level visibility financial advisors need for servicing and relationship management.

Performance reporting analyzes business results but is not the underlying client-account management capability. Client onboarding handles customer acquisition and setup processes. Opportunity management addresses potential sales or revenue-generating activities rather than established client financial products.

Therefore, Financial Account Management is the feature directly responsible for representing, tracking, and servicing customers ' financial accounts.

Actionable Relationship Center supports object-specific related lists so users can inspect relevant information without leaving the relationship graph. For the Account object, supported lists include Client Financial Goals, Household Financial Accounts, and Cases, making A, C, and D correct.

Salesforce ' s ARC documentation lists supported Account-related lists that include Household Financial Accounts, Household Financial Goals, Household Opportunities, Household Referrals, Financial Account Primary Owner, Client Financial Goals, Household Assets and Liabilities, Client Assets and Liabilities, Related Leads, Opportunities, and Cases.

The distinction between Account and other ARC-supported objects is important. Financial Holdings appears as a related-list option for the Financial Account object, not Account. Similarly, Notes and Attachments is supported for objects such as Contact, Lead or Referral, Opportunity, Asset and Liability, and Financial Holding, but it is not listed among the supported Account related lists in the ARC configuration matrix.

ARC can display up to ten related lists that have appropriate compact-layout configuration, and their display order follows the associated object ' s page-layout arrangement. This allows financial advisors to move from a high-level relationship visualization directly into relevant client financial goals, household account holdings, service cases, and other supported records.

Mortgage functionality in Agentforce Financial Services is controlled through the appropriate permission-set and user-access configuration. A user who must create or work with Residential Loan Application records needs access to the mortgage feature and to the mortgage-related objects. Consequently, failure to assign the required Mortgage permissions prevents the consultant from creating the application record.

Salesforce ' s Financial Services setup guidance includes assigning the Mortgage permission set as part of granting users access to mortgage functionality. Salesforce also provides enhanced mortgage permission-set configurations for personas such as loan officers and underwriters.

Current configuration guidance shows that mortgage-oriented permission sets must grant the system permission that licenses the user to access mortgage functionality in Financial Services and must provide the necessary object permissions for Residential Loan Applications and related Loan Applicant and Loan Application objects.

The issue is therefore not resolved by enabling a Residential Loan Application flow or by selecting a user-level Mortgage User checkbox. Nor is there a general Allow Mortgage Access setup switch corresponding to the required user entitlement. Access is established through the prescribed mortgage permissions and associated object-level access.

Organization-Wide Defaults establish the baseline record visibility for users who otherwise have the required object-level permissions. To make Person Account records broadly visible, the Account or Person Account sharing model should provide Public Read Only access. Public Read Only allows all applicable users to view and report on records while reserving editing rights for users who receive additional access.

Financial Accounts contain sensitive financial information, so their baseline sharing should instead be Private. With Private sharing, users do not automatically gain access merely because they can access the Financial Account object. Access can subsequently be expanded only to authorized users through record ownership, role hierarchy where appropriate, sharing rules, manual sharing, Compliant Data Sharing, or another approved mechanism.

Setting Financial Accounts to Public Read Only would expose them broadly and directly contradict the stated privacy requirement. Likewise, removing a Financial Accounts tab or component from a Lightning page is not a security mechanism. A user who retains record access could still potentially retrieve the information through reports, search, APIs, related lists, or another Salesforce interface.

Therefore, the appropriate record-level model is Public Read Only for Person Accounts and Private for Financial Accounts, followed by selective access grants for authorized Financial Account users.

Salesforce Insurance Claims Management supports the complete post-loss claims lifecycle, including reserve management, payment processing, and automated adjudication. These processes operate after a covered loss has occurred and are central to evaluating, funding, and settling a claim.

Reserve Management enables adjusters to establish and modify reserves representing expected future claim exposure. The claim workspace consolidates coverages, reserves, loss items, expense items, and other claim financial information so adjusters can assess current and projected financial exposure.

Payment is another core Claims Management process. Adjusters can create payment details and issue payments while Salesforce validates applicable policy limits and updates the corresponding claim-financial records.

Auto Adjudication applies configured rules and policy information to automate claim-processing decisions where appropriate. This reduces manual handling for qualifying claims and supports straight-through processing.

Quoting belongs to the pre-policy acquisition process, while underwriting evaluates risk before coverage is issued. Those functions are part of other insurance lifecycle capabilities rather than Claims Management. Claims Management therefore centers on Reserve Management, Payment, and Auto Adjudication.

This design requires objects that represent participation in the interaction, sharing of the interaction summary, and participation in the financial deal.

Interaction Participant associates internal users or groups with an Interaction. This enables engagement records to reflect which internal stakeholders participated in the client interaction and provides the connection between the interaction and the involved users or groups.

Interaction Summary Participant controls access to the detailed interaction notes. Salesforce allows an Interaction Summary to be shared with a specific user or group by adding that user or group through the Interaction Summary Participants related list. Compliant Data Sharing must be enabled for Interaction Summary to use this participant-based model.

Financial Deal Participant performs the corresponding function at the deal level. Financial Deal records can be shared with users or groups by adding them as participants, allowing specialists from another line of business to receive controlled access to the relevant transaction.

These objects work together effectively: the Interaction captures the engagement, the Interaction Summary contains the detailed notes, and the Financial Deal represents the underlying transaction. Participant records provide controlled association and sharing across these layers without broadly exposing sensitive information to unrelated users.

The household and the client ' s business are both represented as account-based entities. The client ' s household is modeled using an Account with the Household classification or record type, while Smith ' s Shoes is modeled as a Business Account. The relationship between those two account entities is represented using the Account-Account Relationship model.

Salesforce ' s Financial Services relationship architecture supports organizing customers into households while connecting those households with related businesses and organizations. Current documentation describes a household as a business account associated with a Party Relationship Group and related organizations as additional business-account records.

Salesforce also demonstrates the same pattern with a household and a related trust. The household is represented by a household account or group, the trust is represented as a business account, and the relationship is represented through account-to-account relationship modeling. ARC can use Account Account Relationship as a junction object to visualize these many-to-many connections.

A Contact object is not sufficient to model Smith ' s Shoes because the store is an organization, not an individual. Account Contact Relationship is primarily used to relate an individual or contact to an account. Since the requirement is to connect the household account to a business account, the correct combination is Household Account, Business Account, and Account Account Relationship.