From 0b2fdc6c6f29778c6665c1909033b5826ad152b4 Mon Sep 17 00:00:00 2001 From: Craig Symonds Date: Mon, 20 Apr 2026 15:17:50 -0700 Subject: [PATCH 1/5] Document property columns in Resource Explorer Add a Property columns section to the Resource Search docs covering creation from the gear menu, adding from the detail view, sort/filter/group behavior, column chooser visibility, and URL-based view sharing. Reuse the Team/Enterprise/Business Critical tier callout already used for property queries, and add a matching bullet to the Discovery key capabilities list. Co-Authored-By: Claude Opus 4.7 (1M context) --- content/docs/insights/discovery/_index.md | 1 + content/docs/insights/discovery/search.md | 43 +++++++++++++++++++++++ 2 files changed, 44 insertions(+) diff --git a/content/docs/insights/discovery/_index.md b/content/docs/insights/discovery/_index.md index 819ae81a645b..d2dcbe9194af 100644 --- a/content/docs/insights/discovery/_index.md +++ b/content/docs/insights/discovery/_index.md @@ -43,6 +43,7 @@ The Resource Search interface provides: - **Advanced search**: Query resources by name, type, stack, project, properties, and more using a rich query syntax - **Filtering and grouping**: Organize resources by dragging column headers to create custom views - **Column customization**: Show or hide information to focus on what matters +- **Property columns**: Promote any resource property—such as `tags.Environment` or `instanceType`—into a sortable, filterable, and groupable column (Team, Enterprise, and Business Critical editions) - **Favorites**: Save and share custom views with your team - **AI assist**: Use natural language queries to find resources (e.g., "How many VPCs do I have?") diff --git a/content/docs/insights/discovery/search.md b/content/docs/insights/discovery/search.md index d7b500d69354..16dc8919624e 100644 --- a/content/docs/insights/discovery/search.md +++ b/content/docs/insights/discovery/search.md @@ -396,6 +396,49 @@ In the example above, the query has been restricted to the "dev" stack. Clicking the "X" within the search bar will remove all previously selected filters. +## Property columns + +{{% notes "info" %}} +Property columns are only available to organizations using Team, Enterprise and Business Critical editions. + +If you would like to use them, [contact us](/contact?form=sales) to upgrade. +{{% /notes %}} + +Property columns let you promote any resource input or output property into a first-class column in the results grid. Once added, a property column behaves like any built-in column: you can sort, filter, and group by its values across all resources returned by your query. + +Property columns use the same [property path](/docs/reference/property-paths/) syntax as [property queries](#property-queries). For example, `tags.Environment` exposes the value of the `Environment` tag on each resource, and `instanceType` exposes the instance type of compute resources. Nested and bracketed paths (such as `tags["name containing spaces"]`) are supported. + +### Creating a property column + +To add a property column from the results grid: + +1. Click the gear icon above the grid to open the settings menu. +1. Select **Create property column**. +1. Enter a property path (for example, `tags.Environment` or `instanceType`) in the dialog that appears. +1. Confirm to add the column. + +The new column is appended to the right of the existing columns. Resources that do not have a value for the given property show an empty cell for that column. + +### Adding a column from the detail view + +When you expand a resource row to view its details, each listed input and output property displays an **Add as column** action next to its value. Clicking this action creates a property column for that property path without having to type it manually — useful when you have already located a property of interest on one resource and want to see its value across every resource in the grid. + +### Sorting, filtering, and grouping + +Property columns support the same interactions as built-in columns: + +- **Sort**: Click the property column header to sort results ascending or descending by property value. +- **Filter**: Open the column filter to narrow results to one or more specific property values. +- **Group by**: Drag the property column header into the Row Groups Header to group resources by property value. Expanding a group drills into the matching resources, just as it does for built-in columns. + +### Hiding and showing property columns + +Property columns can be hidden from the grid without being removed by toggling them off in the column chooser, the same as any built-in column. Re-adding a hidden property column via **Create property column** or **Add as column** makes it visible again. + +### Sharing views with property columns + +Property column configuration is persisted in the page URL. Sharing the URL with another member of your organization opens the grid with the same set of property columns, along with any active filters, sort order, and grouping. This makes property columns suitable for building and sharing repeatable views such as "all compute resources by instance type" or "all resources by environment tag". + ## Download a CSV {{% notes "info" %}} From 722c872cb5c4aa0e6078ac9c528e89891da747a0 Mon Sep 17 00:00:00 2001 From: Craig Symonds Date: Mon, 20 Apr 2026 16:38:41 -0700 Subject: [PATCH 2/5] Address review feedback on property columns docs - Use "settings icon" instead of "gear icon" for the menu control - Rewrite the detail-view section: drill in via the name cell, and document the single Create property column action whose behavior depends on whether the value is a singleton or an object with children - Replace "hiding and showing" with "hiding and deleting": hiding is done via Choose columns in the settings menu; deletion is done by dragging a property column out of the grid, and only works for property columns (not built-in columns) Co-Authored-By: Claude Opus 4.7 (1M context) --- content/docs/insights/discovery/search.md | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/content/docs/insights/discovery/search.md b/content/docs/insights/discovery/search.md index 16dc8919624e..52a3887f2f7e 100644 --- a/content/docs/insights/discovery/search.md +++ b/content/docs/insights/discovery/search.md @@ -412,7 +412,7 @@ Property columns use the same [property path](/docs/reference/property-paths/) s To add a property column from the results grid: -1. Click the gear icon above the grid to open the settings menu. +1. Click the settings icon above the grid to open the settings menu. 1. Select **Create property column**. 1. Enter a property path (for example, `tags.Environment` or `instanceType`) in the dialog that appears. 1. Confirm to add the column. @@ -421,7 +421,12 @@ The new column is appended to the right of the existing columns. Resources that ### Adding a column from the detail view -When you expand a resource row to view its details, each listed input and output property displays an **Add as column** action next to its value. Clicking this action creates a property column for that property path without having to type it manually — useful when you have already located a property of interest on one resource and want to see its value across every resource in the grid. +Click the name cell in a row to drill into the Detailed view for that resource. Each listed input and output property in the Detailed view has a **Create property column** action in its row. Selecting this action adds a column for the property without having to type the path manually — useful when you have already located a property of interest on one resource and want to see its value across every resource in the grid. + +The behavior of **Create property column** depends on the type of the property value: + +- If the property is a single value (for example, a string or number), the column is created immediately for that property path. +- If the property is an object with children (for example, a `tags` map), a dialog opens so you can enter the path to the specific child or grandchild property you want as the column — for instance, `tags.Environment` rather than the entire `tags` object. ### Sorting, filtering, and grouping @@ -431,9 +436,11 @@ Property columns support the same interactions as built-in columns: - **Filter**: Open the column filter to narrow results to one or more specific property values. - **Group by**: Drag the property column header into the Row Groups Header to group resources by property value. Expanding a group drills into the matching resources, just as it does for built-in columns. -### Hiding and showing property columns +### Hiding and deleting property columns + +To hide a property column without removing it, open the settings menu on the main Resources grid and select **Choose columns**, then toggle the column off. The column stays in the set of available columns and can be re-enabled from the same menu. This works for both property columns and built-in columns. -Property columns can be hidden from the grid without being removed by toggling them off in the column chooser, the same as any built-in column. Re-adding a hidden property column via **Create property column** or **Add as column** makes it visible again. +To delete a property column entirely, drag the column header out of the grid and drop it outside. This hides the column and removes it from the set of available columns, so it will no longer appear in **Choose columns**. Only property columns can be deleted — built-in columns cannot be removed from the available set. ### Sharing views with property columns From fbdc82f59c39efbb6a430286f87577ee5115014b Mon Sep 17 00:00:00 2001 From: Craig Symonds Date: Mon, 20 Apr 2026 16:42:42 -0700 Subject: [PATCH 3/5] Address additional docs review feedback - Add Oxford comma to the Property columns tier callout in search.md for consistency with the bullet in _index.md - Drop 'first-class column' phrasing; the next sentence already explains the behavior - Rewrite the sharing-views paragraph in active voice - Tighten the Key capabilities bullet to match the brevity of its neighbors by dropping the inline examples (still covered in full in search.md) Co-Authored-By: Claude Opus 4.7 (1M context) --- content/docs/insights/discovery/_index.md | 2 +- content/docs/insights/discovery/search.md | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/content/docs/insights/discovery/_index.md b/content/docs/insights/discovery/_index.md index d2dcbe9194af..8fb3c17f5acc 100644 --- a/content/docs/insights/discovery/_index.md +++ b/content/docs/insights/discovery/_index.md @@ -43,7 +43,7 @@ The Resource Search interface provides: - **Advanced search**: Query resources by name, type, stack, project, properties, and more using a rich query syntax - **Filtering and grouping**: Organize resources by dragging column headers to create custom views - **Column customization**: Show or hide information to focus on what matters -- **Property columns**: Promote any resource property—such as `tags.Environment` or `instanceType`—into a sortable, filterable, and groupable column (Team, Enterprise, and Business Critical editions) +- **Property columns**: Promote any resource property into a sortable, filterable, and groupable column (Team, Enterprise, and Business Critical editions) - **Favorites**: Save and share custom views with your team - **AI assist**: Use natural language queries to find resources (e.g., "How many VPCs do I have?") diff --git a/content/docs/insights/discovery/search.md b/content/docs/insights/discovery/search.md index 52a3887f2f7e..2679478ab4f3 100644 --- a/content/docs/insights/discovery/search.md +++ b/content/docs/insights/discovery/search.md @@ -399,12 +399,12 @@ Clicking the "X" within the search bar will remove all previously selected filte ## Property columns {{% notes "info" %}} -Property columns are only available to organizations using Team, Enterprise and Business Critical editions. +Property columns are only available to organizations using Team, Enterprise, and Business Critical editions. If you would like to use them, [contact us](/contact?form=sales) to upgrade. {{% /notes %}} -Property columns let you promote any resource input or output property into a first-class column in the results grid. Once added, a property column behaves like any built-in column: you can sort, filter, and group by its values across all resources returned by your query. +Property columns let you promote any resource input or output property into a column in the results grid. Once added, a property column behaves like any built-in column: you can sort, filter, and group by its values across all resources returned by your query. Property columns use the same [property path](/docs/reference/property-paths/) syntax as [property queries](#property-queries). For example, `tags.Environment` exposes the value of the `Environment` tag on each resource, and `instanceType` exposes the instance type of compute resources. Nested and bracketed paths (such as `tags["name containing spaces"]`) are supported. @@ -444,7 +444,7 @@ To delete a property column entirely, drag the column header out of the grid and ### Sharing views with property columns -Property column configuration is persisted in the page URL. Sharing the URL with another member of your organization opens the grid with the same set of property columns, along with any active filters, sort order, and grouping. This makes property columns suitable for building and sharing repeatable views such as "all compute resources by instance type" or "all resources by environment tag". +The set of property columns is persisted in the page URL. Share the URL with another member of your organization and they will open the grid with the same property columns, filters, sort order, and grouping applied. This makes property columns suitable for building and sharing repeatable views such as "all compute resources by instance type" or "all resources by environment tag". ## Download a CSV From 1854dd490ff49c9aeb57298417caa2bcc7097566 Mon Sep 17 00:00:00 2001 From: Cam Date: Tue, 21 Apr 2026 00:16:21 +0000 Subject: [PATCH 4/5] Smooth em-dash voice in property columns section Replace three em-dashes in the new property-columns content with periods / a semicolon so the voice matches the rest of search.md, which has no em-dashes elsewhere. Co-Authored-By: Claude Opus 4.7 (1M context) --- content/docs/insights/discovery/search.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/docs/insights/discovery/search.md b/content/docs/insights/discovery/search.md index 2679478ab4f3..e5ee5fb5e2d1 100644 --- a/content/docs/insights/discovery/search.md +++ b/content/docs/insights/discovery/search.md @@ -421,12 +421,12 @@ The new column is appended to the right of the existing columns. Resources that ### Adding a column from the detail view -Click the name cell in a row to drill into the Detailed view for that resource. Each listed input and output property in the Detailed view has a **Create property column** action in its row. Selecting this action adds a column for the property without having to type the path manually — useful when you have already located a property of interest on one resource and want to see its value across every resource in the grid. +Click the name cell in a row to drill into the Detailed view for that resource. Each listed input and output property in the Detailed view has a **Create property column** action in its row. Selecting this action adds a column for the property without having to type the path manually. This is useful when you have already located a property of interest on one resource and want to see its value across every resource in the grid. The behavior of **Create property column** depends on the type of the property value: - If the property is a single value (for example, a string or number), the column is created immediately for that property path. -- If the property is an object with children (for example, a `tags` map), a dialog opens so you can enter the path to the specific child or grandchild property you want as the column — for instance, `tags.Environment` rather than the entire `tags` object. +- If the property is an object with children (for example, a `tags` map), a dialog opens so you can enter the path to the specific child or grandchild property you want as the column. For example, use `tags.Environment` rather than the entire `tags` object. ### Sorting, filtering, and grouping @@ -440,7 +440,7 @@ Property columns support the same interactions as built-in columns: To hide a property column without removing it, open the settings menu on the main Resources grid and select **Choose columns**, then toggle the column off. The column stays in the set of available columns and can be re-enabled from the same menu. This works for both property columns and built-in columns. -To delete a property column entirely, drag the column header out of the grid and drop it outside. This hides the column and removes it from the set of available columns, so it will no longer appear in **Choose columns**. Only property columns can be deleted — built-in columns cannot be removed from the available set. +To delete a property column entirely, drag the column header out of the grid and drop it outside. This hides the column and removes it from the set of available columns, so it will no longer appear in **Choose columns**. Only property columns can be deleted; built-in columns cannot be removed from the available set. ### Sharing views with property columns From c21b445e5f0db849620e8e37abfbf3a36dc58c10 Mon Sep 17 00:00:00 2001 From: Craig Symonds Date: Mon, 20 Apr 2026 18:19:42 -0700 Subject: [PATCH 5/5] Apply suggestions from code review Co-authored-by: Craig Symonds --- content/docs/insights/discovery/search.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/docs/insights/discovery/search.md b/content/docs/insights/discovery/search.md index e5ee5fb5e2d1..1cca0289506a 100644 --- a/content/docs/insights/discovery/search.md +++ b/content/docs/insights/discovery/search.md @@ -404,7 +404,7 @@ Property columns are only available to organizations using Team, Enterprise, and If you would like to use them, [contact us](/contact?form=sales) to upgrade. {{% /notes %}} -Property columns let you promote any resource input or output property into a column in the results grid. Once added, a property column behaves like any built-in column: you can sort, filter, and group by its values across all resources returned by your query. +Property columns let you promote any resource property into a column in the results grid. Once added, a property column behaves like any built-in column: you can sort, filter, and group by its values across all resources returned by your query. Property columns use the same [property path](/docs/reference/property-paths/) syntax as [property queries](#property-queries). For example, `tags.Environment` exposes the value of the `Environment` tag on each resource, and `instanceType` exposes the instance type of compute resources. Nested and bracketed paths (such as `tags["name containing spaces"]`) are supported. @@ -421,7 +421,7 @@ The new column is appended to the right of the existing columns. Resources that ### Adding a column from the detail view -Click the name cell in a row to drill into the Detailed view for that resource. Each listed input and output property in the Detailed view has a **Create property column** action in its row. Selecting this action adds a column for the property without having to type the path manually. This is useful when you have already located a property of interest on one resource and want to see its value across every resource in the grid. +Click the name cell in a row to drill into the Detailed view for that resource. The Action column menu for each property has a **Create property column** action. Selecting this action adds a column for the property without having to type the path manually. This is useful when you have already located a property of interest on one resource and want to see its value across every resource in the grid. The behavior of **Create property column** depends on the type of the property value: