C
Chanel Haugh
The Problem: CO records are still. single endless column. Records with 30-50+ fields mean constant scrolling to find one value - a real cost on a live call, when a rep needs a field now, not after 3 scrolls. It pushes teams toward post-call corrections and error-prone workaround automations to capture what was missed.
This isn't a new ask - it's a gap.
You already built and shipped this exact framework for Contacts in Labs (April 2026): panel layouts, drag-and-drop fields reordering, show/hide fields, assignable views per user or team. Custom Objects never got it. This requires is simply: apply the same framework you already validated with 100 beta customers and zero reported bugs to Custom Object records.
What we're asking for:
• Bring the Contact Page Customization framework (panels, reorderable modules, show/hide fields, assignable views) to Custom Object record detail pages. A 3-column layout alone would surface roughly 3x the fields in the same scroll depth as today's single column.
• Section/panel grouping also matters beyond speed: keeping related fields (financials, contact info, status, etc.) visually distinct rather than blurred into one long list makes records easier to scan and navigate for anyone who relies on visual structure to find information quickly - a real accessibility gain, not just a convenience one.
• Interrim step if the full framework takes longer: 1-click access to pinned "key fields" folder at the top of the record, with an equally fast click back to the full field list.
What this is NOT asking for:
Not a change to list view (which already has customizable, sortable columns) - this is specifically the sing-record detail page, which List View doesn't touch. Not a request for a new UI system - it's reusing the panel/module framework that already exists for Contacts.
Why now:
Custom Objects has had steady investment this year - List view, workflow actions for associated records, unique field enforcement, native form support. The record detail page I the one piece of that experience still stuck in v1.