diff --git a/modules/administration-guide/pages/proc_deploy-open-vsx-from-workspace.adoc b/modules/administration-guide/pages/proc_deploy-open-vsx-from-workspace.adoc
index 5849db8e77..d08cc4a012 100644
--- a/modules/administration-guide/pages/proc_deploy-open-vsx-from-workspace.adoc
+++ b/modules/administration-guide/pages/proc_deploy-open-vsx-from-workspace.adoc
@@ -29,6 +29,9 @@ The link:https://github.com/eclipse-openvsx/openvsx/blob/master/.devfile.yaml[.d
 The environment, including all necessary commands, is defined in the `.devfile.yaml` file.
 ====
 
+. Login to the cluster as a cluster administrator from the workspace terminal:
+.. Navigate to *Terminal* -> *New Terminal*
+.. Execute: `$ oc login --token=<USER_TOKEN> --server=<CLUSTER_API_URL>`
 . Create a new project for Open VSX.
 +
 Run the `2.1. Create Namespace for OpenVSX` task in the workspace:
diff --git a/modules/administration-guide/partials/proc_adding-or-removing-extensions-in-a-workspace.adoc b/modules/administration-guide/partials/proc_adding-or-removing-extensions-in-a-workspace.adoc
index 2752403abf..bb051b047e 100644
--- a/modules/administration-guide/partials/proc_adding-or-removing-extensions-in-a-workspace.adoc
+++ b/modules/administration-guide/partials/proc_adding-or-removing-extensions-in-a-workspace.adoc
@@ -13,8 +13,8 @@ The embedded plugin registry is deprecated. Setting up an internal, on-premises
 
 .Prerequisites
 
-* You are logged in to your {prod-short} instance as an administrator.
 * You have started a workspace using the link:{plugin-registry-repo-url}[plugin registry repository].
+* You are logged in to the cluster as a cluster administrator from the workspace terminal: `$ oc login --token=<USER_TOKEN> --server=<CLUSTER_API_URL>`
 * You have created a link:https://access.redhat.com/terms-based-registry/[Red Hat Registry Service Account] and have the username and token available.
 * For IBM Power (`ppc64le`) and IBM Z (`s390x`) architectures, you must build the custom plugin registry locally on the corresponding hardware.
 * (Optional) You can rebuild the container based on the latest tag or SHA to get the latest security fixes after a {prod-short} update.