diff --git a/docs/topics/developer-lightspeed/con_developer-lightspeed-pathways.adoc b/docs/topics/developer-lightspeed/con_developer-lightspeed-pathways.adoc
index a7fb02f4..c550eecc 100644
--- a/docs/topics/developer-lightspeed/con_developer-lightspeed-pathways.adoc
+++ b/docs/topics/developer-lightspeed/con_developer-lightspeed-pathways.adoc
@@ -53,7 +53,7 @@ As an Administrator, you must complete the following workflow to enable the LLM
 
 * Create a xref:tackle-llm-secret_getting-started[secret] for your LLM key in the Red Hat {ocp-name} cluster.
 
-* In the xref:tackle-enable-llm-proxy_getting-started[Tackle custom resource (CR)], enable the LLM proxy service, enable the Solution Server if you want Migrators to use the Solution Server mode, and configure the LLM provider and the LLM model.
+* In the xref:tackle-enable-llm-proxy_getting-started[Tackle custom resource (CR)], enable the LLM proxy service, enable the Solution Server if you want Migrators to use the Solution Server mode, and configure the LLM provider, the LLM model, and the LLM base URL.
 
 As a Migrator, you can:
 
diff --git a/docs/topics/developer-lightspeed/proc_tackle-enable-llm-proxy.adoc b/docs/topics/developer-lightspeed/proc_tackle-enable-llm-proxy.adoc
index 8ae66e13..da245bf6 100644
--- a/docs/topics/developer-lightspeed/proc_tackle-enable-llm-proxy.adoc
+++ b/docs/topics/developer-lightspeed/proc_tackle-enable-llm-proxy.adoc
@@ -3,7 +3,7 @@
 :_mod-docs-content-type: PROCEDURE
 
 [id="tackle-enable-llm-proxy_{context}"]
-= Enabling LLM proxy in the Tackle custom resource
+= Configuring the Tackle custom resource
 
 [role="_abstract"]
 To use the LLM proxy service, you must enable the proxy in the Tackle custom resource (CR) and deploy it in the Red Hat {ocp-name} project where you installed the {ProductShortName} Operator.
@@ -33,7 +33,8 @@ To use the Solution Server, the Administrator must enable it in the Tackle CR al
 vi tackle
 ----
 
-. Enable `kai_llm_proxy_enabled` in the Tackle CR:
+. Complete one of the following Tackle configurations:
+.. Enable LLM proxy and optionally the Solution Server in the Tackle CR:
 +
 [source, yaml]
 ----
@@ -49,9 +50,26 @@ spec:
   kai_llm_provider: <provider-name> #For example, OpenAI.
   # optional, pick a suitable model for your provider
   kai_llm_model: <model-name>
+  kai_llm_baseurl: "https://<serving-name>-<data-science-project-name>.apps.mta-ai.example.com/v1"
+---
+----
+.. Enter the LLM configurations in the Tackle CR without the proxy service:
++
+[source, yaml]
+----
+---
+kind: Tackle
+apiVersion: tackle.konveyor.io/v1alpha1
+metadata:
+  name: mta
+  namespace: openshift-mta
+spec:
+  kai_llm_provider: <provider-name> #For example, OpenAI.
+  # optional, pick a suitable model for your provider
+  kai_llm_model: <model-name>
+  kai_llm_baseurl: "https://<serving-name>-<data-science-project-name>.apps.mta-ai.example.com/v1"
 ---
 ----
-
 . Save the Tackle CR configuration.
 
 . Apply the Tackle CR in the `openshift-mta` project: