Search

Dashboard

A dashboard presents only the information that’s relevant to the user’s priorities in a single, consolidated view. The user can monitor key performance metrics, access frequent actions, and quickly spot trends or issues to help them make informed decisions and take action in a timely manner.

While the specific content will vary depending on the target audience, the overall structure is widely applicable and supports a consistent user experience in diverse contexts.

When to Use

Follow the page layout for a dashboard when the user needs to:

  • Monitor key metrics, trends, or exceptions, and spot issues or opportunities at a glance
    • Examples: Financial performance, operational KPIs, sales pipelines, and delays in key workflows
  • Have a consolidated view of the information that matters most to their role, with data that’s aggregated and visualized from multiple sources
    • Examples: Management, operations, and support
  • Have immediate visibility into high-priority tasks, alerts, or recent changes, allowing them to triage issues and focus their attention where it’s needed most—rather than processing records one by one
    • Examples: New incidents, escalations, and urgent tickets
  • Detect anomalies like overdue items or process delays; identify trends; and then drill into more details
    • Examples: Monitoring financial health, tracking operational performance, managing sales, and customer support activities

Key Sections

A typical dashboard has 2 sections of content:

  1. Header area
  2. Primary information

1. Header Area

Tells the user where they are within the application and provides context about what’s on the page. This generally includes the page title and actions. It could also include a breadcrumb.

2. Primary Information

Presents supporting details—such as recent activity, alerts, charts, or quick links—that help users understand context, spot trends, and take action.

Components

IDS components can help you build a dashboard. The structure of the page will depend on how much information the user needs to see. Here are some components to consider:

  1. Header
  2. Card*
    • Displays information (such as status or key metrics) or quick actions (such as “Edit” or “Delete”) about a selected item
    • Presents skimmable information, actionable alerts, or summaries (such as tasks, messages, or incidents)
    • May contain other components such as listviews, icons, fieldsets, charts, and data grids

*As an alternative to cards, consider using other components that are described in the list and details page layout or the data grid view page layout.

Example

This is a hi-fi example of a dashboard designed using IDS components. Use it as a guide for designing your own page. This layout is available in Figma in the IDS Page Layout Library v. 1.0.

Refer to this library to see examples of dashboards that are being used in the CloudSuites today. (For internal reference only. An Infor SAAM request is required for Wiki access. Updated October 2025.)