From cccfab53aeb3cdccb24f5f248b0d344f1a1b3caa Mon Sep 17 00:00:00 2001 From: Florent LB Date: Thu, 2 Jul 2026 15:39:13 +0200 Subject: [PATCH 1/8] docs: rework import dashboards for the Dashboards API workflow (#7166) Split the import page into an applies-switch mirroring the Export JSON section: a 9.4+/serverless tab that routes to copy-to-space and the Dashboards API / manage-as-code, and a 9.0-9.3 tab that keeps the Saved Objects NDJSON import. Move import and sharing under Managing dashboards. Co-authored-by: Cursor --- explore-analyze/dashboards.md | 2 +- .../dashboards/import-dashboards.md | 31 +++++++++++++++---- explore-analyze/toc.yml | 5 +-- 3 files changed, 29 insertions(+), 9 deletions(-) diff --git a/explore-analyze/dashboards.md b/explore-analyze/dashboards.md index c49a5e7be3..8b33f1dfbc 100644 --- a/explore-analyze/dashboards.md +++ b/explore-analyze/dashboards.md @@ -44,7 +44,7 @@ Once you understand the basics, explore these common tasks: - [Manage dashboards](dashboards/managing.md): Browse, search, organize, and track usage of your dashboards. - [Share and export dashboards](dashboards/sharing.md): Share with your team using links or embeds, and export as PDF, PNG, or CSV. - [Duplicate a dashboard](dashboards/duplicate-dashboards.md): Create customizable copies of existing dashboards. -- [Import a dashboard](dashboards/import-dashboards.md): Bring dashboards from other environments. +- [Import a dashboard](dashboards/import-dashboards.md): Bring a dashboard from another space, instance, or deployment into your own. ## About managed dashboards [managed-dashboards] diff --git a/explore-analyze/dashboards/import-dashboards.md b/explore-analyze/dashboards/import-dashboards.md index 98335e33c7..62720b88d3 100644 --- a/explore-analyze/dashboards/import-dashboards.md +++ b/explore-analyze/dashboards/import-dashboards.md @@ -1,7 +1,7 @@ --- mapped_pages: - https://www.elastic.co/guide/en/kibana/current/_import_dashboards.html -description: Import dashboards and their related objects into Kibana from NDJSON files using the Saved Objects interface. +description: Move a Kibana dashboard into another space or deployment by copying it, recreating it with the Dashboards API, or importing it from an NDJSON file. applies_to: stack: ga serverless: ga @@ -11,9 +11,26 @@ products: # Import a dashboard [_import_dashboards] -Import dashboards into {{product.kibana}} from NDJSON files exported from other {{product.kibana}} instances or spaces. When you import a dashboard, you also import its related objects such as data views and visualizations, making it easy to migrate dashboards between environments or share them with other teams. +Bring a dashboard from another {{product.kibana}} space, instance, or deployment into your own. -## Requirements [import-dashboard-requirements] +:::::{applies-switch} + +::::{applies-item} {stack: preview 9.4, serverless: preview} + +Choose the approach that matches where the dashboard is coming from: + +- **From another space in the same deployment**: [copy the dashboard to the target space](../find-and-organize/saved-objects.md#saved-objects-copy-to-other-spaces) from the **Saved Objects** page. The copy includes the dashboard's related objects, such as data views. +- **From another deployment, or as part of a code-based workflow**: recreate the dashboard from its JSON definition with the [Dashboards API](create-dashboards-programmatically.md). [Export the source dashboard as API-compatible JSON](sharing.md#export-dashboard-json), then send it to the API in the target deployment. To version-control dashboards and keep their references portable across environments, refer to [Manage dashboards as code](manage-dashboards-as-code.md). + +:::{note} +You can still [import dashboards from NDJSON files](../find-and-organize/saved-objects.md#saved-objects-import) on the **Saved Objects** page. The approaches above are the recommended way to move dashboards across spaces and deployments. +::: + +:::: + +::::{applies-item} {stack: ga 9.0-9.3} + +Import dashboards into {{product.kibana}} from NDJSON files exported from other {{product.kibana}} instances or spaces. When you import a dashboard, you also import its related objects such as data views and visualizations, so you can migrate dashboards between environments or share them with other teams. To import dashboards, you need: @@ -21,13 +38,15 @@ To import dashboards, you need: * An NDJSON file containing the dashboard and its related objects * Access to **Stack Management** in {{product.kibana}} -## Import a dashboard [import-dashboard-steps] - You can import dashboards from the [Saved Objects](../find-and-organize/saved-objects.md) page under **Stack Management**. When importing dashboards, you also import their related objects, such as data views and visualizations. Import options allow you to define how the import should behave with these related objects: -* **Check for existing objects**: When selected, objects are not imported when another object with the same ID already exists in this space or cluster. For example, if you import a dashboard that uses a data view which already exists, the data view is not imported and the dashboard uses the existing data view instead. You can also chose to select manually which of the imported or the existing objects are kept by selecting **Request action on conflict**. +* **Check for existing objects**: When selected, objects are not imported when another object with the same ID already exists in this space or cluster. For example, if you import a dashboard that uses a data view which already exists, the data view is not imported and the dashboard uses the existing data view instead. You can also choose to select manually which of the imported or the existing objects are kept by selecting **Request action on conflict**. * **Create new objects with random IDs**: All related objects are imported and are assigned a new ID to avoid conflicts. ![Import panel](/explore-analyze/images/kibana-dashboard-import-saved-object.png "") + +:::: + +::::: diff --git a/explore-analyze/toc.yml b/explore-analyze/toc.yml index 46aad620e1..0ea92f92a8 100644 --- a/explore-analyze/toc.yml +++ b/explore-analyze/toc.yml @@ -286,9 +286,10 @@ toc: - file: dashboards/drilldowns.md - file: dashboards/arrange-panels.md - file: dashboards/duplicate-dashboards.md - - file: dashboards/import-dashboards.md - file: dashboards/managing.md - - file: dashboards/sharing.md + children: + - file: dashboards/sharing.md + - file: dashboards/import-dashboards.md - file: dashboards/tutorials.md children: - file: dashboards/create-dashboard-of-panels-with-web-server-data.md From b7e9c7b7eee598e59d3ced54d0715b8e26795b18 Mon Sep 17 00:00:00 2001 From: Florent LB Date: Wed, 8 Jul 2026 18:36:49 +0200 Subject: [PATCH 2/8] docs: motivate import use cases and lead the 9.4+ flow with the Dashboards API Rework the intro to present why you would import a dashboard, and reframe the 9.4+ tab so the Dashboards API is the primary import flow. Demote copy-to-space to a secondary aside for same-deployment moves. Co-authored-by: Cursor --- explore-analyze/dashboards/import-dashboards.md | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/explore-analyze/dashboards/import-dashboards.md b/explore-analyze/dashboards/import-dashboards.md index 62720b88d3..569c5c5a89 100644 --- a/explore-analyze/dashboards/import-dashboards.md +++ b/explore-analyze/dashboards/import-dashboards.md @@ -1,7 +1,7 @@ --- mapped_pages: - https://www.elastic.co/guide/en/kibana/current/_import_dashboards.html -description: Move a Kibana dashboard into another space or deployment by copying it, recreating it with the Dashboards API, or importing it from an NDJSON file. +description: Import a Kibana dashboard into another space, instance, or deployment with the Dashboards API, or from an NDJSON file on earlier versions. applies_to: stack: ga serverless: ga @@ -11,19 +11,24 @@ products: # Import a dashboard [_import_dashboards] -Bring a dashboard from another {{product.kibana}} space, instance, or deployment into your own. +Import a dashboard to recreate one that was built elsewhere in your own {{product.kibana}} space, instance, or deployment. You might import a dashboard to: + +- Promote it across environments, such as from development to staging to production. +- Share it with another team or {{kib}} instance. +- Recreate it from a version-controlled or backed-up definition. :::::{applies-switch} ::::{applies-item} {stack: preview 9.4, serverless: preview} -Choose the approach that matches where the dashboard is coming from: +The [Dashboards API](create-dashboards-programmatically.md) is the main way to import a dashboard. You recreate a dashboard from its JSON definition: take the dashboard's [API-compatible JSON](sharing.md#export-dashboard-json), exported from the source dashboard or stored in version control, and send it to the Dashboards API in the target space, instance, or deployment. The API creates the dashboard, or updates it in place when you deploy it with the same ID. + +For an imported dashboard to work, the objects it references, such as data views and library visualizations, must also exist in the target environment. To version-control dashboards and keep their references portable across environments, refer to [Manage dashboards as code](manage-dashboards-as-code.md). -- **From another space in the same deployment**: [copy the dashboard to the target space](../find-and-organize/saved-objects.md#saved-objects-copy-to-other-spaces) from the **Saved Objects** page. The copy includes the dashboard's related objects, such as data views. -- **From another deployment, or as part of a code-based workflow**: recreate the dashboard from its JSON definition with the [Dashboards API](create-dashboards-programmatically.md). [Export the source dashboard as API-compatible JSON](sharing.md#export-dashboard-json), then send it to the API in the target deployment. To version-control dashboards and keep their references portable across environments, refer to [Manage dashboards as code](manage-dashboards-as-code.md). +To move a dashboard to another space within the same deployment, you don't need to export and import it. Instead, [copy it to the target space](../find-and-organize/saved-objects.md#saved-objects-copy-to-other-spaces) from the **Saved Objects** page, together with its related objects. :::{note} -You can still [import dashboards from NDJSON files](../find-and-organize/saved-objects.md#saved-objects-import) on the **Saved Objects** page. The approaches above are the recommended way to move dashboards across spaces and deployments. +You can still [import dashboards from NDJSON files](../find-and-organize/saved-objects.md#saved-objects-import) on the **Saved Objects** page, but the Dashboards API is the recommended way to import a dashboard. ::: :::: From de6272d63ed129f90120a80c4295b134d41bd8cd Mon Sep 17 00:00:00 2001 From: Florent LB Date: Wed, 8 Jul 2026 19:06:07 +0200 Subject: [PATCH 3/8] docs: restructure import page by exported artifact type Replace the version-based applies-switch with a tab set named by the exported format (JSON via Dashboards API, NDJSON via Saved Objects). Reframe the intro around how the dashboard was exported, give each tab clear prerequisites, and lean on the export page for the concepts. Co-authored-by: Cursor --- .../dashboards/import-dashboards.md | 55 ++++++++++--------- 1 file changed, 29 insertions(+), 26 deletions(-) diff --git a/explore-analyze/dashboards/import-dashboards.md b/explore-analyze/dashboards/import-dashboards.md index 569c5c5a89..f000ffaa13 100644 --- a/explore-analyze/dashboards/import-dashboards.md +++ b/explore-analyze/dashboards/import-dashboards.md @@ -1,7 +1,7 @@ --- mapped_pages: - https://www.elastic.co/guide/en/kibana/current/_import_dashboards.html -description: Import a Kibana dashboard into another space, instance, or deployment with the Dashboards API, or from an NDJSON file on earlier versions. +description: Import a Kibana dashboard exported from another space, instance, deployment, or project, using the Dashboards API or the Saved Objects API. applies_to: stack: ga serverless: ga @@ -11,47 +11,50 @@ products: # Import a dashboard [_import_dashboards] -Import a dashboard to recreate one that was built elsewhere in your own {{product.kibana}} space, instance, or deployment. You might import a dashboard to: +Import a dashboard that was exported from another {{product.kibana}} space, instance, deployment, or project. How you import it depends on the format it was exported in. Refer to [Share and export dashboards](sharing.md#export-dashboards) for the export options, then use the matching import method: -- Promote it across environments, such as from development to staging to production. -- Share it with another team or {{kib}} instance. -- Recreate it from a version-controlled or backed-up definition. +- {applies_to}`stack: preview 9.4` {applies_to}`serverless: preview` **JSON**: import it with the [Dashboards API](create-dashboards-programmatically.md). This is the recommended method. +- **NDJSON**: import it with the [Saved Objects API]({{kib-apis}}group/endpoint-saved-objects), or from the **Saved Objects** page. -:::::{applies-switch} +:::{note} +To move a dashboard to another space within the same deployment, you don't need to export and import it. Instead, [copy it to the target space](../find-and-organize/saved-objects.md#saved-objects-copy-to-other-spaces) from the **Saved Objects** page, together with its related objects. +::: -::::{applies-item} {stack: preview 9.4, serverless: preview} +::::::{tab-set} -The [Dashboards API](create-dashboards-programmatically.md) is the main way to import a dashboard. You recreate a dashboard from its JSON definition: take the dashboard's [API-compatible JSON](sharing.md#export-dashboard-json), exported from the source dashboard or stored in version control, and send it to the Dashboards API in the target space, instance, or deployment. The API creates the dashboard, or updates it in place when you deploy it with the same ID. +:::::{tab-item} JSON (Dashboards API) -For an imported dashboard to work, the objects it references, such as data views and library visualizations, must also exist in the target environment. To version-control dashboards and keep their references portable across environments, refer to [Manage dashboards as code](manage-dashboards-as-code.md). +{applies_to}`stack: preview 9.4` {applies_to}`serverless: preview` Recreate the dashboard by sending its JSON definition to the [Dashboards API](create-dashboards-programmatically.md). This is the recommended import method. -To move a dashboard to another space within the same deployment, you don't need to export and import it. Instead, [copy it to the target space](../find-and-organize/saved-objects.md#saved-objects-copy-to-other-spaces) from the **Saved Objects** page, together with its related objects. +**Prerequisites** -:::{note} -You can still [import dashboards from NDJSON files](../find-and-organize/saved-objects.md#saved-objects-import) on the **Saved Objects** page, but the Dashboards API is the recommended way to import a dashboard. -::: +- The dashboard's API-compatible JSON. Refer to [Share and export dashboards](sharing.md#export-dashboard-json) to produce it. +- **All** privilege for the **Dashboard** feature in {{product.kibana}}. +- A way to call the API, such as {{kib}} Dev Tools Console or an API key. -:::: +Send the JSON to the Dashboards API in the target space, instance, deployment, or project. The [JSON export flow](sharing.md#export-dashboard-json) can open a pre-populated request in {{kib}} Dev Tools Console, where you set the target space before sending it. The API creates the dashboard, or updates it in place when you send it with an existing ID. -::::{applies-item} {stack: ga 9.0-9.3} +For the imported dashboard to work, the objects it references, such as data views and library visualizations, must also exist in the target environment. To version-control dashboards and keep their references portable across environments, refer to [Manage dashboards as code](manage-dashboards-as-code.md). -Import dashboards into {{product.kibana}} from NDJSON files exported from other {{product.kibana}} instances or spaces. When you import a dashboard, you also import its related objects such as data views and visualizations, so you can migrate dashboards between environments or share them with other teams. +::::: -To import dashboards, you need: +:::::{tab-item} NDJSON (Saved Objects) -* **All** privilege for the **Dashboard** and **Saved Objects Management** features in {{product.kibana}} -* An NDJSON file containing the dashboard and its related objects -* Access to **Stack Management** in {{product.kibana}} +Import the dashboard and its related objects from an NDJSON file on the **Saved Objects** page. -You can import dashboards from the [Saved Objects](../find-and-organize/saved-objects.md) page under **Stack Management**. +**Prerequisites** -When importing dashboards, you also import their related objects, such as data views and visualizations. Import options allow you to define how the import should behave with these related objects: +- An NDJSON file containing the dashboard and its related objects. Refer to [Share and export dashboards](sharing.md#export-dashboards) to produce it. +- **All** privilege for the **Dashboard** and **Saved Objects Management** features in {{product.kibana}}. +- Access to **Stack Management** in {{product.kibana}}. -* **Check for existing objects**: When selected, objects are not imported when another object with the same ID already exists in this space or cluster. For example, if you import a dashboard that uses a data view which already exists, the data view is not imported and the dashboard uses the existing data view instead. You can also choose to select manually which of the imported or the existing objects are kept by selecting **Request action on conflict**. -* **Create new objects with random IDs**: All related objects are imported and are assigned a new ID to avoid conflicts. +Import the dashboard from the [Saved Objects](../find-and-organize/saved-objects.md) page under **Stack Management**. When you import a dashboard, you also import its related objects, such as data views and visualizations. Import options control how the import handles these related objects: -![Import panel](/explore-analyze/images/kibana-dashboard-import-saved-object.png "") +- **Check for existing objects**: When selected, objects are not imported when another object with the same ID already exists in this space or cluster. For example, if you import a dashboard that uses a data view which already exists, the data view is not imported and the dashboard uses the existing data view instead. You can also choose which of the imported or existing objects to keep by selecting **Request action on conflict**. +- **Create new objects with random IDs**: All related objects are imported and are assigned a new ID to avoid conflicts. -:::: +![Import panel](/explore-analyze/images/kibana-dashboard-import-saved-object.png "") ::::: + +:::::: From f6e7ff4835f453c27bae548e781b4f9fa30fd62e Mon Sep 17 00:00:00 2001 From: Florent LB Date: Wed, 8 Jul 2026 19:34:02 +0200 Subject: [PATCH 4/8] docs: add API automation counterparts for NDJSON import and copy-to-space Point to the import saved objects API from the NDJSON tab and the copy saved objects to space API from the copy note, so every UI path also shows its programmatic form. Co-authored-by: Cursor --- explore-analyze/dashboards/import-dashboards.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/explore-analyze/dashboards/import-dashboards.md b/explore-analyze/dashboards/import-dashboards.md index f000ffaa13..b949153e82 100644 --- a/explore-analyze/dashboards/import-dashboards.md +++ b/explore-analyze/dashboards/import-dashboards.md @@ -17,7 +17,7 @@ Import a dashboard that was exported from another {{product.kibana}} space, inst - **NDJSON**: import it with the [Saved Objects API]({{kib-apis}}group/endpoint-saved-objects), or from the **Saved Objects** page. :::{note} -To move a dashboard to another space within the same deployment, you don't need to export and import it. Instead, [copy it to the target space](../find-and-organize/saved-objects.md#saved-objects-copy-to-other-spaces) from the **Saved Objects** page, together with its related objects. +To move a dashboard to another space within the same deployment, you don't need to export and import it. Instead, [copy it to the target space](../find-and-organize/saved-objects.md#saved-objects-copy-to-other-spaces) from the **Saved Objects** page, together with its related objects. To automate this, use the [copy saved objects to space API]({{kib-apis}}operation/operation-post-spaces-copy-saved-objects). ::: ::::::{tab-set} @@ -55,6 +55,8 @@ Import the dashboard from the [Saved Objects](../find-and-organize/saved-objects ![Import panel](/explore-analyze/images/kibana-dashboard-import-saved-object.png "") +To automate the import, use the [import saved objects API]({{kib-apis}}operation/operation-post-saved-objects-import) instead. + ::::: :::::: From 7a066815fb20a8a06e415005370f0151ce10df3a Mon Sep 17 00:00:00 2001 From: Florent LB Date: Wed, 8 Jul 2026 19:43:27 +0200 Subject: [PATCH 5/8] docs: move copy-to-space note below the import tabs Co-authored-by: Cursor --- explore-analyze/dashboards/import-dashboards.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/explore-analyze/dashboards/import-dashboards.md b/explore-analyze/dashboards/import-dashboards.md index b949153e82..922fa3a48e 100644 --- a/explore-analyze/dashboards/import-dashboards.md +++ b/explore-analyze/dashboards/import-dashboards.md @@ -16,10 +16,6 @@ Import a dashboard that was exported from another {{product.kibana}} space, inst - {applies_to}`stack: preview 9.4` {applies_to}`serverless: preview` **JSON**: import it with the [Dashboards API](create-dashboards-programmatically.md). This is the recommended method. - **NDJSON**: import it with the [Saved Objects API]({{kib-apis}}group/endpoint-saved-objects), or from the **Saved Objects** page. -:::{note} -To move a dashboard to another space within the same deployment, you don't need to export and import it. Instead, [copy it to the target space](../find-and-organize/saved-objects.md#saved-objects-copy-to-other-spaces) from the **Saved Objects** page, together with its related objects. To automate this, use the [copy saved objects to space API]({{kib-apis}}operation/operation-post-spaces-copy-saved-objects). -::: - ::::::{tab-set} :::::{tab-item} JSON (Dashboards API) @@ -60,3 +56,7 @@ To automate the import, use the [import saved objects API]({{kib-apis}}operation ::::: :::::: + +:::{note} +To move a dashboard to another space within the same deployment, you don't need to export and import it. Instead, [copy it to the target space](../find-and-organize/saved-objects.md#saved-objects-copy-to-other-spaces) from the **Saved Objects** page, together with its related objects. To automate this, use the [copy saved objects to space API]({{kib-apis}}operation/operation-post-spaces-copy-saved-objects). +::: From 9adc642abf334f75e07a05c28ddf1331a17eb365 Mon Sep 17 00:00:00 2001 From: Florent LB Date: Thu, 9 Jul 2026 14:18:20 +0200 Subject: [PATCH 6/8] docs: add intro section list to managing dashboards page Co-authored-by: Cursor --- explore-analyze/dashboards/managing.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/explore-analyze/dashboards/managing.md b/explore-analyze/dashboards/managing.md index 8d9a6d7400..a2fd31fb4d 100644 --- a/explore-analyze/dashboards/managing.md +++ b/explore-analyze/dashboards/managing.md @@ -13,6 +13,19 @@ products: Manage your collection of dashboards in {{product.kibana}} using search, filtering, and organization features that help you quickly find and track the dashboards you need. Whether you're working with a few dashboards or hundreds, these management tools help you stay organized and monitor dashboard usage across your team. +On this page, find and organize your dashboards: + +- [Browse dashboards](#find-dashboards): Search, filter, and sort your dashboard list. +- [Browse saved visualizations and annotation groups](#find-visualizations-annotation-groups): Open the Visualize Library. +- [Keep track of your favorite dashboards](#_keep_track_of_your_favorite_dashboards): Star dashboards to find them quickly. +- [View dashboard usage](#_view_dashboard_usage): Check how much a dashboard is viewed. + +To move dashboards between environments or manage them as code, refer to: + +- [Share and export dashboards](sharing.md): Share with your team using links or embeds, and export as PDF, PNG, CSV, or JSON. +- [Import a dashboard](import-dashboards.md): Bring a dashboard from another space, instance, deployment, or project into your own. +- [Manage dashboards as code](manage-dashboards-as-code.md): Version-control dashboards and deploy them across spaces, clusters, and stages. + ## Browse dashboards [find-dashboards] From 9735f2afa9458045a8ed120f77ac12502fc9ccd4 Mon Sep 17 00:00:00 2001 From: Florent LB Date: Thu, 9 Jul 2026 14:32:31 +0200 Subject: [PATCH 7/8] docs: sharpen on-page list descriptions in managing dashboards Co-authored-by: Cursor --- explore-analyze/dashboards/managing.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/explore-analyze/dashboards/managing.md b/explore-analyze/dashboards/managing.md index a2fd31fb4d..ce391bbe59 100644 --- a/explore-analyze/dashboards/managing.md +++ b/explore-analyze/dashboards/managing.md @@ -15,9 +15,9 @@ Manage your collection of dashboards in {{product.kibana}} using search, filteri On this page, find and organize your dashboards: -- [Browse dashboards](#find-dashboards): Search, filter, and sort your dashboard list. -- [Browse saved visualizations and annotation groups](#find-visualizations-annotation-groups): Open the Visualize Library. -- [Keep track of your favorite dashboards](#_keep_track_of_your_favorite_dashboards): Star dashboards to find them quickly. +- [Browse dashboards](#find-dashboards): Search, filter, and sort to quickly find the dashboards you need in a large collection. +- [Browse saved visualizations and annotation groups](#find-visualizations-annotation-groups): Manage the visualizations saved in the library that you can reuse across multiple dashboards. +- [Keep track of your favorite dashboards](#_keep_track_of_your_favorite_dashboards): Flag the dashboards you use often so you can access them faster. - [View dashboard usage](#_view_dashboard_usage): Check how much a dashboard is viewed. To move dashboards between environments or manage them as code, refer to: From 05cd7edb3baf33402f59852dd9eb90beec0fe0a3 Mon Sep 17 00:00:00 2001 From: Florent LB Date: Thu, 9 Jul 2026 14:52:14 +0200 Subject: [PATCH 8/8] docs: declare how-to content type on import dashboards page Co-authored-by: Cursor --- explore-analyze/dashboards/import-dashboards.md | 1 + 1 file changed, 1 insertion(+) diff --git a/explore-analyze/dashboards/import-dashboards.md b/explore-analyze/dashboards/import-dashboards.md index 922fa3a48e..317fa7baab 100644 --- a/explore-analyze/dashboards/import-dashboards.md +++ b/explore-analyze/dashboards/import-dashboards.md @@ -2,6 +2,7 @@ mapped_pages: - https://www.elastic.co/guide/en/kibana/current/_import_dashboards.html description: Import a Kibana dashboard exported from another space, instance, deployment, or project, using the Dashboards API or the Saved Objects API. +type: how-to applies_to: stack: ga serverless: ga