diff --git a/getting-started/deployment/local.mdx b/getting-started/deployment/local.mdx
index b26a583..9c62ac0 100644
--- a/getting-started/deployment/local.mdx
+++ b/getting-started/deployment/local.mdx
@@ -29,8 +29,8 @@ If you can't use the autoinstall script, follow the manual installation steps fo
 2. Open a new terminal window and run the following command to create a folder and download the OpenOps release files:
     ```shell
     mkdir -p openops && cd openops && \
-    curl -OL https://github.com/openops-cloud/openops/releases/download/0.6.13/openops-dc-0.6.13.zip && \
-    unzip openops-dc-0.6.13.zip && cp -n .env.defaults .env
+    curl -OL https://github.com/openops-cloud/openops/releases/download/0.6.14/openops-dc-0.6.14.zip && \
+    unzip openops-dc-0.6.14.zip && cp -n .env.defaults .env
    ```
 3. <UpdateCredentials/>
 4. Pull the images and run `docker compose`:
@@ -54,13 +54,13 @@ You can now access the application by navigating to http://localhost.
     # create and change directory
     mkdir -p openops && cd openops
     # download the release file
-    curl -OL https://github.com/openops-cloud/openops/releases/download/0.6.13/openops-dc-0.6.13.zip
+    curl -OL https://github.com/openops-cloud/openops/releases/download/0.6.14/openops-dc-0.6.14.zip
     # refresh package lists
     sudo apt update
     # install unzip
     sudo apt install unzip
     # decompress release file
-    unzip openops-dc-0.6.13.zip
+    unzip openops-dc-0.6.14.zip
     # copy the defaults to env without overwriting existing files
     cp --update=none .env.defaults .env
     ```
@@ -99,8 +99,8 @@ You can now access the application by navigating to http://localhost.
     ```
 3. Download the OpenOps release files:
     ```powershell
-    Invoke-WebRequest -Uri "https://github.com/openops-cloud/openops/releases/download/0.6.13/openops-dc-0.6.13.zip"
-    Expand-Archive -Path "openops-dc-0.6.13.zip" -DestinationPath .
+    Invoke-WebRequest -Uri "https://github.com/openops-cloud/openops/releases/download/0.6.14/openops-dc-0.6.14.zip"
+    Expand-Archive -Path "openops-dc-0.6.14.zip" -DestinationPath .
     if (-Not (Test-Path ".env")) {
         Copy-Item ".env.defaults" ".env"
     }
diff --git a/getting-started/updating-openops.mdx b/getting-started/updating-openops.mdx
index 01ff448..0da1147 100644
--- a/getting-started/updating-openops.mdx
+++ b/getting-started/updating-openops.mdx
@@ -28,8 +28,8 @@ The script will stop all running containers, pull the latest images, and restart
     ```
 4. Download and extract the new version:
     ```shell
-    curl -OL https://github.com/openops-cloud/openops/releases/download/0.6.13/openops-dc-0.6.13.zip && \
-    unzip -o openops-dc-0.6.13.zip
+    curl -OL https://github.com/openops-cloud/openops/releases/download/0.6.14/openops-dc-0.6.14.zip && \
+    unzip -o openops-dc-0.6.14.zip
     ```
     (This code sample refers to a specific version. Don't forget to update it to the version you're installing.)
 5. Fetch the new images and restart the application:
diff --git a/reporting-analytics/analytics.mdx b/reporting-analytics/analytics.mdx
index f7e1b16..7a9f66a 100644
--- a/reporting-analytics/analytics.mdx
+++ b/reporting-analytics/analytics.mdx
@@ -11,11 +11,25 @@ You can visualize data that you collect with [OpenOps tables](/reporting-analyti
 
 In addition to OpenOps tables, OpenOps Analytics can connect to and visualize your existing data sources, such as CSV files, Google Sheets, Postgres databases, and more.
 
+## Prerequisites
+
+* OpenOps Analytics must be deployed and reachable by the OpenOps app.
+* You need the admin password for the Analytics portal (configured with `OPS_ANALYTICS_ADMIN_PASSWORD`).
+
+If Analytics is not deployed for your environment, the OpenOps app can still run, but the **Analytics** view is not available.
+
+## Analytics seeding behavior
+
+OpenOps runs an internal Analytics seeding step during startup.
+
+* If `OPS_ANALYTICS_PRIVATE_URL` is not configured, the seeding step is skipped.
+* If the `SHOW_DEMO_HOME_PAGE` flag is not enabled, seeding the demo **Homepage** dashboard is skipped.
+
 ## Analytics admin portal
 
 To configure data visualizations, click **Analytics** on the main navigation bar in OpenOps. When the **Analytics** view opens, click **Admin Panel** to proceed to the Analytics admin portal that is separate from the main OpenOps application.
 
-To sign in to the Analytics portal, use `admin` as the username and the password defined with the `OPS_ANALYTICS_ADMIN_PASSWORD` variable in the `.env` file in your OpenOps installation folder. (If you haven’t changed the password, the default is `please-change-this-password-1`.)
+To sign in to the Analytics portal, use `admin` as the username and the password defined with the `OPS_ANALYTICS_ADMIN_PASSWORD` variable in the `.env` file in your OpenOps installation folder. (If you haven't changed the password, the default is `please-change-this-password-1`.)
 
 <Note>
 If you don't have access to the OpenOps installation folder: