docs:Bulk configuration section added in Ingestion Properties (#407)

* docs:Bulk configuration section added in Ingestion Properties

* modified the edge case for data filter and cursor field

* corrected the bulk config definition and refurbished the edge cases

Author: nayanj98

docs/understanding/terminologies/olake.mdx

@@ -364,6 +364,50 @@ These modes control how records are written to the destination for CDC and Incre
 
 ---
 
+### 9. Bulk Configure
+
+Bulk Configure lets users apply the same configuration to multiple selected streams at once. When working with sources containing multiple streams, users often need to apply the same configuration across several streams. Bulk Configuration significantly reduces setup time and improves usability.
+
+#### Supported Bulk Configurations
+
+When multiple streams are selected using checkboxes, users can trigger a bulk configuration action to apply the following properties for all selected streams at once:
+
+- **Sync Mode**
+- **Cursor Fields:** Shown only if Sync mode is *Full Refresh + Incremental*. Only columns that are common across all selected streams are available for cursor field selection.
+- **Data Filter (Column and Values):** Only columns that are common across all selected streams and have similar data types are available for data filter configuration.
+- **Partition Regex Value**
+
+::::info Important Considerations
+- **Overwriting Existing Configurations:** Existing configurations are overwritten only for the modified properties. If a user uses the bulk configure option to change only a few properties of a previously configured stream, properties configured outside the bulk configure feature remain unchanged.
+- **Warning on Reconfiguration:** If a few streams are already configured and the user configures them again via Bulk Configuration, a warning modal will appear to confirm the action. Changing an already configured stream property will trigger a clear destination run.
+::::
+
+#### Step 1: Initiate Bulk Configuration
+
+From the Streams page, the **Bulk Configure** button can be used to apply the same configuration across multiple streams at once.
+
+![Bulk Configuration Button](/img/docs/terminologies/bulk-configure-button.webp)
+
+#### Step 2: Select Streams
+
+After clicking **Bulk Configure**, a modal opens where the target streams can be selected for bulk configuration. Once stream selection is complete, click **Configure Streams** to continue.
+
+![Bulk Configuration Streams Selection](/img/docs/terminologies/bulk-configure-select-streams.webp)
+
+#### Step 3: Select Configuration
+
+The next window displays the selected streams for bulk configuration. Configure the properties to be applied across those streams. The properties that are configured are marked with a warning sign, and only those marked properties are applied.
+
+![Bulk Configuration on the streams](/img/docs/terminologies/configure-bulk-streams.webp)
+
+#### Step 4: Review and Apply Configuration
+
+In the final window, the selected configuration can be reviewed before submission. After confirmation, clicking **Apply Changes** applies the configuration to the selected streams.
+
+![Review and Apply Bulk Configuration](/img/docs/terminologies/review-bulk-config.webp)
+
+---
+
 ## OLake-Generated Columns
 
 When OLake replicates data from source (like PostgreSQL, MySQL, Oracle or MongoDB) to destination formats (Apache Iceberg, Parquet), it automatically adds several metadata columns to track the lifecycle and processing history of each record. These columns help users understand how and when each row was captured and written to the destination.
@@ -540,3 +584,4 @@ When a job is inactive, certain job-level features are unavailable:
 
 To use these features, resume the job to move it back to active status.
 :::
+