Merge pull request #6842 from segmentio/prigiattiperrut-patch-4

Adding a note about Scope of Transformations

Author: forstisabella

src/protocols/transform/index.md

@@ -27,7 +27,8 @@ Segment's goal is to make Transformations a powerful tool that complements a wel
 - **Source-level transformations are irrevocable:** When applied at the source, a transformation permanently changes the structure of the event. The original events are not easily recoverable or [Replayable](/docs/guides/what-is-replay). Assume that transformed data cannot be recovered.
 - **Device-mode destinations are NOT supported:** Source scoped transformations will **only** apply to cloud-mode destinations, warehouses, and S3 destinations. Destination scoped transformations will **only** apply to cloud-mode destinations.
 - **Transformation order:** Segment processes source-scoped transformations before the events reach destination filters. Segment processes destination-scoped transformations after the events pass through destination filters.
-- **Multiple instances of the same destination:** If multiple instances of a destination are connected to a single source, then the same transformation applies across every instance. 
+- **Multiple instances of the same destination:** If multiple instances of a destination are connected to a single source, then the same transformation applies across every instance.
+- **Transformation scope:** Transformations can be applied to event names, properties, and traits. However, it's important to note that transformations cannot be applied to top-level attributes like userId.
 
 
 ## View all Transformations