diff --git a/_docs/runtime/monitor-manage-runtimes.md b/_docs/runtime/monitor-manage-runtimes.md
index 875b3703..d985199c 100644
--- a/_docs/runtime/monitor-manage-runtimes.md
+++ b/_docs/runtime/monitor-manage-runtimes.md
@@ -27,8 +27,9 @@ Select the view mode to view runtime components and information, and manage prov
 
 
 Manage provisioned runtimes: 
-* [Add managed clusters to hybrid or hosted runtimes]({{site.baseurl}}/docs/runtime/managed-cluster/))
-* [Add and manage Git Sources associated with hybrid or hosted runtimes]({{site.baseurl}}/docs/runtime/git-sources/))
+* [Add managed clusters to hybrid or hosted runtimes]({{site.baseurl}}/docs/runtime/managed-cluster/)
+* [Add and manage Git Sources associated with hybrid or hosted runtimes]({{site.baseurl}}/docs/runtime/git-sources/)
+* [Reset shared configuration repository](#reset-shared-configuration-repository)
 * [Upgrade provisioned hybrid runtimes](#hybrid-upgrade-provisioned-runtimes)
 * [Upgrade Codefresh CLI](#upgrade-codefresh-cli)
 * [Uninstall provisioned runtimes](#uninstall-provisioned-runtimes)
@@ -99,6 +100,24 @@ Here is a description of the information in the Topology view.
 |**Health/Sync status** |The health and sync status of the runtime or cluster. {::nomarkdown}<ul><li><img src="../../../images/icons/error.png" display="inline-block"> indicates health or sync errors in the runtime, or a managed cluster if one was added to the runtime.</br> The runtime or cluster node is bordered in red and the name is colored red.</li> <li><img src="../../../images/icons/cf-sync-status.png" display=inline-block/> indicates that the runtime is being synced to the cluster on which it is provisioned.</li></ul> {:/} |
 |**Search and View options** | {::nomarkdown}<ul><li>Find a runtime or its clusters by typing part of the runtime/cluster name, and then navigate to the entries found. </li> <li>Topology view options: Resize to window, zoom in, zoom out, full screen view.</li></ul> {:/}|
 
+### Reset shared configuration repository
+Codefresh creates the [shared configuration repository]({{site.baseurl}}/docs/reference/shared-configuration) when you install the first hybrid or hosted GitOps runtime for your account, and uses it for all runtimes you add to the same account.
+
+If needed, you can reset the location of the shared configuration repository in your account and re-initialize it. For example, when moving from evaluation to production.  
+Uninstall all the existing runtimes in your account, and then run the reset command. On the next installation, Codefresh re-initializes the shared configuration repo.
+ 
+
+>Reset shared configuration repo is supported from CLI v0.1.18 and higher.
+
+
+**Before you begin**   
+[Uninstall every runtime in the account](#uninstall-provisioned-runtimes)
+
+**How to**  
+* Run:  
+  `cf config --reset-shared-config-repo`
+
+
 
 ### Upgrade Codefresh CLI
 The Codefresh CLI automatically self-checks its version, and if a newer version is available, prints a banner with the notification.