diff --git a/openmetadata-docs/content/v1.7.x/connectors/ingestion/workflows/dbt/ingest-dbt-owner.md b/openmetadata-docs/content/v1.7.x/connectors/ingestion/workflows/dbt/ingest-dbt-owner.md
index 22fbef5d3c2..1b07d2c25ba 100644
--- a/openmetadata-docs/content/v1.7.x/connectors/ingestion/workflows/dbt/ingest-dbt-owner.md
+++ b/openmetadata-docs/content/v1.7.x/connectors/ingestion/workflows/dbt/ingest-dbt-owner.md
@@ -48,7 +48,34 @@ Openmetadata fetches the owner information from the `catalog.json` file. Below i
 ### 3. Adding the User or Team to OpenMetadata
 The user or team which will be set as the entity owner should be first created in OpenMetadata.
 
-While linking the owner from `manifest.json` or `catalog.json` files to the entity, OpenMetadata first searches for the user if it is present. If the user is not present it searches for the team 
+While linking the owner from `manifest.json` or `catalog.json` files to the entity, OpenMetadata first searches for the user if it is present. If the user is not present it searches for the team.
+
+### 4. Adding Multiple Owners to dbt Models
+
+OpenMetadata allows you to define multiple owners (users or teams) for dbt models through the `owner` field under `meta.openmetadata` in your `schema.yml` configuration. This helps reflect shared ownership and collaborative accountability on data assets.
+
+#### Example Configuration
+
+```yaml
+models:
+  - name: customers
+    meta:
+      openmetadata:
+        glossary: [
+          'Test_Glossary.term_one',
+          'Test_Glossary.term_two.nested_term.more_nested_term',
+        ]
+        tier: 'Tier.Tier2'
+        owner: ['John Doe', 'jane@gmail.com']
+    config:
+      tags: ["model_tag_one", "model_tag_two"]
+```
+
+#### Guidelines
+
+- **Owner Field**: Provide a list of users or team identifiers under owner.
+- **User Validation**: Ensure the specified owners (e.g., John Doe, jane@gmail.com) exist in OpenMetadata as valid user or team entities.
+- **Overwrite Behavior**: Use the dbtUpdateOwners parameter in your ingestion configuration to control whether this list overwrites existing owners or only applies to unowned assets.
 
 #### Following steps shows adding a User to OpenMetadata:
 **1.** Click on the `Users` section from homepage
diff --git a/openmetadata-docs/content/v1.8.x-SNAPSHOT/connectors/ingestion/workflows/dbt/ingest-dbt-owner.md b/openmetadata-docs/content/v1.8.x-SNAPSHOT/connectors/ingestion/workflows/dbt/ingest-dbt-owner.md
index 8cb4cc60f56..f6e460b00da 100644
--- a/openmetadata-docs/content/v1.8.x-SNAPSHOT/connectors/ingestion/workflows/dbt/ingest-dbt-owner.md
+++ b/openmetadata-docs/content/v1.8.x-SNAPSHOT/connectors/ingestion/workflows/dbt/ingest-dbt-owner.md
@@ -48,7 +48,34 @@ Openmetadata fetches the owner information from the `catalog.json` file. Below i
 ### 3. Adding the User or Team to OpenMetadata
 The user or team which will be set as the entity owner should be first created in OpenMetadata.
 
-While linking the owner from `manifest.json` or `catalog.json` files to the entity, OpenMetadata first searches for the user if it is present. If the user is not present it searches for the team 
+While linking the owner from `manifest.json` or `catalog.json` files to the entity, OpenMetadata first searches for the user if it is present. If the user is not present it searches for the team.
+
+### 4. Adding Multiple Owners to dbt Models
+
+OpenMetadata allows you to define multiple owners (users or teams) for dbt models through the `owner` field under `meta.openmetadata` in your `schema.yml` configuration. This helps reflect shared ownership and collaborative accountability on data assets.
+
+#### Example Configuration
+
+```yaml
+models:
+  - name: customers
+    meta:
+      openmetadata:
+        glossary: [
+          'Test_Glossary.term_one',
+          'Test_Glossary.term_two.nested_term.more_nested_term',
+        ]
+        tier: 'Tier.Tier2'
+        owner: ['John Doe', 'jane@gmail.com']
+    config:
+      tags: ["model_tag_one", "model_tag_two"]
+```
+
+#### Guidelines
+
+- **Owner Field**: Provide a list of users or team identifiers under owner.
+- **User Validation**: Ensure the specified owners (e.g., John Doe, jane@gmail.com) exist in OpenMetadata as valid user or team entities.
+- **Overwrite Behavior**: Use the dbtUpdateOwners parameter in your ingestion configuration to control whether this list overwrites existing owners or only applies to unowned assets.
 
 #### Following steps shows adding a User to OpenMetadata:
 **1.** Click on the `Users` section from homepage