diff --git a/modules/end-user-guide/pages/starting-a-new-workspace-with-a-clone-of-a-git-repository.adoc b/modules/end-user-guide/pages/starting-a-new-workspace-with-a-clone-of-a-git-repository.adoc
index df9b1bc049..f18c8fcb83 100644
--- a/modules/end-user-guide/pages/starting-a-new-workspace-with-a-clone-of-a-git-repository.adoc
+++ b/modules/end-user-guide/pages/starting-a-new-workspace-with-a-clone-of-a-git-repository.adoc
@@ -15,7 +15,9 @@ TIP: You can also use the *Git Repository URL* field on the *Create Workspace* p
 
 [IMPORTANT]
 ====
-Starting a workspace using an HTTPS URL from a Git service other than GitHub, GiLab, Bitbucket, or Microsoft Azure DevOps will fail.
+* Starting a workspace using a URL from a Git service other than GitHub, GiLab, Bitbucket, or Microsoft Azure DevOps will fail.
+* If you use an SSH URL to start a new workspace, you must propagate the SSH key. See link:https://github.com/devfile/devworkspace-operator/blob/main/docs/additional-configuration.adoc#configuring-devworkspaces-to-use-ssh-keys-for-git-operations[Configuring DevWorkspaces to use SSH keys for Git operations] for more information.
+* If the SSH URL points to a private repository, you must apply an access token to be able to fetch the `devfile.yaml` content. You can do this either by accepting an SCM authentication page or following a xref:using-a-git-provider-access-token.adoc[Personal Access Token] procedure.
 ====
 
 [IMPORTANT]