diff --git a/website/versioned_docs/version-0.31.2/cluster-management/img/hr-selection.png b/website/versioned_docs/version-0.31.2/cluster-management/img/hr-selection.png
new file mode 100644
index 0000000000..d32b58d42e
Binary files /dev/null and b/website/versioned_docs/version-0.31.2/cluster-management/img/hr-selection.png differ
diff --git a/website/versioned_docs/version-0.31.2/cluster-management/img/profile-selection.png b/website/versioned_docs/version-0.31.2/cluster-management/img/profile-selection.png
deleted file mode 100644
index 4f0243b070..0000000000
Binary files a/website/versioned_docs/version-0.31.2/cluster-management/img/profile-selection.png and /dev/null differ
diff --git a/website/versioned_docs/version-0.31.2/cluster-management/img/profiles-selection.png b/website/versioned_docs/version-0.31.2/cluster-management/img/profiles-selection.png
new file mode 100644
index 0000000000..e7e8ca2fe8
Binary files /dev/null and b/website/versioned_docs/version-0.31.2/cluster-management/img/profiles-selection.png differ
diff --git a/website/versioned_docs/version-0.31.2/cluster-management/profiles.mdx b/website/versioned_docs/version-0.31.2/cluster-management/profiles.mdx
index eafac7637c..17c4b8af13 100644
--- a/website/versioned_docs/version-0.31.2/cluster-management/profiles.mdx
+++ b/website/versioned_docs/version-0.31.2/cluster-management/profiles.mdx
@@ -134,11 +134,15 @@ spec:
 
 ### Select the Profiles You Want Installed at Cluster Creation
 
-WGE inspects the namespace in the management cluster where it is deployed, and looks for a `HelmRepository` object named `weaveworks-charts`. This Kubernetes object should point to a Helm chart repository that includes the Profiles available for installation.
+WGE inspects the namespace in the management cluster where it is deployed, and looks for `HelmRepository` objects. These Kubernetes objects should point to Helm chart repositories that include the Profiles available for installation.
 
-When creating a cluster from the UI using a CAPI template, these Profiles are available for selection in the `Profiles` section of the template. For example:
+When creating a cluster from the UI using a CAPI template, these Helm Repositories together with their Profiles are available for selection in the `Profiles` section of the template. For example:
 
-![Profiles Selection](./img/profile-selection.png)
+![HelmRepositories Selection](./img/hr-selection.png)
+
+The helm repositories selection will filter down the profiles available for selection at the next step.
+
+![Profiles Selection](./img/profiles-selection.png)
 
 As shown above, some Profiles are optional, while others are required. This is determined when the template is authored and allows for operations teams to control which Helm packages should be installed on new clusters by default.
 
diff --git a/website/versioned_docs/version-0.31.2/gitops-templates/profiles.mdx b/website/versioned_docs/version-0.31.2/gitops-templates/profiles.mdx
index 77a4e6d06d..8cb39b5e87 100644
--- a/website/versioned_docs/version-0.31.2/gitops-templates/profiles.mdx
+++ b/website/versioned_docs/version-0.31.2/gitops-templates/profiles.mdx
@@ -22,8 +22,14 @@ spec:
         targetNamespace: nginx
       - name: cert-manager
         targetNamespace: cert-manager
+        sourceRef:
+          kind: HelmRepository
+          name: podinfo
+          namespace: default
 ```
 
+For each profile, a sourceRef can be specified. This is the name/namespace reference to the HelmRepository where the profile can be found. The HelmRepository must be present on the rendering cluster. If this is not provided, `weaveworks-charts` is used by default. 
+
 A template with the above profiles would offer Application Developers the option
 to add `nginx` and `cert-manager` resources to their templated resources, ready
 for deployment to their cluster.