diff --git a/ingestion/src/metadata/profiler/orm/functions/datetime.py b/ingestion/src/metadata/profiler/orm/functions/datetime.py
index cf0d94b649c..e4d6da01ebc 100644
--- a/ingestion/src/metadata/profiler/orm/functions/datetime.py
+++ b/ingestion/src/metadata/profiler/orm/functions/datetime.py
@@ -188,7 +188,7 @@ def _(elements, compiler, **kwargs):  # pylint: disable=unused-argument
             "Bigquery does not support `month` or `year` interval for table partitioned on timestamp",
             "field types. You can set the `interval_unit to day or hour directly from OpenMetadata UI`."
             # pylint: disable=line-too-long
-            "Visit https://docs.open-metadata.org/connectors/ingestion/workflows/profiler#4-updating-profiler-setting-at-the-table-level for more details.",
+            "Visit https://docs.open-metadata.org/how-to-guides/data-quality-observability/profiler/workflow#4-updating-profiler-setting-at-the-table-level for more details.",
         )
 
     return (
diff --git a/ingestion/src/metadata/workflow/output_handler.py b/ingestion/src/metadata/workflow/output_handler.py
index a8c0e6000d0..8f429f798c9 100644
--- a/ingestion/src/metadata/workflow/output_handler.py
+++ b/ingestion/src/metadata/workflow/output_handler.py
@@ -63,7 +63,7 @@ EXAMPLES_WORKFLOW_PATH: Path = Path(__file__).parent / "../examples" / "workflow
 
 URLS = {
     WorkflowType.INGEST: "https://docs.open-metadata.org/connectors/ingestion/workflows/metadata",
-    WorkflowType.PROFILE: "https://docs.open-metadata.org/connectors/ingestion/workflows/profiler",
+    WorkflowType.PROFILE: "https://docs.open-metadata.org/how-to-guides/data-quality-observability/profiler/workflow",
     WorkflowType.TEST: "https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality",
     WorkflowType.LINEAGE: "https://docs.open-metadata.org/connectors/ingestion/workflows/lineage",
     WorkflowType.USAGE: "https://docs.open-metadata.org/connectors/ingestion/workflows/usage",
diff --git a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/BigQuery.md b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/BigQuery.md
index 0dcc060daea..a1cbaf9414f 100644
--- a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/BigQuery.md
+++ b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/BigQuery.md
@@ -39,7 +39,7 @@ You can find further information on the BigQuery connector in the [docs](https:/
 
 
 ### Profiler & Data Quality
-Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. The user should also be allowed to view information in `table_storage` for all objects in the database. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/connectors/ingestion/workflows/profiler) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
+Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. The user should also be allowed to view information in `table_storage` for all objects in the database. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/how-to-guides/data-quality-observability/profiler/workflow) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
 
 ## Connection Details
 
diff --git a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Clickhouse.md b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Clickhouse.md
index 01e483024a0..c951fa21177 100644
--- a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Clickhouse.md
+++ b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Clickhouse.md
@@ -22,7 +22,7 @@ GRANT SELECT ON <schema_name>.* to <username>;
 
 ### Profiler & Data Quality
 
-Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. The user should also be allowed to view information in `tables` for all objects in the database. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/connectors/ingestion/workflows/profiler) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
+Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. The user should also be allowed to view information in `tables` for all objects in the database. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/how-to-guides/data-quality-observability/profiler/workflow) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
 
 ### Usage & Lineage
 
diff --git a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Db2.md b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Db2.md
index 8c16513bc94..da50e3321a8 100644
--- a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Db2.md
+++ b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Db2.md
@@ -28,7 +28,7 @@ GRANT SELECT ON SYSCAT.VIEWS TO USER_NAME;
 
 ### Profiler & Data Quality
 
-Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/connectors/ingestion/workflows/profiler) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
+Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/how-to-guides/data-quality-observability/profiler/workflow) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
 
 You can find further information on the DB2 connector in the [docs](https://docs.open-metadata.org/connectors/database/db2).
 
diff --git a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Greenplum.md b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Greenplum.md
index 8bb2adf75e8..3ad908a7005 100644
--- a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Greenplum.md
+++ b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Greenplum.md
@@ -6,7 +6,7 @@ In this section, we provide guides and references to use the Greenplum connector
 
 ### Profiler & Data Quality
 
-Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/connectors/ingestion/workflows/profiler) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
+Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/how-to-guides/data-quality-observability/profiler/workflow) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
 
 You can find further information on the Greenplum connector in the [docs](https://docs.open-metadata.org/connectors/database/greenplum).
 
diff --git a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Hive.md b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Hive.md
index 24113faf9fa..33f75c22232 100644
--- a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Hive.md
+++ b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Hive.md
@@ -5,7 +5,7 @@ In this section, we provide guides and references to use the Hive connector. You
 To extract metadata, the user used in the connection needs to be able to perform `SELECT`, `SHOW`, and `DESCRIBE` operations in the database/schema where the metadata needs to be extracted from.
 
 ### Profiler & Data Quality
-Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/connectors/ingestion/workflows/profiler) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
+Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/how-to-guides/data-quality-observability/profiler/workflow) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
 
 You can find further information on the Hive connector in the [docs](https://docs.open-metadata.org/connectors/database/hive).
 
diff --git a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Impala.md b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Impala.md
index 6ab542aac6e..c6dbbaa67d5 100644
--- a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Impala.md
+++ b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Impala.md
@@ -5,7 +5,7 @@ In this section, we provide guides and references to use the Impala connector. Y
 To extract metadata, the user used in the connection needs to be able to perform `SELECT`, `SHOW`, and `DESCRIBE` operations in the database/schema where the metadata needs to be extracted from.
 
 ### Profiler & Data Quality
-Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/connectors/ingestion/workflows/profiler) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
+Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/how-to-guides/data-quality-observability/profiler/workflow) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
 
 You can find further information on the Impala connector in the [docs](https://docs.open-metadata.org/connectors/database/impala).
 
diff --git a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/MariaDB.md b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/MariaDB.md
index bbf6fc6737b..defc551007c 100644
--- a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/MariaDB.md
+++ b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/MariaDB.md
@@ -21,7 +21,7 @@ GRANT SELECT ON world.hello TO '<username>';
 ```
 
 ### Profiler & Data Quality
-Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/connectors/ingestion/workflows/profiler) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
+Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/how-to-guides/data-quality-observability/profiler/workflow) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
 
 You can find further information on the MariaDB connector in the [docs](https://docs.open-metadata.org/connectors/database/mariadb).
 
diff --git a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Mssql.md b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Mssql.md
index 4da34220c5b..9bbc95ca01b 100644
--- a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Mssql.md
+++ b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Mssql.md
@@ -15,7 +15,7 @@ GRANT SELECT TO Mary;
 ```
 
 ### Profiler & Data Quality
-Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/connectors/ingestion/workflows/profiler) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
+Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/how-to-guides/data-quality-observability/profiler/workflow) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
 
 ### Usage & Lineage
 For the usage and lineage workflow, the user will need `SELECT` privilege table. You can find more information on the usage workflow [here](https://docs.open-metadata.org/connectors/ingestion/workflows/usage) and the lineage workflow [here](https://docs.open-metadata.org/connectors/ingestion/workflows/lineage).
diff --git a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Mysql.md b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Mysql.md
index cba04f4cca1..6d766c53ad7 100644
--- a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Mysql.md
+++ b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Mysql.md
@@ -25,7 +25,7 @@ OpenMetadata supports MySQL version `8.0.0` and up.
 $$
 
 ### Profiler & Data Quality
-Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. The user should also be allowed to view information in `tables` for all objects in the database. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/connectors/ingestion/workflows/profiler) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
+Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. The user should also be allowed to view information in `tables` for all objects in the database. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/how-to-guides/data-quality-observability/profiler/workflow) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
 
 You can find further information on the MySQL connector in the [docs](https://docs.open-metadata.org/connectors/database/mysql).
 
diff --git a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Oracle.md b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Oracle.md
index 56986ad15bf..3ed062d5aa6 100644
--- a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Oracle.md
+++ b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Oracle.md
@@ -34,7 +34,7 @@ GRANT SELECT ON table_name TO {user | role};
 ```
 
 ### Profiler & Data Quality
-Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. The user should also be allowed to view information in `all_objects` and `all_tables` for all objects in the database. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/connectors/ingestion/workflows/profiler) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
+Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. The user should also be allowed to view information in `all_objects` and `all_tables` for all objects in the database. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/how-to-guides/data-quality-observability/profiler/workflow) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
 
 ### Usage & Lineage
 For the usage and lineage workflow, the user will need `SELECT` privilege. You can find more information on the usage workflow [here](https://docs.open-metadata.org/connectors/ingestion/workflows/usage) and the lineage workflow [here](https://docs.open-metadata.org/connectors/ingestion/workflows/lineage).
diff --git a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Postgres.md b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Postgres.md
index 199c5300d20..661071d4041 100644
--- a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Postgres.md
+++ b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Postgres.md
@@ -10,7 +10,7 @@ $$
 
 ### Profiler & Data Quality
 
-Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/connectors/ingestion/workflows/profiler) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
+Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/how-to-guides/data-quality-observability/profiler/workflow) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
 
 ### Usage and Lineage
 
diff --git a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Presto.md b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Presto.md
index acda2867147..eb30ae28f53 100644
--- a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Presto.md
+++ b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Presto.md
@@ -8,7 +8,7 @@ To extract metadata, the user needs to be able to perform `SHOW CATALOGS`, `SHOW
 
 ### Profiler & Data Quality
 
-Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/connectors/ingestion/workflows/profiler) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
+Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/how-to-guides/data-quality-observability/profiler/workflow) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
 
 You can find further information on the Presto connector in the [docs](https://docs.open-metadata.org/connectors/database/presto).
 
diff --git a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Redshift.md b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Redshift.md
index 657e3e4b3ed..d174104e4bd 100644
--- a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Redshift.md
+++ b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Redshift.md
@@ -16,7 +16,7 @@ GRANT SELECT ON TABLE svv_table_info to test_user;
 
 ### Profiler & Data Quality
 
-Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. The user should also be allowed to view information in `svv_table_info` for all objects in the database. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/connectors/ingestion/workflows/profiler) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
+Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. The user should also be allowed to view information in `svv_table_info` for all objects in the database. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/how-to-guides/data-quality-observability/profiler/workflow) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
 
 ### Usage & Lineage
 
diff --git a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/SapHana.md b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/SapHana.md
index 76856e4c6c8..5900ef8bc58 100644
--- a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/SapHana.md
+++ b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/SapHana.md
@@ -22,7 +22,7 @@ ALTER USER openmetadata DISABLE PASSWORD LIFETIME;
 
 ### Profiler & Data Quality
 
-Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. The user should also be allowed to view information in `tables` for all objects in the database. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/connectors/ingestion/workflows/profiler) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
+Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. The user should also be allowed to view information in `tables` for all objects in the database. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/how-to-guides/data-quality-observability/profiler/workflow) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
 
 You can find further information on the SAP Hana connector in the [docs](https://docs.open-metadata.org/connectors/database/sap-hana).
 
diff --git a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/SingleStore.md b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/SingleStore.md
index 31d78dff32b..444326c8926 100644
--- a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/SingleStore.md
+++ b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/SingleStore.md
@@ -21,7 +21,7 @@ GRANT SELECT ON world.hello TO '<username>';
 ```
 
 ### Profiler & Data Quality
-Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/connectors/ingestion/workflows/profiler) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
+Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/how-to-guides/data-quality-observability/profiler/workflow) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
 
 You can find further information on the SingleStore connector in the [docs](https://docs.open-metadata.org/connectors/database/singlestore).
 
diff --git a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Snowflake.md b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Snowflake.md
index 61d6d58d3b1..86057d9aa30 100644
--- a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Snowflake.md
+++ b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Snowflake.md
@@ -59,7 +59,7 @@ You can find further information on the Snowflake connector in the [docs](https:
 
 
 ### Profiler & Data Quality
-Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. The user should also be allowed to view information in `tables` for all objects in the database. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/connectors/ingestion/workflows/profiler) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
+Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. The user should also be allowed to view information in `tables` for all objects in the database. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/how-to-guides/data-quality-observability/profiler/workflow) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
 
 ## Connection Details
 
diff --git a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Teradata.md b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Teradata.md
index 006d92153db..4f57112e87f 100644
--- a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Teradata.md
+++ b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Teradata.md
@@ -6,7 +6,7 @@ In this section, we provide guides and references to use the Teradata connector.
 
 ### Profiler & Data Quality
 
-Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/connectors/ingestion/workflows/profiler) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
+Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/how-to-guides/data-quality-observability/profiler/workflow) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
 
 You can find further information on the Teradata connector in the [docs](https://docs.open-metadata.org/connectors/database/teradata).
 
diff --git a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Trino.md b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Trino.md
index 4e86cd674d9..2efd7f1abb5 100644
--- a/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Trino.md
+++ b/openmetadata-ui/src/main/resources/ui/public/locales/en-US/Database/Trino.md
@@ -13,7 +13,7 @@ To extract metadata, the user needs to have `SELECT` permission on the following
 Access to resources will be based on the user access permission to access specific data sources. More information regarding access and security can be found in the Trino documentation [here](https://trino.io/docs/current/security.html).
 
 ### Profiler & Data Quality
-Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/connectors/ingestion/workflows/profiler) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
+Executing the profiler Workflow or data quality tests, will require the user to have `SELECT` permission on the tables/schemas where the profiler/tests will be executed. More information on the profiler workflow setup can be found [here](https://docs.open-metadata.org/how-to-guides/data-quality-observability/profiler/workflow) and data quality tests [here](https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality).
 
 You can find further information on the Trino connector in the [docs](https://docs.open-metadata.org/connectors/database/trino).
 
diff --git a/openmetadata-ui/src/main/resources/ui/src/components/Database/Profiler/TableProfiler/NoProfilerBanner/NoProfilerBanner.component.tsx b/openmetadata-ui/src/main/resources/ui/src/components/Database/Profiler/TableProfiler/NoProfilerBanner/NoProfilerBanner.component.tsx
index 063f3d2dbe4..873155d5942 100644
--- a/openmetadata-ui/src/main/resources/ui/src/components/Database/Profiler/TableProfiler/NoProfilerBanner/NoProfilerBanner.component.tsx
+++ b/openmetadata-ui/src/main/resources/ui/src/components/Database/Profiler/TableProfiler/NoProfilerBanner/NoProfilerBanner.component.tsx
@@ -30,7 +30,7 @@ const NoProfilerBanner = () => {
           target="_blank"
           to={{
             pathname:
-              'https://docs.open-metadata.org/connectors/ingestion/workflows/profiler',
+              'https://docs.open-metadata.org/how-to-guides/data-quality-observability/profiler/workflow',
           }}>
           {`${t('label.here-lowercase')}.`}
         </Link>
diff --git a/openmetadata-ui/src/main/resources/ui/src/constants/docs.constants.ts b/openmetadata-ui/src/main/resources/ui/src/constants/docs.constants.ts
index 845db303a0a..f47ae92f3ce 100644
--- a/openmetadata-ui/src/main/resources/ui/src/constants/docs.constants.ts
+++ b/openmetadata-ui/src/main/resources/ui/src/constants/docs.constants.ts
@@ -14,7 +14,7 @@
 export const OMD_REPOSITORY_LINK = 'https://star-us.open-metadata.org/';
 
 export const WORKFLOWS_PROFILER_DOCS =
-  'https://docs.open-metadata.org/connectors/ingestion/workflows/profiler';
+  'https://docs.open-metadata.org/how-to-guides/data-quality-observability/profiler/workflow';
 
 export const DATA_QUALITY_DOCS =
   'https://docs.open-metadata.org/connectors/ingestion/workflows/data-quality';