> For the complete documentation index, see llms.txt.
Skip to main content

Check out Port for yourself ➜ 

Dashboard page

Dashboards are collections of widgets that allow you to display entity data using graphic elements.

⬆ The AI Agent Control Center dashboard as displayed in Port's demo portal.
It lists the AI agents running in your software factory, tracks their runs, and lets you provision new agents through a governed workflow
.


Similar to catalog pages, dashboards reside in the panel on the left-hand side of the software catalog.
Dashboards are a great way to display aggregated data and track information that is relevant and/or interesting to you and your developers.

Create a dashboard page​


  1. Go to the Software catalog in your portal.

  2. In the left sidebar, click on +, then select New dashboard.

  3. Name your dashboard and click Create.

Properties​

When creating a dashboard page, you can set the following properties:

FieldDescriptionRequired
TitleDashboard page titletrue
IdentifierThe dashboard identifier. This is used to reference the page in various places within your portal and is automatically generated when you create the page.true
DescriptionA description of the dashboard.
Supports markdown links ([link text](https://www.link.com))
false
IconThe page iconfalse

Add new widgets​

A dashboard can include any of the supported widgets.

To add a new widget, click on the + Widget button in the top right corner of the dashboard page and choose your desired type.

Reorder and resize widgets​

Widgets can be expanded and/or moved within a dashboard page:

  • To move a widget, drag it from the top to your desired position.

  • To resize a widget, hover over one of its sides, then click and drag it to expand/shrink it.

Minimum row height

Each dashboard row has a minimum height of 400px and cannot be resized below this threshold.

Expand a widget to full page (borderless)​

When a dashboard page has exactly one widget, you can expand that widget so it fills the page without a card header or border. This is useful when you want a single table, chart, or other widget to use the full content area.

To expand a widget:

  1. Open the widget's ... menu.
  2. Select Expand to Page.

In full-page mode:

  • The widget fills the page content area without a card header or border.
  • The widget ... menu moves to the page filter row.
  • Dragging the widget is disabled.

To return to the normal card layout, open the ... menu and select Collapse from Page.

Single widget only

Expand to Page is available only when the page has exactly one widget. If you add a second widget, the normal grid layout returns. The full-page setting is kept, so removing the extra widgets brings full-page mode back automatically.

You need edit permissions on the page to expand or collapse a widget. The option is not available when the page is locked.

You can also set full-page mode when managing pages via the API or IaC by adding "fullPage": true on the root dashboard-widget:

Dashboard widget with full-page mode (click to expand)
{
"id": "myDashboardWidget",
"type": "dashboard-widget",
"fullPage": true,
"layout": [
{
"height": 400,
"columns": [
{ "id": "myTableWidget", "size": 12 }
]
}
],
"widgets": [
{
"id": "myTableWidget",
"type": "table-entities-explorer",
"title": "Services",
"dataset": {
"combinator": "and",
"rules": [
{
"property": "$blueprint",
"operator": "=",
"value": "service"
}
]
}
}
]
}

Duplicate a dashboard​

You can duplicate an existing dashboard page to quickly create a copy with the same configuration.

To duplicate a dashboard:

  1. Click the ... menu either in the top right corner of the dashboard page, or next to the dashboard item in the catalog sidebar.
  2. Select Duplicate dashboard.

The duplicated dashboard inherits the original name followed by the suffix (copy). It appears immediately below the source dashboard in the sidebar and retains all original widgets, layout configurations, and permission settings.

Required permissions

To duplicate a dashboard, you need both edit permissions on the source page and create page permissions in the portal.

Dashboard filters​

Dashboard filters allow you to apply selected filters across all supported widgets within a dashboard at once.
This makes it easier to explore data consistently, without having to filter each widget individually.

You can also save named filter presets and switch between them from the dashboard.

Click a filter to change its values in the value picker. To edit, duplicate, or delete the filter itself, use the ... menu in that picker.

Owning team value picker with Edit, Duplicate, and Delete under the more actions menu

Advanced and custom JSON filters open the full form or JSON editor instead of the value picker.

Filter changes work the same for everyone, but who they apply to depends on role:

Admins (or members with edit permissions for the page): Change filter values and use the ... menu to edit, duplicate, or delete filters. Use Save this view to apply the filters for everyone who can open the dashboard.

Members: Same filter changes as admins are available, but they apply only to a personal view of the dashboard.

Filter placeholders

You can save a filter with no value selected as a placeholder. Until someone picks a value, the filter does not narrow the dashboard. This is supported only for:

  • has any of (for example an empty Owning teams filter).
  • is in.
  • Boolean properties using the = operator.

Admins can leave these placeholders for members to complete from the value picker.

Supported widgets​

Dashboard filters currently apply to the following widgets:

Supported filter types​

When creating a dashboard filter, you can choose between:

  • Basic properties - Meta properties that apply across all blueprints in the dashboard.
  • Blueprint-specific properties - Properties from a specific blueprint that is selected in one or more widgets in the dashboard.
  • User properties - Properties of the user who is viewing the dashboard.
  • Teams properties - Properties of the teams that user belongs to.

The source dropdown lists Basic properties, the blueprints used by widgets in the dashboard, User properties, and Teams properties. For example, if a widget uses the microservice blueprint, microservice will appear as an option in the filter dropdown.

Dashboard filter form with Microservice selected and blueprint options displayed

Filter scope

Filters applied to a specific blueprint will only affect widgets that are relevant to that blueprint in the dashboard.
Filters applied to basic properties will affect all supported widgets across all blueprints.

Basic properties

When selecting Basic properties, you can filter on the following meta properties:

  • Owning teams:
    • Filter entities based on selected team(s).
    • Use the My Teams option to dynamically filter entities relevant to the current user.
    • Applies only to blueprints that include an Owning Team property.
  • Title: Filter entities by their entity title using different string operators.
  • Identifier: Filter entities by their identifier using different string operators.
  • Entity creation date: Filter entities by the date they were created, using date-time operators.
  • Last update: Filter entities by the date they were last updated, using date-time operators.

Blueprint properties

When selecting a specific blueprint (e.g., service), you can filter on any property defined for that blueprint, including:

  • Owning teams: Filter entities of that specific blueprint based on selected team(s). This differs from filtering on owning team using basic properties, which applies across all blueprints.
  • Any other blueprint property: Filter on any property defined in the selected blueprint using the appropriate comparison operators for that property type.

For example, you can filter on owning team across all dashboard blueprints by selecting Basic properties → Owning teams, or you can filter on owning team only for the service blueprint by selecting Service → Owning teams.

User and Teams properties

Select User properties to set a personalized filter using a property of the logged-in user, such as role, status. Select Teams properties to filter using a property of the teams that user belongs to.

The comparison value can also be a user or team property. In the value selector, choose User properties or Teams properties instead of a fixed value. Port then resolves the filter for whoever is viewing the dashboard. For example, you can match an entity's owning team to the current user's teams.

These filters use contextual query rules.

Advanced filters​

A new dashboard filter starts as a single rule. Turn on Advanced in the filter form to build a filter from more than one rule.

Dashboard filter form with Advanced enabled, showing Add Filter and Edit JSON

Multiple rules

With Advanced on, you can:

  • Add more rules.
  • Combine the rules with And or Or.
  • Use User properties and Teams properties in any of those rules, including as the comparison value.
  • Edit JSON code to create more complex filter.

The filter chip shows how many rules it contains, for example 2 filters. Hover over the chip to see the full description of each rule.

Turning Advanced off keeps only the first rule and combines rules with And.

JSON filters

An Edit JSON button appears when Advanced is on. Use it when the filter needs nested rules, such as a group of rules inside another group. The form cannot express those queries.

The JSON uses the same search query structure as other Port filters: a combinator (and or or) and a rules array. A rule can itself be a group with its own combinator and rules. Include blueprint when the filter applies to one blueprint.

{
"combinator": "and",
"blueprint": "microservice",
"rules": [
{
"combinator": "or",
"rules": [
{ "property": "language", "operator": "=", "value": "Go" },
{ "property": "language", "operator": "=", "value": "TypeScript" }
]
},
{ "property": "$team", "operator": "containsAny", "value": ["platform"] }
]
}

A nested filter appears in the dashboard as a Custom filter. Clicking that chip opens the JSON editor again, not the form.

Below is an example dashboard with two types of filters applied:

  1. A Blueprint properties filter on the microservice blueprint that excludes entities where language = Ruby. This filter only affects widgets that display microservice data.
  2. A Basic properties filter on Owning teams, which applies to all supported widgets in the dashboard, regardless of blueprint.

In the example, the Services by language widget reflects the blueprint filter by omitting microservices with language = Ruby, while every widget is narrowed by the Owning teams filter to show only entities associated with the selected team(s).

Dashboard with Microservice language and Owning Teams filters applied across table and pie chart widgets

Date filter​

The date filter narrows the data on the page to a date range. It appears as a calendar chip at the start of the filter bar, and works together with the other dashboard filters.

It is available on dashboard, home, and entity pages. On entity pages, the date range applies to all entities of the blueprint, not just the entity you are viewing.

Choose a date range​

Click the date chip, pick a range, and click Apply. Default removes the date range, so the date filter no longer narrows any widget. Widgets still apply the filters defined in their own configuration, such as an initial date filter.

Pick one of the predefined ranges:

  • Today - The current day.
  • Yesterday - The previous day.
  • 7D, 30D - The last 7 or 30 days, including today.
  • 3M, 6M, 12M - The last 3, 6, or 12 calendar months.

Or click Custom and select one of the following range types:

  • Fixed - Between two dates, both inclusive. Type the dates or select them on the calendar.
  • Last - The last N days, weeks, months, or quarters, ending today. Use Ending to end the range earlier, for example the last 4 weeks ending 1 week ago.
  • Next - The next N days, weeks, months, or quarters, starting today. Use Starting to start the range later.
  • Since - From a date until today.
  • Period to date - From the start of the current day, week, month, quarter, or year until today. Weeks start on Monday.

Prefer relative ranges such as Last or 30D: they move forward with time, so the dashboard stays current. A Fixed range always shows the same dates.

Supported widgets​

The date range applies to widgets that show entities or entity data. Each widget filters by a date property:

WidgetDate property used
Table, Board, Pie chart, Bar chart$createdAt by default. Can be changed in the date filter settings.
Number chartThe time property set in the widget (measureTimeBy). Number charts that display a single property are not filtered.
Line chartThe time property set in the widget (measureTimeBy), for each line in a multi-line chart. Charts that display the history of a property value show only the part of their time range that falls inside the date range.

Choose the date property per widget​

If you have edit permissions on the page, click the settings icon in the date picker to open Date filter settings. It lists the widgets on the page and lets you choose which date property each table, board, pie chart, and bar chart widget uses when a date range is applied.

Widgets whose date property is set in their definition, such as number and line charts, are listed with their property and cannot be changed here.

Combine with other filters​

The date filter does not replace your other filters. You can still add date-based dashboard filters with the Filter button, for example on Entity creation date or Last update.

All of these are combined with AND: the date filter, the dashboard filters, and the filters defined in each widget's own configuration. A widget shows only the entities that match all of them.

Save the date range​

A date range you pick is remembered in your browser for each page, and applies only to your own view.

To save it for everyone who can open the page, click Save this view. If the page has filter presets, the date range is saved with the selected preset instead.

Manage the date filter from the API​

Set the pageDateFilter field when you create or update a page. It contains a range object whose type is one of the following:

TypePropertiesExample
quickRangequickRange: today, yesterday, 7d, 30d, 3m, 6m, or 12m{ "type": "quickRange", "quickRange": "30d" }
fixedfrom, to: dates in YYYY-MM-DD format, both inclusive{ "type": "fixed", "from": "2026-01-01", "to": "2026-03-31" }
sincefrom: a date in YYYY-MM-DD format{ "type": "since", "from": "2026-01-01" }
lastamount, unit (day, week, month, or quarter), and an optional offset{ "type": "last", "amount": 2, "unit": "week", "offset": 1 }
nextamount, unit (day, week, month, or quarter), and an optional offset{ "type": "next", "amount": 1, "unit": "month" }
periodToDateperiod: day, week, month, quarter, or year{ "type": "periodToDate", "period": "quarter" }

For example, the following page definition sets the date filter of the microservice_dashboard page to the last 30 days:

{
"identifier": "microservice_dashboard",
"pageDateFilter": {
"range": { "type": "quickRange", "quickRange": "30d" }
}
}

Set pageDateFilter to null to remove the date filter. To choose the date property of a table, board, pie chart, or bar chart widget, set dashboardDateProperty in the widget definition. The default is $createdAt.

In Terraform, use the page_date_filter attribute of the port_page resource.

Filter presets​

Filter presets let you save named sets of dashboard filters and switch between them without rebuilding the query each time.

A preset also saves the date range that is selected when you create it.

Each dashboard with presets includes an All tab. All shows the dashboard with no preset filters applied. Named presets appear next to it.

Create a preset​

  1. Add one or more dashboard filters using the Filter button.
  2. Click Save as Preset.
  3. Enter a Preset name, then click Save.

The new preset appears as a tab and becomes the active selection.

After the first preset exists, use the + button next to the preset tabs to save another preset from the current filters.

Save as Preset is available only when at least one filter is applied, you have edit permissions on the page, and the page is not locked.

Apply a preset​

Click a named preset tab to apply its saved filters across all supported widgets. Click All to clear those filters.

Port remembers the last preset you selected on each dashboard. If you have not selected a preset yet and the dashboard already has presets, the first named preset is applied.

Reorder and delete presets​

If you have edit permissions and the page is not locked:

  • Drag a named preset tab to change its order. All stays first and cannot be moved.
  • Click the close icon on a named preset tab to delete it.

If you delete the active preset, Port selects the first remaining named preset. If none remain, it selects All.

Save presets for other users​

Creating, reordering, and deleting presets updates your current view. Click Save this view to persist those changes for everyone who can open the dashboard.

If you change filters while a named preset is selected, Save this view updates that preset.

Saving on All

If All is selected and the dashboard already has presets, you cannot save filters on All. Create a named preset instead.

You can still save the view from All when the change is to the preset list itself, for example after deleting a preset.

Reset view restores the saved filters for the currently selected preset. If All is selected, it clears the filters.

Manage presets from the API​

You can define presets when you create or update a dashboard page by setting pageFilterPresets. Each preset has:

  • identifier: A unique identifier for the preset.
  • title: The label shown on the preset tab.
  • filters: An array of dashboard filters. Each filter uses the same shape as pageFilters (identifier, title, and query).
  • pageDateFilter: Optional. The date range that is applied when the preset is selected.

Preset identifiers must be unique on the page. Filter identifiers must also be unique within each preset.

Permissions​

Admin role: As an admin (or a member with edit permissions for the dashboard), you can add, edit, or remove filters from the dashboard page. Then, save the view to apply it for other users. You can also create, reorder, and delete filter presets, then save the view so others can use them.

Member role: As a member, you can view, add, edit, or remove filters on the page (unless the page is locked). The changes apply only to your own view. You can switch between existing filter presets. Creating, reordering, or deleting presets requires edit permissions on the page.

If the page is locked, you cannot change filters or switch presets.

Dashboard filter editor changing the Service language filter to exclude Ruby