refactor: further duplicate guidance

- Additionally add a screenshot on how to duplicate an existing dashboard [skip pizza]
theopensystemslab · Nov 15, 2023 · 36c75f9 · 36c75f9
1 parent ba88df1
commit 36c75f9
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 1 deletion.
diff --git a/doc/how-to/how-to-setup-metabase-for-a-new-team.md b/doc/how-to/how-to-setup-metabase-for-a-new-team.md
@@ -15,9 +15,13 @@ Metabase is set up and running on both Staging and Production environments, but
 
 3. Duplicate existing Dashboards (FOIYNPP, LDC) from an existing team, renaming them and adding to new Collection.
 
+![Screenshot - Duplicate and existing dashboard](./images/setup-metabase/duplicate_an_existing_dashboard.png)
+
+   * Not all teams host the same services on PlanX. Ensure you only duplicate Dashboards for which teams have an associated flows. This can be checked via the PlanX Editor.
+
 ![Screenshot - Only duplicate the dashboard](./images/setup-metabase/only_duplicate_dashboard.png)
 
-   * Not all teams host the same services on PlanX. Ensure you only duplicate Dashboards for which teams have an associated flows. This can be checked via the PlanX Editor
+   * Ensure "Only duplicate the dashboard" is selected. This avoids unecessarily duplicating the visualisations which we maintain.
 
 4. Navigate to the new Collection, and edit each Dashboard to update the FlowID variable.
 

diff --git a/doc/how-to/images/setup-metabase/duplicate_an_existing_dashboard.png b/doc/how-to/images/setup-metabase/duplicate_an_existing_dashboard.png