Merge pull request #8149 from newrelic/Log-capabilities-improve

fix(user type): add logs detail

src/content/docs/accounts/accounts-billing/new-relic-one-user-management/user-type.mdx

@@ -195,11 +195,11 @@ Here's a detailed comparison of capabilities by user type. For tips on why you'd
 
     <tr>
       <td>
-        [Log management](/docs/logs/get-started/get-started-log-management)<sup>1</sup>
+        [Log management](/docs/logs/get-started/get-started-log-management)
       </td>
 
       <td style="text-align:center">
-        Search/view only
+        Search/view only[<sup>1</sup>](#logs-capabilities)
       </td>
 
       <td style="text-align:center">
@@ -603,14 +603,46 @@ Here's a detailed comparison of capabilities by user type. For tips on why you'd
     id="logs-capabilities"
     title="Log management capabilities"
   >
-    <Callout variant="important">
-      On January 12, 2022, basic users had some log management capabilities removed. Their current capabilities are described below.
-    </Callout>
+Details on log management capabilities by user type:
+
+<table>
+  <thead>
+    <tr style="width:170px">
+      <th>
+        Basic users
+      </th>
+
+      <th>
+        Core users and full platform users
+      </th>
+    </tr>
+  </thead>
+<tbody>
+    <tr>
+      <td>
+* Search, view, and query log data
+* Saved views
+* Attributes
+      </td>
+<td>
+
+All features, including those in **Basic user** column and: 
+
+* Patterns
+* Drop filters
+* Parsing
+* Data partitions
+* Define custom rules and logic
+* Log obfuscation (available with [Data Plus](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing#data-prices))
+* [Livetail](/docs/logs/troubleshooting/view-log-messages-real-time-live-tail)
+
+These users can also see [logs in context](/docs/logs/logs-context/configure-logs-context-apm-agents) for the UI experiences they have access to (for example, core users can see log data in the errors inbox UI).
+      </td>
+    </tr>
+  </tbody>
+</table>
 
-    Log-related capabilities:
 
-    * **Basic users** can view and search the [Logs UI](/docs/logs/get-started/get-started-log-management).
-    * **Core users** and **full platform users** have access to all [Logs UI features](/docs/logs/ui-data/use-logs-ui) and configuration capabilities, and can see [logs in context](/docs/logs/logs-context/configure-logs-context-apm-agents) for the UI experiences they have access to (for example, core users can see applicable log data in the errors inbox UI).
   </Collapser>
 
   <Collapser
@@ -772,15 +804,6 @@ For rules around billing and downgrading users, see [Billing and downgrade rules
 
 For an explanation of how the concept of user type relates to our roles, see [User management concepts](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/#standard-roles).
 
-## Change to "full user" language [#full-user-language]
-
-In November of 2021, in the product and public docs, the "full user" user type name was changed to "full platform user."
-
-For organizations that have the [pricing version without core users](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/user-count-billing#pricing-versions):
-
-* "Full platform users" are equivalent to what are referred to as "full users" and "monthly provisioned users" in your New Relic agreement. For more about agreement-level language, see [Billable user agreement terminology](/docs/licenses/license-information/usage-plans/new-relic-one-usage-plan-descriptions#billable-user-terms).
-* When [querying your full platform user counts](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts), you use `FullUsersBillable` and not `FullPlatformUsersBillable`.
-
 ## Lacking access to something? [#access]
 
 For questions related to lack of access to New Relic accounts or features, see [Factors affecting access](/docs/accounts/accounts-billing/general-account-settings/factors-affecting-access-features-data/#account-access).