@@ -384,7 +384,7 @@ SentryAndroid.init(this) { options ->
 
 Navigation 3 support is available in `sentry-android-navigation3` `8.60.0` and later.
 
-See the [Limitations](#limitations) section below for additional restrictions.
+See [Supported Setups](#supported-setups) and [Limitations](#limitations) for setup restrictions.
 
 </Alert>
 
@@ -406,6 +406,8 @@ See [Customize Nav3 Options](#customize-nav3-options) to learn how to modify tho
 
 Install the Android SDK and add the `sentry-android-navigation3` library:
 
+At runtime, this integration requires Compose UI 1.7 or later, or `lifecycle-runtime-compose` 2.8.3 or later.
+
 ```groovy {filename:build.gradle}
 dependencies {
   implementation 'io.sentry:sentry-android:{{@inject packages.version('sentry.java.android', '8.60.0') }}'
@@ -469,12 +471,6 @@ Values returned from `BackStackEntryMapper` are **not** scrubbed by the Sentry S
 
 </Alert>
 
-<Alert>
-
-Multiple, simultaneously active `SentryNavEffect` instances writing to the same [Sentry scope](https://docs.sentry.io/platforms/android/enriching-events/scopes/) are **_not_** supported. Violating this restriction can result in duplicated or interleaved data and undefined transaction behavior.
-
-</Alert>
-
 ### Customize Nav3 Options
 
 Use `SentryNavOptions` to disable breadcrumbs or transactions, or to limit how much of the back stack Sentry stores with captured events.
@@ -634,13 +630,41 @@ val backStackItemMapper = BackStackEntryMapper<NavKey> { entry ->
 }
 ```
 
+### Supported Setups
+
+The setups below require `sentry-android-navigation3` 8.63.0 or later. Earlier versions support only one active `SentryNavEffect` per Sentry scope.
+
+`SentryNavEffect` is compatible with most, but not all, Nav3 setups. Each effect uses the lifecycle of its nearest `LocalLifecycleOwner` to decide when it can write to Sentry's [shared scope](/platforms/android/enriching-events/scopes/), and compatibility between effects depends on how those lifecycle owners interact. Incompatible effects won't crash, but they can generate stale navigation data, produce interleaved breadcrumbs, or interfere with each other's transactions.
+
+<Alert>
+
+All supported setups below assume that each `SentryNavEffect` is called in the same composable as the `NavDisplay` it observes, and that the effect is called before it.
+
+They also assume that `SentryNavEffect` is **_not_** called from content rendered by `NavDisplay`, such as a `NavEntry`, `NavEntryDecorator`, or `Scene`. `SentryNavEffect` needs the lifecycle of the Activity or Fragment hosting your `NavDisplay`, rather than the navigation-scoped lifecycle `NavDisplay` provides to its content.
+
+</Alert>
+
+**Supported:**
+
+- A single-Activity app with one `NavDisplay` and `SentryNavEffect` pair.
+- A multi-Activity app where each Activity has its own `NavDisplay` and `SentryNavEffect` pair.
+- A multi-Fragment app where each Fragment has its own `NavDisplay` and `SentryNavEffect` pair, and the host Activity or Activities have none of their own.
+- A `ViewPager2` whose pages are Fragments, each with its own `NavDisplay` and `SentryNavEffect` pair.
+- An Activity or Fragment with its own `NavDisplay` and `SentryNavEffect` pair that stays visible beneath a `DialogFragment` or translucent Activity with its own pair.
+
+**Not supported:**
+
+- Side-by-side `NavDisplay` and `SentryNavEffect` pairs in the same Activity or Fragment.
+- Nested `NavDisplay` and `SentryNavEffect` pairs in the same Activity or Fragment. If you nest `NavDisplay` instances, call `SentryNavEffect` only for the outermost one.
+- `SentryNavEffect` instances in multiple Activities or Fragments that users can interact with at the same time, such as an Activity and hosted Fragments where the Activity and Fragments each have their own `NavDisplay` and `SentryNavEffect` pairs, or two Activities from the same app in [multi-resume mode](https://developer.android.com/develop/ui/views/layout/support-multi-window-mode).
+- `SentryNavEffect` instances in pages or tabs that share their host's lifecycle, such as Compose `HorizontalPager` pages, `ViewPager2` pages that aren't Fragments, or tabs that are all kept in the composition. Those pages or tabs share one `LifecycleOwner`, so at most one can call `SentryNavEffect`.
+
 ### Limitations
 
 `SentryNavEffect` treats the top entry in your back stack as the current screen. That works well for most Nav3 setups, but it means that `SentryNavEffect` does **_not_**:
 
 - understand the concept of Nav3 [Scenes](https://developer.android.com/guide/navigation/navigation-3/scenes) or multi-pane layouts
-- track multiple back stacks
-- permit multiple, simultaneously active `SentryNavEffect` instances
+- track multiple back stacks with one `SentryNavEffect` instance
 - make special accommodations for [predictive back](https://developer.android.com/guide/navigation/custom-back/predictive-back-gesture) gestures (e.g., spans produced by predictively rendered composables may appear under the current destination's transaction)
 
 ## Navigation 2 and Navigation 3 Interoperability