diff --git a/software/dashboard/docs/csv-import.md b/software/dashboard/docs/csv-import.md
index 48d7413..304c734 100644
--- a/software/dashboard/docs/csv-import.md
+++ b/software/dashboard/docs/csv-import.md
@@ -23,6 +23,6 @@ As the CSV is reachable by Grafana, you can create a data source, there.
 Whith Grafana having access to data in the CSV file, it's easy to access this data to create a dashboard.
 
 ![Using CSV data](./images/grafana-csv-data.png)
-
+![Defining types](./images/grafana-csv-data-type.png)
 
 
diff --git a/software/dashboard/docs/images/grafana-csv-data-type.png b/software/dashboard/docs/images/grafana-csv-data-type.png
new file mode 100644
index 0000000..c243520
Binary files /dev/null and b/software/dashboard/docs/images/grafana-csv-data-type.png differ
diff --git a/software/dashboard/grafana/grafana.db b/software/dashboard/grafana/grafana.db
index bb7cf6e..4411342 100644
Binary files a/software/dashboard/grafana/grafana.db and b/software/dashboard/grafana/grafana.db differ
diff --git a/software/flow/.config.users.json b/software/flow/.config.users.json
index bbed7a1..77dff85 100644
--- a/software/flow/.config.users.json
+++ b/software/flow/.config.users.json
@@ -6,7 +6,7 @@
                 "view-store-position": false,
                 "view-show-grid": true,
                 "view-snap-grid": true,
-                "view-grid-size": 20,
+                "view-grid-size": "20",
                 "view-node-status": true,
                 "view-node-show-label": true,
                 "view-show-tips": true,
@@ -15,6 +15,15 @@
             "tours": {
                 "welcome": "3.0.2"
             }
+        },
+        "git": {
+            "user": {
+                "name": "",
+                "email": ""
+            },
+            "workflow": {
+                "mode": "manual"
+            }
         }
     }
 }
\ No newline at end of file
diff --git a/software/flow/.config.users.json.backup b/software/flow/.config.users.json.backup
index c6bcd30..bbed7a1 100644
--- a/software/flow/.config.users.json.backup
+++ b/software/flow/.config.users.json.backup
@@ -11,6 +11,9 @@
                 "view-node-show-label": true,
                 "view-show-tips": true,
                 "view-show-welcome-tours": true
+            },
+            "tours": {
+                "welcome": "3.0.2"
             }
         }
     }
diff --git a/software/flow/README.md b/software/flow/README.md
index db10de4..ab41bc4 100644
--- a/software/flow/README.md
+++ b/software/flow/README.md
@@ -21,6 +21,16 @@ A node can:
 
 Flows are an organized sequence of nodes. Let's do the "first steps" by creating a simple flow.
 
+## Plugins
+
+> The plugin folder is pushed into this Git repository and is mounted in Docker. Maybe we should use an own Docker file, instead.
+
+Node-RED uses plugins (e.g. for Grafana, InfluxDB or own Dashboard capabilites).
+
+You can access the plugins in the right burger menu.
+
+![Plugins](./docs/images/node-red-plugins.png)
+
 ## First steps
 
 For debuging I already added Node-RED's own dashboard (sure, we are going to use Grafana, later).
diff --git a/software/flow/docs/images/node-red-plugins.png b/software/flow/docs/images/node-red-plugins.png
new file mode 100644
index 0000000..62a84ef
Binary files /dev/null and b/software/flow/docs/images/node-red-plugins.png differ