---
schema_version: "1"
id: e8d80242d43cc8a6ba2366e590ace157184ef31e94aca21672a0f7e3ecd7d919
title: Record Banner
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/experience/264-0-0/rss_record_headline.md
canonical_url: https://help.salesforce.com/s/articleView?id=experience.rss_record_headline.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 0b9de95eff4e16a4bf9d6ac7fbed34b24c4c0c25a29839b50ae5885359dde738
description: The Record Banner component shows the record name, key record highlights, and action buttons that allow users to edit or delete the record.
products:
  - Experiences
release: "264"
---
# Record Banner

The Record Banner component shows the record name, key record highlights, and action buttons that allow users to edit or delete the record.

Before Spring ’16, this component was named Record Headline. The Customer Service template supports a record detail page that you can use out of the box with no configuration. All objects in your site without a preassigned record detail page use this generic page, called Record Detail, to display record data. For example, consider the scenario where a user lands on a case detail page. The page uses a preassigned case detail layout. The user clicks a contact in the related records. If you haven’t created a custom record detail page for contacts, the contact information is displayed using the generic Record Detail page. Under the hood, the Record Detail page uses the Record Banner component along with the Record Information Tabs component to display record data.

- You can use the Record Banner component on custom record detail pages that you create. We recommend using it with the Record Information Tabs component.
- You can modify what fields display in the Record Banner component by customizing the Highlights Panel layout in the object’s compact page layout.
- Members with the necessary permissions can use the Edit, Delete, and Follow buttons to modify, delete, or follow the record. These buttons don’t display on mobile devices.
- The Record Banner component doesn’t support translation on the Topic Detail page.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-experience-communities-264-0-0-production-enus/bf7df212-91a1-4fa3-a007-4d6f3e3b470b/images/icon_note.png)

Note

For optimal appearance, choose a wide column width when placing this component on your page. Some fields are hidden when there isn't enough space to display them due to browser width or zoom level.

1. From the Pages menu in Experience Builder, select Record Detail or your custom record detail page.
2. Select the **Record Banner** component, or drag the component from the Components panel to the page.
3. In the property editor, configure the properties for the component.
    
     
    | Property | Details |
    | --- | --- |
    | Record ID | The ID of the record displayed. Typically, this field is automatically populated. |

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-experience-communities-264-0-0-production-enus/bf7df212-91a1-4fa3-a007-4d6f3e3b470b/images/icon_example.png)

Example

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-experience-communities-264-0-0-production-enus/bf7df212-91a1-4fa3-a007-4d6f3e3b470b/images/icon_note.png)

Note In the mobile app, lookup fields in the Record Banner component are shown as text, not links.

Sample Record Banner component in the Customer Service template.

![Record Banner component](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-experience-communities-264-0-0-production-enus/bf7df212-91a1-4fa3-a007-4d6f3e3b470b/communities/images/record_headline_napili.png)

#### See Also

- [Which Components Can I Use with Each Aura Template?](https://help.salesforce.com/s/articleView?id=experience.rss_component_reference_table.htm&release=264.0.0&type=5 "Aura site templates, such as Customer Service and Partner Central, are each composed of pages, which in turn are made up of customizable components. Consult this table to find out which Aura template each component can be used in, and when the component became available.")