[reorg fix] Update RUM ownership of views page with rules

hugo/content/en/real_user_monitoring/ownership_of_views.md

@@ -12,21 +12,35 @@
 
 ## Overview
 
-Ownership of views lets you see only the RUM metrics and events for the parts of your application that your team is responsible for. After you've set up ownership of views, every RUM event and metric attached to those views is **tagged** with your team's name. You can turn this filter on or off using the {{< ui >}}My Teams{{< /ui >}} toggle on the {{< ui >}}Summary{{< /ui >}}, {{< ui >}}Optimization{{< /ui >}}, and {{< ui >}}Session Explorer{{< /ui >}} pages.
+Ownership of views lets you see only the RUM metrics and events for the parts of your application that your team owns. After you've set up ownership of views, every RUM event and metric attached to those views is **tagged** with your team's name. You can turn this filter on or off using the {{< ui >}}My Teams{{< /ui >}} toggle on the {{< ui >}}Summary{{< /ui >}}, {{< ui >}}Optimization{{< /ui >}}, and {{< ui >}}Session Explorer{{< /ui >}} pages.
 
 {{< img src="/real_user_monitoring/ownership_of_views/ownership-sessions-explorer-1.png" alt="View of Sessions Explorer, where you can filter user sessions based on the teams assigned in Team Ownership, making it easy to find replays relevant to your team." >}}
 
-By default, the toggle is enabled, which filters metrics and event data to show only the one coming from views your team owns. If you belong to multiple teams, you can enable or disable specific team filters. The teams that own a view are also listed in the top-right corner of all event side panels.
+By default, the toggle is enabled, which filters metrics and event data to show only data from views your team owns. If you belong to multiple teams, you can enable or disable specific team filters. The teams that own a view are also listed in the top-right corner of all event side panels.
+
+## Ownership rules
+
+There are two types of rules to configure ownership of views:
+
+1. **Exact rules**, which map one-to-one with a view name 
+2. **Prefix rules**, which capture all views that contain the prefix in their name
+
+{{< img src="/real_user_monitoring/ownership_of_views/ownership-rule-type.png" alt="Side panel displaying the two different types of rules to define ownership of views." >}}
+
+Every rule must have at least one **team** and one **scope** defined. Two scope types are supported:
+- For the **current RUM application** across all services
+- For a **specific service** across all applications
 
 ## Setup
 
-<div class="alert alert-info">To use this feature, your organization must have teams enabled and configured. </div>
+<div class="alert alert-info">To use this feature, your organization must have teams enabled and configured.</div>
 
 To configure team ownership for your application's views:
 
 1. In Datadog, navigate to the [{{< ui >}}Digital Experience{{< /ui >}} > {{< ui >}}Manage Applications{{< /ui >}}][1] page and select your application.
-2. In the left navigation menu, select {{< ui >}}Team Ownership{{< /ui >}}.
-3. For each selected view, click {{< ui >}}Edit Teams{{< /ui >}} and select one or more teams. This attributes each view in your application to those teams.
+2. In the left navigation menu, select {{< ui >}}Ownership{{< /ui >}}.
+3. For each view, click {{< ui >}}Missing Ownership{{< /ui >}} and create a rule for the view.
+4. Click on the {{< ui >}}All Rules{{< /ui >}} tab to review all created rules and their associated views.
 
 After you associate a view with a team, Datadog automatically attributes new event data to that team.