diff --git a/modules/administration-guide/nav.adoc b/modules/administration-guide/nav.adoc
index 6b19ae5c1f..e8c2df46fe 100644
--- a/modules/administration-guide/nav.adoc
+++ b/modules/administration-guide/nav.adoc
@@ -41,6 +41,7 @@
 *** xref:configuring-workspace-target-namespace.adoc[]
 *** xref:provisioning-namespaces-in-advance.adoc[]
 *** xref:configuring-a-user-namespace.adoc[]
+*** xref:configuring-direct-namespace-creation-on-openshift.adoc[]
 ** xref:configuring-server-components.adoc[]
 *** xref:mounting-a-secret-as-a-file-or-an-environment-variable-into-a-container.adoc[]
 *** xref:advanced-configuration-options-for-the-che-server-component.adoc[]
diff --git a/modules/administration-guide/pages/configuring-direct-namespace-creation-on-openshift.adoc b/modules/administration-guide/pages/configuring-direct-namespace-creation-on-openshift.adoc
new file mode 100644
index 0000000000..ca885b065f
--- /dev/null
+++ b/modules/administration-guide/pages/configuring-direct-namespace-creation-on-openshift.adoc
@@ -0,0 +1,39 @@
+:_content-type: PROCEDURE
+:description: Configuring {prod-short} to create standard {orch-namespace}s instead of {ocp} projects
+:keywords: administration guide, configuring, namespace, openshift, project
+:navtitle: Configuring direct {orch-namespace} creation on {ocp}
+:page-aliases:
+
+[id="configuring-direct-namespace-creation-on-openshift"]
+= Configuring direct {orch-namespace} creation on {ocp}
+
+By default, on {ocp} clusters, {prod-short} uses the OpenShift ProjectRequest API to create user {orch-namespace}s.
+The ProjectRequest API triggers any cluster-specific Project Templates configured by the cluster administrator.
+
+If you want {prod-short} to create standard {kubernetes} {orch-namespace}s directly, bypassing the ProjectRequest API and its associated Project Templates, you can enable the `createNamespaceDirectly` option.
+
+.Prerequisites
+
+* An active `{prod-cli}` session with administrative permissions to the destination {ocp} cluster. See xref:installing-the-chectl-management-tool.adoc[].
+
+.Procedure
+
+* Configure the `CheCluster` Custom Resource. See xref:using-the-cli-to-configure-the-checluster-custom-resource.adoc[].
++
+[source,yaml,subs="+quotes,+attributes"]
+----
+spec:
+  devEnvironments:
+    defaultNamespace:
+      createNamespaceDirectly: true
+----
+
+.Verification
+
+* Start a workspace and verify that {prod-short} creates a standard {kubernetes} {orch-namespace} instead of an {ocp} project.
+
+.Additional resources
+
+* xref:configuring-namespace-provisioning.adoc[]
+
+* xref:using-the-cli-to-configure-the-checluster-custom-resource.adoc[]
diff --git a/modules/administration-guide/pages/configuring-namespace-provisioning.adoc b/modules/administration-guide/pages/configuring-namespace-provisioning.adoc
index 0502e2f333..395587a338 100644
--- a/modules/administration-guide/pages/configuring-namespace-provisioning.adoc
+++ b/modules/administration-guide/pages/configuring-namespace-provisioning.adoc
@@ -15,4 +15,5 @@ You can modify {prod-short} behavior by:
 
 * xref:configuring-workspace-target-namespace.adoc[]
 * xref:provisioning-namespaces-in-advance.adoc[]
-* xref:configuring-a-user-namespace.adoc[]
\ No newline at end of file
+* xref:configuring-a-user-namespace.adoc[]
+* xref:configuring-direct-namespace-creation-on-openshift.adoc[]
\ No newline at end of file