The Page Header appears across most product pages and adapts based on the page type.

view pages

Display information such as object details, dashboards, or configurable views.

View pages focus on reviewing and interacting with existing information and have the following characteristics:

• The Page Title typically displays an object name or system-generated identifier.
• Status chips and supporting information may communicate object state or attributes.
• Header actions represent common tasks related to the object.

form pages

Support creating or editing records and surface workflow actions such as Create, Save, or Cancel.

Form pages focus on entering or updating information to complete a task and have the following characteristics:

• The Page Title communicates the task being performed (for example, Create or Edit).
• Header actions are workflow actions used to complete the task (Create, Save, Cancel, Next).
• Actions are designed to complete or exit the workflow, rather than interact with existing data.

• Keep the page title concise and descriptive so users can quickly identify the page or object.

• Use supporting information only when it adds meaningful context.

• Limit header actions to one primary action and up to two secondary actions.

• Use status chips to highlight the current state of an object.

• Avoid placing secondary or low-priority actions in the header. Move them to page content or the overflow menu when possible.

The Page Header appears across most product pages and adapts based on the page type.

view pages

Display information such as object details, dashboards, or configurable views.

View pages focus on reviewing and interacting with existing information and have the following characteristics:

• The Page Title typically displays an object name or system-generated identifier.
• Status chips and supporting information may communicate object state or attributes.
• Header actions represent common tasks related to the object.

form pages

Support creating or editing records and surface workflow actions such as Create, Save, or Cancel.

Form pages focus on entering or updating information to complete a task and have the following characteristics:

• The Page Title communicates the task being performed (for example, Create or Edit).
• Header actions are workflow actions used to complete the task (Create, Save, Cancel, Next).
• Actions are designed to complete or exit the workflow, rather than interact with existing data.

• Keep the page title concise and descriptive so users can quickly identify the page or object.

• Use supporting information only when it adds meaningful context.

• Limit header actions to one primary action and up to two secondary actions.

• Use status chips to highlight the current state of an object.

• Avoid placing secondary or low-priority actions in the header. Move them to page content or the overflow menu when possible.

The Page Header appears across most product pages and adapts based on the page type.

view pages

Display information such as object details, dashboards, or configurable views.

View pages focus on reviewing and interacting with existing information and have the following characteristics:

• The Page Title typically displays an object name or system-generated identifier.
• Status chips and supporting information may communicate object state or attributes.
• Header actions represent common tasks related to the object.

form pages

Support creating or editing records and surface workflow actions such as Create, Save, or Cancel.

Form pages focus on entering or updating information to complete a task and have the following characteristics:

• The Page Title communicates the task being performed (for example, Create or Edit).
• Header actions are workflow actions used to complete the task (Create, Save, Cancel, Next).
• Actions are designed to complete or exit the workflow, rather than interact with existing data.

• Keep the page title concise and descriptive so users can quickly identify the page or object.

• Use supporting information only when it adds meaningful context.

• Limit header actions to one primary action and up to two secondary actions.

• Use status chips to highlight the current state of an object.

• Avoid placing secondary or low-priority actions in the header. Move them to page content or the overflow menu when possible.