Search Layout
A Search Layout is the per-object configuration that controls which fields appear as columns when Salesforce displays the object in search results, list views, lookup dialogs, and recent-items panels.
Definition
A Search Layout is the per-object configuration that controls which fields appear as columns when Salesforce displays the object in search results, list views, lookup dialogs, and recent-items panels. Each object has its own search layout settings managed in Setup, and each context (Global Search Results, Search Results, Lookup Dialogs, Lookup Phone Dialogs, Tab) can use a different set of fields and ordering.
Search Layouts are the user-facing answer to "what should I see when this object shows up in a list." The fields visible on an Opportunity search result, for example, are not the same fields shown on the Opportunity record detail page; the search layout selects which subset to show, in which order, and the user sees only those columns regardless of the underlying record's data richness. Tuning search layouts is one of the highest-impact admin tasks because it directly affects how quickly users can identify the right record without clicking through.
How Search Layouts shape the day-to-day Salesforce experience for end users
The four search layout contexts
Salesforce treats search layouts as four distinct contexts per object. Search Results applies to the global search results page when the object appears as a tab. Lookup Dialogs applies to the picker that opens when a user clicks the magnifying glass on a relationship field. Lookup Phone Dialogs is the click-to-dial picker for phone fields. Tab is the list view header on the object's standard tab. Each context can show different fields, in different order, because the user's intent differs: a lookup dialog needs the discriminator fields (Name plus Industry); a tab list view typically needs more business detail.
Configuring the column set
Setup, Object Manager, the object, Search Layouts. The screen lists each context with its current field set. Editing a context opens a two-panel picker: available fields on the left, selected fields on the right. The order in the right panel determines the column order in the UI. Salesforce caps the number of columns per context (typically 10 to 15 depending on context); pick the discriminator fields users actually scan, not every field the record carries.
Compact Layouts and the relationship to Search Layouts
Lightning Experience introduced Compact Layouts, which define which fields appear in record highlights panels, related-list collapsed views, and mobile cards. Compact Layouts overlap conceptually with Search Layouts but apply in different UI surfaces. Compact Layouts drive the small summary card at the top of every record; Search Layouts drive the search results pages and lookup dialogs. Both need attention, and the field sets often differ because the contexts highlight different aspects of the record.
Search Layout vs Search Result rendering
The Search Layout configures the columns Salesforce attempts to show. The actual rendered table depends on the user's permissions: any field the user cannot read is hidden from their search result rows, even if the search layout includes it. This is the right behavior for security but produces a confusing user experience if some users see fewer columns than others. Audit search layouts against the permission set hierarchy when rolling out a new field or restricting visibility.
Mobile and Salesforce App
On the Salesforce mobile app, search results respect the configured search layout but typically only render the first 4 to 6 fields because of screen real estate. The mobile-first column choice should be the most discriminating fields (Name, Account, Stage, Amount for an Opportunity). Reps using the mobile app to look up records mid-call have far less screen than desktop; a tuned search layout cuts seconds off every lookup.
Custom buttons in search layouts
Search Layouts also control which custom buttons appear above the search results table. An admin can add a custom button (a deep-link to a flow, a Visualforce action) that fires from the search results page itself. This is useful for bulk actions that should be available from the result list (Mass Convert Lead, Bulk Reassign Owner) without forcing the user to navigate into each record first.
Global Search Results object selection
Beyond per-object search layouts, Salesforce has a setting for which objects appear in Global Search Results at all. Setup, User Interface, Search Settings. The admin selects which objects to include in the global search; objects not selected are hidden from the search picker entirely. This is the org-wide filter that runs before any per-object search layout applies, and it is the first place to look when a user reports an object missing from search.
Customize the Search Layout for an object
Pick the fields that should appear as columns in search results and lookup dialogs for a specific object, then save and verify end users see the new column set.
- Open Object Manager
Setup, Object Manager. Pick the target object (Account, Opportunity, custom object). The object detail screen lists every configuration area including Search Layouts.
- Open Search Layouts
Click Search Layouts in the left nav. The page lists the four contexts (Search Results, Lookup Dialogs, Lookup Phone Dialogs, Tab) with current field sets.
- Edit the target context
Click Edit next to the context you want to update. The two-panel picker appears with available fields on the left.
- Select and order fields
Move the discriminator fields to the right panel. Use the Up and Down buttons to set column order. Aim for 4 to 8 fields; more is rarely useful.
- Save and verify
Save. Run a search or open a lookup dialog as a test user. Confirm the new columns appear in the expected order.
- Audit permissions
For each field added, confirm the right profiles can read it. A field included in the search layout but invisible to some users will show as blank for them.
Columns shown in the global search results tab for this object.
Columns shown in the picker that opens from a relationship field.
Columns shown in the default list view on the object's standard tab.
Actions surfaced above the search results table; configurable per layout.
- Field-level security overrides the search layout. A field in the layout that the user cannot read renders as blank, which surprises users who expected the column to be populated.
- Lightning Experience also uses Compact Layouts for record highlights. Updating one does not update the other; both need attention when a key field changes.
- Search Layout changes do not appear in saved list views. Existing list views keep their original columns; new list views inherit the updated search layout defaults.
- Object visibility in Global Search Results is controlled separately in Search Settings. If an object is missing from global search entirely, check that screen first.
Trust & references
Cross-checked against the following references.
- Customize Search LayoutsSalesforce Help
- Search OverviewSalesforce Help
- Compact Layouts OverviewSalesforce Help
Straight from the source - Salesforce's reference material on Search Layout.
- Search Layouts DocumentationSalesforce Help
- Global SearchSalesforce Help
- Field-Level SecuritySalesforce Help
Hands-on resources to go deeper on Search Layout.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is a Search Layout?
Q2. Why customize search layouts?
Q3. Where do search layouts apply?
Discussion
Loading discussion…