Add latest changes from gitlab-org/gitlab@master

3 files changed, 11 insertions, 4 deletions

diff --git a/doc/administration/audit_events.md b/doc/administration/audit_events.md
index 97c1cbc7490..9d51be5ebf4 100644
--- a/doc/administration/audit_events.md
+++ b/doc/administration/audit_events.md
@@ -356,6 +356,7 @@ The following user actions on a GitLab instance generate instance audit events:
   GitLab 15.1.
 - Enabled Admin Mode. [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/362101) in GitLab 15.7.
 - All [group events](#group-events) and [project events](#project-events).
+- User was unblocked using the Admin Area or API. [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/115727) in GitLab 15.11.
 
 Instance events can also be accessed using the [Instance Audit Events API](../api/audit_events.md#instance-audit-events).
 
diff --git a/doc/ci/triggers/index.md b/doc/ci/triggers/index.md
index 393b128c658..b9e5dd87b24 100644
--- a/doc/ci/triggers/index.md
+++ b/doc/ci/triggers/index.md
@@ -187,7 +187,12 @@ In pipelines triggered with a trigger token, jobs are labeled as `triggered` in
 
 ## Troubleshooting
 
-### `404 not found` when triggering a pipeline
+### `403 Forbidden` when you trigger a pipeline with a webhook
+
+When you trigger a pipeline with a webhook, the API might return a `{"message":"403 Forbidden"}` response.
+To avoid trigger loops, do not use [pipeline events](../../user/project/integrations/webhook_events.md#pipeline-events) to trigger pipelines.
+
+### `404 Not Found` when triggering a pipeline
 
 A response of `{"message":"404 Not Found"}` when triggering a pipeline might be caused
 by using a [personal access token](../../user/profile/personal_access_tokens.md)
diff --git a/doc/user/analytics/value_streams_dashboard.md b/doc/user/analytics/value_streams_dashboard.md
index 550b5e2d1df..d6e1a26afab 100644
--- a/doc/user/analytics/value_streams_dashboard.md
+++ b/doc/user/analytics/value_streams_dashboard.md
@@ -6,11 +6,12 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 # Value Streams Dashboard (Beta) **(ULTIMATE)**
 
-> Introduced in GitLab 15.8 as a Closed [Beta](../../policy/alpha-beta-support.md#beta-features) feature [with a flag](../../administration/feature_flags.md) named `group_analytics_dashboards_page`. Disabled by default.
+> - Introduced in GitLab 15.8 as a Closed [Beta](../../policy/alpha-beta-support.md#beta-features) feature [with a flag](../../administration/feature_flags.md) named `group_analytics_dashboards_page`. Disabled by default.
+> - Released in GitLab 15.11 as an Open [Beta](../../policy/alpha-beta-support.md#beta-features) feature [with a flag](../../administration/feature_flags.md) named `group_analytics_dashboards_page`. Enabled by default.
 
 FLAG:
-On self-managed GitLab, by default this feature is not available. To make it available, ask an administrator to [enable the feature flag](../../administration/feature_flags.md) named `group_analytics_dashboards_page`.
-On GitLab.com, this feature is not available. This feature is not ready for production use.
+On self-managed GitLab, this feature is available by default. To disable it, ask an administrator to [disable the feature flag](../../administration/feature_flags.md) named `group_analytics_dashboards_page`.
+On GitLab.com, this feature is available. This feature is not ready for production use.
 
 You can leave feedback on dashboard bugs or functionality in [issue 381787](https://gitlab.com/gitlab-org/gitlab/-/issues/381787).