diff --git a/docs/admin/authentication/roles.md b/docs/admin/authentication/roles.md
index 37f7659f01..a906a1c387 100644
--- a/docs/admin/authentication/roles.md
+++ b/docs/admin/authentication/roles.md
@@ -89,7 +89,14 @@ Run:ai supports the following roles and their permissions:
 ??? "Viewer"
     ![](img/roles-viewer.png)
 
-
+!!! Notes
+    Keep the following in mind when upgrading from versions 2.13 or earlier:
+
+    * **Admin** becomes **System Admin** with full access to all managed objects and scopes  
+    * **Research Manager** is not automatically assigned to all projects, but to projects set by the relevant **Admin** when assigning this role to a user, group or app  
+    * To preserve backwards compatibility, users with the role of **Research Manager** are assigned to all current projects, but not to new projects  
+    * To allow the **Department Admin** to assign a **Researcher** role to a user, group or app, the **Department Admin** must have **VECD** permissions for jobs and workspaces. This creates a broader span of managed objects  
+    * To preserve backwards compatibility, users with the role of **Editor**, are assigned to the same scope they had before the upgrade. However, with new user assignments, the **Admin** can limit the scope to only part of the organizational scope.
 
 ## Permitted workloads
 
diff --git a/docs/admin/runai-setup/cluster-setup/cluster-prerequisites.md b/docs/admin/runai-setup/cluster-setup/cluster-prerequisites.md
index f4999eb7a6..5d2f08d837 100644
--- a/docs/admin/runai-setup/cluster-setup/cluster-prerequisites.md
+++ b/docs/admin/runai-setup/cluster-setup/cluster-prerequisites.md
@@ -71,6 +71,8 @@ For existing Kubernetes clusters, see the following Kubernetes version support m
 
 | Run:ai version | Supported Kubernetes versions | Supported OpenShift versions |
 | :---- | :---- | :---- |
+| v2.13 | 1.23 to 1.28 | 4.10 to 4.13 |
+| v2.16 | 1.26 to 1.28 | 4.11 to 4.14 |
 | v2.17 | 1.27 to 1.29 | 4.12 to 4.15 |
 | v2.18 | 1.28 to 1.30 | 4.12 to 4.16 |
 | v2.19 | 1.28 to 1.31 | 4.12 to 4.17 |
diff --git a/docs/admin/runai-setup/cluster-setup/cluster-upgrade.md b/docs/admin/runai-setup/cluster-setup/cluster-upgrade.md
index f2fbdf2a7a..45f9dd6555 100644
--- a/docs/admin/runai-setup/cluster-setup/cluster-upgrade.md
+++ b/docs/admin/runai-setup/cluster-setup/cluster-upgrade.md
@@ -33,14 +33,27 @@ Follow the setup and installation instructions below to get the installation ins
 
 #### Installation instructions
 
-1. Follow the installation instructions 
-   run the Helm commands provided on your Kubernetes cluster (see the troubleshooting below if installation fails)  
+1. Follow the installation instructions (See the additional instructions below when [upgrading to v2.13](#upgrade-to-runai-cluster-version-213-old-release))  
+run the Helm commands provided on your Kubernetes cluster (see the troubleshooting below if installation fails)  
 2. Click **DONE**  
 3. Once installation is complete, validate the cluster is **Connected** and listed with the new cluster version (see the cluster troubleshooting scenarios). Once you have done this, the cluster is upgraded to the latest version.
 
 !!! Note
     To upgrade to a specific version, modify the `--version` flag by specifying the desired `<version-number>`. You can find all available versions by using the `helm search repo` command.
 
+## Upgrade to Run:ai cluster version 2.13 (old release)
+
+Run:ai cluster version 2.13 (old release) does not support migration of the configured Helm values. If you have customized configurations you want to migrate, follow the additional steps below:
+
+1. Download the Run:ai Helm values file by running the command provided in your terminal  
+2. Run the following command to save existing cluster Helm values into `old-values.yaml`
+
+``` bash
+helm get values runai-cluster -n runai > old-values.yaml
+```
+
+4. Identify configured custom values that you want to migrate  
+5. Manually merge the values from `old-values.yaml` into the new values file
 
 ## Troubleshooting
 
diff --git a/docs/admin/runai-setup/self-hosted/k8s/upgrade.md b/docs/admin/runai-setup/self-hosted/k8s/upgrade.md
index 16f5686813..e2cd34bdba 100644
--- a/docs/admin/runai-setup/self-hosted/k8s/upgrade.md
+++ b/docs/admin/runai-setup/self-hosted/k8s/upgrade.md
@@ -59,7 +59,7 @@ The Run:ai control-plane installation has been rewritten and is no longer using
 
 
 ## Upgrade Control Plane
-### Upgrade from version 2.17, or later
+### Upgrade from version 2.13, or later
 === "Connected"
 
     ``` bash
diff --git a/docs/admin/runai-setup/self-hosted/ocp/upgrade.md b/docs/admin/runai-setup/self-hosted/ocp/upgrade.md
index e70036b706..0cfdbe305f 100644
--- a/docs/admin/runai-setup/self-hosted/ocp/upgrade.md
+++ b/docs/admin/runai-setup/self-hosted/ocp/upgrade.md
@@ -49,7 +49,7 @@ The Run:ai control-plane installation has been rewritten and is no longer using
 * Search for the customizations you found in the [optional configurations](./backend.md#additional-runai-configurations-optional) table and add them in the new format.  
 
 ## Upgrade Control Plane
-### Upgrade from version 2.17, or later
+### Upgrade from version 2.13, or later
 === "Connected"
 
     ``` bash