Problem Statement

Currently, when viewing custom objects associated with a contact (in the contact's detail view), only the primary display field is shown. This makes it extremely difficult to get useful information at a glance without having to click into each individual custom object record.

For example, I use custom objects to track insurance policies for my clients. When I look at a contact's associated policies, I only see the policy number. I cannot see critical information like:

Policy type (Auto, Home, Life, etc.)

Premium amount

Coverage limits

Carrier/Insurance company

Expiration date

Status

This forces me to click into each policy individually just to see basic details, which is time-consuming and inefficient when managing multiple policies per client.

Requested Feature

Add the ability to customize which custom object fields are displayed in the contact association panel, similar to how Opportunity cards can be customized.

Ideally, this would allow users to:

Select 3-7 custom fields to display on each custom object card in the association view

Choose the layout/format of how these fields appear

Apply these display settings at the custom object schema level (so all instances show the same fields)

Use Cases

This feature would benefit many industries and use cases:

Insurance agencies tracking multiple policies per client

Real estate tracking properties, showings, and listings

Legal firms tracking cases and documents

Healthcare tracking treatments, appointments, or prescriptions

Financial services tracking accounts, investments, or loans

Any business using custom objects to track multiple related records per contact

Impact

This enhancement would make custom objects significantly more practical and user-friendly, reducing clicks and improving workflow efficiency. Right now, opportunities have better display customization than custom objects, which limits the usefulness of the custom objects feature for many users.

Comparison to Current Features

Opportunity cards already have this functionality and can display multiple custom fields. Bringing this same capability to custom objects would create feature parity and make both tools equally powerful for different use cases.