remove audit mentions (#44309)

docs/configuring-metabase/email.md

@@ -128,4 +128,4 @@ People who are sandboxed won't see suggestions.
 - [Dashboard subscriptions](../dashboards/subscriptions.md)
 - [Notification permissions](../permissions/notifications.md)
 - [Setting up Slack](./slack.md)
-- [Auditing Metabase](../usage-and-performance-tools/audit.md)
+- [Usage Analytics](../usage-and-performance-tools/usage-analytics.md)

docs/configuring-metabase/slack.md

@@ -91,4 +91,4 @@ Once your Metabase app is added to the private channel, you'll need to type out
 - [Dashboard subscriptions](../dashboards/subscriptions.md)
 - [Notification permissions](../permissions/notifications.md)
 - [Setting up email](./email.md)
-- [Auditing Metabase](../usage-and-performance-tools/audit.md)
+- [Usage analytics](../usage-and-performance-tools/usage-analytics.md)

docs/dashboards/subscriptions.md

@@ -106,9 +106,9 @@ To remove a subscription from a dashboard, select the subscription you'd like to
 
 ## Viewing existing dashboard subscriptions
 
-{% include plans-blockquote.html feature="Audit logs" %}
+{% include plans-blockquote.html feature="Usage analytics" %}
 
-To view a list of all alerts and dashboard subscriptions that people have set up in your Metabase, click on the **gear** icon in the upper right and select **Admin settings** > **Audit** > **Subscriptions & Alerts**. See [Audit logs](../usage-and-performance-tools/audit.md).
+You can view a list of all alerts and dashboard subscriptions that people have set up in your Metabase in **Metabase analytics** collection. See [Usage analytics](../usage-and-performance-tools/usage-analytics.md).
 
 ## Customize filter values for each dashboard subscription
 
@@ -135,4 +135,4 @@ See [Notification permissions](../permissions/notifications.md).
 - [Alerts](../questions/sharing/alerts.md)
 - [Setting up email](../configuring-metabase/email.md)
 - [Setting up Slack](../configuring-metabase/slack.md)
-- [Auditing Metabase](../usage-and-performance-tools/audit.md)
+- [Usage analytics](../usage-and-performance-tools/usage-analytics.md)

docs/databases/connections/bigquery.md

@@ -73,7 +73,7 @@ foo,bar,baz
 To sync datasets based on a string match, use the `*` wildcard:
 
 - To sync bar and baz, select **Only these...** and enter the string `b*`.
-- To sync foo only, select **All except...**  and enter the string `b*`.
+- To sync foo only, select **All except...** and enter the string `b*`.
 
 Note that only the `*` wildcard is supported; you can't use other special characters or regexes.
 
@@ -83,7 +83,7 @@ We suggest you leave this off unless you're doing manual [timezone](../../config
 
 ### Include User ID and query hash in queries
 
-This can be useful for [auditing](../../usage-and-performance-tools/audit.md) and debugging, but prevents BigQuery from caching results and may increase your costs.
+This can be useful for [auditing](../../usage-and-performance-tools/usage-analytics.md) and debugging, but prevents BigQuery from caching results and may increase your costs.
 
 ### Re-run queries for simple explorations
 

docs/embedding/introduction.md

@@ -37,14 +37,14 @@ If you'd like to share your data with the good people of the internet, you can c
 ## Comparison of embedding types
 
 | Action                                                                                                   | [Interactive](./interactive-embedding.md) | [Static](./static-embedding.md) | [Public](../questions/sharing/public-links.md) |
-|----------------------------------------------------------------------------------------------------------|-------------------------------------|---------------------------------|------------------------------------------------|
-| Display charts and dashboards                                                                            | ✅                                  | ✅                              | ✅                                             |
-| Display interactive [filter widgets](https://www.metabase.com/glossary/filter_widget)                    | ✅                                  | ✅                              | ✅                                             |
-| Restrict data with [locked filters](./static-embedding-parameters.md#restricting-data-in-a-static-embed) | ❌                                  | ✅                              | ❌                                             |
-| Restrict data with [sandboxes](../permissions/data-sandboxes.md)                                         | ✅                                  | ❌                              | ❌                                             |
-| Use the [drill-through menu](https://www.metabase.com/learn/questions/drill-through)               | ✅                                  | ❌                              | ❌                                             |
-| Self-serve via [query builder](https://www.metabase.com/glossary/query_builder)                          | ✅                                  | ❌                              | ❌                                             |
-| View usage of embeds with [auditing tools](../usage-and-performance-tools/audit.md)                      | ✅                                  | ❌                              | ❌                                             |
+| -------------------------------------------------------------------------------------------------------- | ----------------------------------------- | ------------------------------- | ---------------------------------------------- |
+| Display charts and dashboards                                                                            | ✅                                        | ✅                              | ✅                                             |
+| Display interactive [filter widgets](https://www.metabase.com/glossary/filter_widget)                    | ✅                                        | ✅                              | ✅                                             |
+| Restrict data with [locked filters](./static-embedding-parameters.md#restricting-data-in-a-static-embed) | ❌                                        | ✅                              | ❌                                             |
+| Restrict data with [sandboxes](../permissions/data-sandboxes.md)                                         | ✅                                        | ❌                              | ❌                                             |
+| Use the [drill-through menu](https://www.metabase.com/learn/questions/drill-through)                     | ✅                                        | ❌                              | ❌                                             |
+| Self-serve via [query builder](https://www.metabase.com/glossary/query_builder)                          | ✅                                        | ❌                              | ❌                                             |
+| View usage of embeds with [usage analytics](../usage-and-performance-tools/usage-analytics.md)           | ✅                                        | ❌                              | ❌                                             |
 
 ## Switching from static to interactive embedding
 

docs/permissions/application.md

@@ -33,7 +33,6 @@ Monitoring access sets permissions for the following:
 
 - [Tools](../usage-and-performance-tools/tools.md)
 - [Troubleshooting](../troubleshooting-guide/index.md)
-- [Auditing](../usage-and-performance-tools/audit.md)
 
 ## Subscriptions and alerts
 

docs/permissions/introduction.md

@@ -47,7 +47,7 @@ If instead you're wondering about what data Metabase the company can see, check
 [Application permissions](application.md) (available on paid plans) dictate access to Metabase application-level features, including:
 
 - **Settings**: The Settings tab in the Admin panel.
-- **Monitoring access**: The Tools, Audit, and Troubleshooting tabs in the Admin panel.
+- **Monitoring access**: The Tools and Troubleshooting tabs in the Admin panel.
 - **Subscriptions and Alerts**. Which groups can create/edit dashboard subscriptions and alerts.
 
 ### SQL snippet folder permissions

docs/permissions/notifications.md

@@ -36,8 +36,6 @@ People in the admin group can:
 - Add or remove recipients from an existing subscription or alert. Admins can safely add and remove recipients without changing the permissions of the alert or subscription. For example, if an admin adds Anya to a subscription created by Beau, Anya will receive emails with the same data that Beau can see (not what the admin can see).
 - Delete subscriptions or alerts.
 
-Admins can also use Metabase's [auditing tools](../usage-and-performance-tools/audit.md#subscriptions-and-alerts) to manage notifications.
-
 ## What notification recipients can see
 
 Notification **recipients** can see whatever the notification **creator** can see. For example, if:
@@ -57,4 +55,3 @@ On [Enterprise](https://www.metabase.com/product/enterprise) and [Pro](https://w
 
 - [Dashboard subscriptions](../dashboards/subscriptions.md)
 - [Alerts](../questions/sharing/alerts.md)
-- [Auditing](../usage-and-performance-tools/audit.md)

docs/questions/sharing/alerts.md

@@ -70,7 +70,6 @@ Admins get special privileges with alerts.
 
 - Admins can edit and delete any alert. This can't be undone, so be careful!
 - Admins can add or remove recipients on any alert, even ones that they did not create themselves.
-- Admins on some [paid plans](https://www.metabase.com/pricing) can view, edit, and delete all dashboard subscriptions and alerts in the [Audit tab](../../usage-and-performance-tools/audit.md#subscriptions-and-alerts).
 
 ### Everyone
 
@@ -79,7 +78,7 @@ Admins get special privileges with alerts.
 
 ## Avoid changing the name of the alerted channel in Slack
 
-Once you set up an alert to a Slack channel, avoid changing the name of that channel in Slack. If you rename the channel in Slack, but you want Metabase to continue to send alerts to that renamed channel, you'll need to update the alert in Metabase to point to the new channel name. 
+Once you set up an alert to a Slack channel, avoid changing the name of that channel in Slack. If you rename the channel in Slack, but you want Metabase to continue to send alerts to that renamed channel, you'll need to update the alert in Metabase to point to the new channel name.
 
 ## Alert expiration
 
@@ -91,11 +90,11 @@ Some circumstances will automatically delete alerts:
 
 Alerts will continue to work even if the person who set up the alert no longer has an active account. For example, if an alert with multiple recipients (or to a Slack channel) was set up by someone whose account has since been deactivated, that alert will continue to work (though Metabase will stop sending the alerts to the deactivated account).
 
-## Admins can audit alerts
+## Admins can see all alerts
 
-{% include plans-blockquote.html feature="Audit logs" %}
+{% include plans-blockquote.html feature="Usage analytics" %}
 
-Admins can view a list of all alerts and dashboard subscriptions that people have set up in your Metabase. Click on the **gear** icon in the upper right and select **Admin settings** > **Audit** > **Subscriptions & Alerts**. See [Audit](../../usage-and-performance-tools/audit.md#subscriptions-and-alerts).
+Admins can view a list of all alerts and dashboard subscriptions that people have set up in your Metabase in the **Metabase analytics** collection. See [Usage analytics](../../usage-and-performance-tools/usage-analytics.md#alerts-model).
 
 ## How permissions work with alerts
 
@@ -110,4 +109,4 @@ See [Sending alerts and subscriptions to private Slack channels](../../configuri
 - [Dashboard subscriptions](../../dashboards/subscriptions.md)
 - [Setting up email](../../configuring-metabase/email.md)
 - [Setting up Slack](../../configuring-metabase/slack.md)
-- [Auditing Metabase](../../usage-and-performance-tools/audit.md)
+- [Usage analytics](../../usage-and-performance-tools/usage-analytics.md)

docs/troubleshooting-guide/db-performance.md

@@ -14,7 +14,7 @@ To fix problems with your Metabase [application database](../installation-and-op
 
 ## Identifying bottlenecks
 
-1. Optional: use Metabase's [auditing tools](../usage-and-performance-tools/audit.md) to look at your Metabase usage stats.\*
+1. Optional: use Metabase's [Usage analytics](../usage-and-performance-tools/usage-analytics.md) to look at your Metabase usage stats.\*
 2. Go to your database's server logs and check whether:
    - Your tables are growing in size,
    - More people are using Metabase to access your database,

docs/troubleshooting-guide/my-dashboard-is-slow.md

@@ -14,7 +14,7 @@ First, you'll want to make sure your browser is on friendly terms with Metabase:
 1. Create a new dashboard for each group of cards that are related to the same time period or segment.
    - For example, create new dashboards for weekly vs. monthly metrics, or new vs. returning customers.
 2. Move your cards to the new dashboard(s) until each dashboard has 10 or fewer cards.
-2. Use [custom destinations](https://www.metabase.com/learn/dashboards/custom-destinations) to link related cards on different dashboards.
+3. Use [custom destinations](https://www.metabase.com/learn/dashboards/custom-destinations) to link related cards on different dashboards.
 
 **Explanation**
 
@@ -24,7 +24,7 @@ Aside from running faster, a small and focused dashboard is also easier for peop
 
 ## Dashboard used by many people at the same time
 
-1. Optional: use Metabase's [auditing tools](../usage-and-performance-tools/audit.md) to look at your Metabase usage stats\*.
+1. Optional: use Metabase's [Usage analytics](../usage-and-performance-tools/usage-analytics.md) to look at your Metabase usage stats\*.
 2. Set up [caching](../configuring-metabase/caching.md) for the questions on your popular dashboard.
 3. Run the dashboard during off-hours so that people can load the cached results in seconds instead of executing a fresh query to your database.