diff --git a/openmetadata-docs/content/how-to-guides/cli-ingestion-with-basic-auth/index.md b/openmetadata-docs/content/how-to-guides/cli-ingestion-with-basic-auth/index.md
new file mode 100644
index 00000000000..752b45bceb3
--- /dev/null
+++ b/openmetadata-docs/content/how-to-guides/cli-ingestion-with-basic-auth/index.md
@@ -0,0 +1,60 @@
+---
+title: How To Run Ingestion Pipeline Via CLI with Basic Auth
+slug: /how-to-guides/cli-ingestion-with-basic-auth
+---
+
+# How To Run Ingestion Pipeline Via CLI with Basic Auth
+
+Out of the box, OpenMetadata comes with a Username & Password Login Mechanism.
+
+
+
+ Basic Authentication
+
+
+
+
+
+From `0.12.1` OpenMetadata has changed the default `no-auth` to `Basic` auth, So to run any ingestion pipeline from CLI you will have to pass the `jwtToken` and `authProvider` in the `securityConfig`.
+
+
+## How to get the JWT token
+
+1. Go to the `settings` page from the navbar and then scroll down to the `Integrations` Section. Click on the `Bots` and you will see the list of bots, then click on the `ingestion-bot`.
+
+
+
+
+2. You will be redirected to the `ingestion-bot` details page. there you will get the JWT token, click on the copy button and copy the JWT token.
+
+
+
+
+Alright, now you have the JWT token, let see how to add that into the workflow config.
+
+## How to add JWT token into the workflow config
+
+Now Past the copied JWT Token into your pipeline `securityConfig`, So your final workflow config will look like this.
+
+
+> AuthProvider Should be **openmetadata** i.e authProvider: openmetadata
+
+```yaml
+workflowConfig:
+ openMetadataServerConfig:
+ hostPort: http://localhost:8585/api
+ authProvider: openmetadata
+ securityConfig:
+ jwtToken: 'eyJraWQiO...'
+```
+
+Now you can run the pipeline by running.
+
+```commandline
+metadata ingest -c ./pipeline_name.yaml
+```
diff --git a/openmetadata-docs/content/how-to-guides/teams-and-users/how-to-organise-teams-and-users.md b/openmetadata-docs/content/how-to-guides/teams-and-users/how-to-organise-teams-and-users.md
index 16f773edc99..442db463640 100644
--- a/openmetadata-docs/content/how-to-guides/teams-and-users/how-to-organise-teams-and-users.md
+++ b/openmetadata-docs/content/how-to-guides/teams-and-users/how-to-organise-teams-and-users.md
@@ -3,7 +3,9 @@ title: How To Organise Teams And users
slug: /how-to-guides/teams-and-users/how-to-organise-teams-and-users
---
-# Team structure in OpenMetadata
+# How To Organise Teams And users
+
+## Team structure in OpenMetadata
In OpenMetadata we have hierarchal team structure with `teamType` that can be `Organization`, `Business Unit`, `Division`, `Department`, and `Group` (default team type).
diff --git a/openmetadata-docs/content/menu.md b/openmetadata-docs/content/menu.md
index 367d71702e5..f0b1240de09 100644
--- a/openmetadata-docs/content/menu.md
+++ b/openmetadata-docs/content/menu.md
@@ -166,6 +166,8 @@ site_menu:
url: /how-to-guides/teams-and-users
- category: How to guides / Teams and Users / How to Organise Teams and Users
url: /how-to-guides/teams-and-users/how-to-organise-teams-and-users
+ - category: How to guides / CLI Ingestion with basic auth
+ url: /how-to-guides/cli-ingestion-with-basic-auth
- category: OpenMetadata
url: /openmetadata
diff --git a/openmetadata-docs/images/cli-ingestion-with-basic-auth/bot-list.png b/openmetadata-docs/images/cli-ingestion-with-basic-auth/bot-list.png
new file mode 100644
index 00000000000..2e8ca9aff19
Binary files /dev/null and b/openmetadata-docs/images/cli-ingestion-with-basic-auth/bot-list.png differ
diff --git a/openmetadata-docs/images/cli-ingestion-with-basic-auth/bot-token.png b/openmetadata-docs/images/cli-ingestion-with-basic-auth/bot-token.png
new file mode 100644
index 00000000000..dd2515444b3
Binary files /dev/null and b/openmetadata-docs/images/cli-ingestion-with-basic-auth/bot-token.png differ