docs: 7.2 updates (#10611)

website/docs/reference/change-requests.mdx

@@ -21,7 +21,7 @@ Change requests also allow you to group changes and [apply them at a specific po
 
 Change requests can be enabled for a specific environment within a project, or configured globally for an environment across all projects. This allows you to differentiate your configurations across different environments, such as production and development.
 
-You can require up to 10 approvals for a change request.
+You can require up to 10 approvals for a change request. When you add an approver to a change request, they are notified by email.
 
 <VideoContent videoUrls={["https://www.youtube.com/embed/ENUqFVcdr-w"]}/>
 

website/docs/reference/feature-toggles.mdx

@@ -183,12 +183,15 @@ For example, you could set a pattern like `^(red|blue|green)\.[a-z-]+\.[0-9]+$`.
 
 ## Archive a feature flag
 
-You can archive a feature flag once you no longer need it. To do so, go to the feature flag's page and click **Archive feature flag**.
+Archiving feature flags that you no longer need is an important part of keeping your instance healthy and technical debt low. To archive a flag, go to the feature flag's page and click **Archive feature flag**.
 
 Once archived, the flag is no longer available to client SDKs.
 
 ![Archive a feature flag](/img/archive-feature-flag.png)
 
+Unleash also helps you identify flags that are safe to archive. Flags in the cleanup stage that haven't been used for seven days automatically appear with an archive suggestion.
+You can review the list and archive flags in bulk with confidence, keeping your setup clean and manageable.
+
 ### View archived flags
 
 To view archived feature flags in a project, use the **Show only archived** filter in the **Feature flags** list.
@@ -237,3 +240,15 @@ You can add external links to your feature flags, allowing you to connect them t
 In addition, you can define link templates at the project level in **Settings > Project settings > Enterprise settings > Project link templates**. These templates automatically populate links for all new feature flags within that project. For example, you can create templates to find all usages of 
 a feature flag in your repository or automatically link to a Jira issue when a flag is created from Jira.
 
+## Unknown flag checker
+
+:::note Availability
+
+**Version**: `7.2+`
+
+:::
+
+Unleash automatically checks for feature flags that your SDKs try to evaluate but that don't exist in your instance. You can view these under **Unknown flags** in **Flags overview**.
+This list helps you quickly spot typos, misconfigurations, or stale references in your code. 
+
+Reviewing unknown flags regularly keeps your configuration in sync with your applications and helps prevent errors caused by missing or misnamed flags.

website/docs/reference/insights.mdx

@@ -13,17 +13,29 @@ import SearchPriority from '@site/src/components/SearchPriority';
 :::
 
 
-Analytics is a feature designed to help you better understand and gain insights into what is happening in your Unleash instance. You can view analytics across all projects or by selecting single or multiple projects using the filter.
+Analytics gives you visibility into how flags are created, used, and cleaned up in your Unleash instance. These dashboards connect engineering activity to business outcomes by showing how quickly features move to production, how well teams manage technical debt, and how your user base evolves over time.
+You can view analytics across all projects or by selecting single or multiple projects using the filter.
 
-In total, there are 6 different charts available that show information over time:
-
-- Total users
-- Flags
+The dashboard shows:
+- Feature flag lifecycle data
+- Total users and flags
 - Technical debt
 - Median time to production
 - Flag evaluation metrics
 - Updates per environment type
 
+### Flags lifecycle
+
+
+:::note Availability
+
+**Plan**: [Pro](/availability#plans) and [Enterprise](https://www.getunleash.io/pricing) | **Version**: `7.2+`
+
+:::
+
+Shows how many flags are currently in each major lifecycle stage: Develop, Production, and Cleanup. Each stage shows how many flags are new this week, how many have been there for more than a week, and the median time flags spend in that stage. You can also compare this to the historical median to spot outliers.
+
+![Total users chart](/img/flag-lifecycle-analytics.png)
 
 ### Total users
 

website/docs/reference/release-templates.mdx

@@ -8,22 +8,10 @@ import SearchPriority from '@site/src/components/SearchPriority';
 
 :::note Availability
 
-**Plan**: [Enterprise](https://www.getunleash.io/pricing) cloud-hosted | **Version**: `6.8+` in [BETA](/availability#beta-features).
+**Plan**: [Enterprise](https://www.getunleash.io/pricing) | **Version**: `7.2+`
 
 :::
 
-<details>
-  <summary>Participate in the beta program</summary>
-
-  Release templates are currently in beta. If you're interesting in trying the feature out, please contact us at beta@getunleash.io.
-
-  Future iterations of the feature may include:
-    - An overview of ongoing releases and currently running milestones across all projects
-    - Automated transitions between different milestones
-    - Reporting on release templates
-</details>
-
-
 ## Overview
 
 [Release templates](#release-template) help you standardize your approach to rolling out new features. By predefining a set of release milestones, you can ensure consistency across all your feature rollouts.

website/docs/reference/resource-limits.mdx

@@ -36,15 +36,12 @@ The resources and their respective limits and environment variables are:
 | [Action](./actions) sets per project                                                 | N/A                                                    | N/A                              | 5                                                     | `UNLEASH_ACTION_SETS_PER_PROJECT_LIMIT`        |
 | [Action](./actions) set filters                                                      | N/A                                                    | N/A                              | 5                                                     | `UNLEASH_ACTION_SET_FILTERS_LIMIT`             |
 | [Action](./actions) set filter values                                                | N/A                                                    | N/A                              | 25                                                    | `UNLEASH_ACTION_SET_FILTER_VALUES_LIMIT`       |
+| [Release templates](./release-templates)                                             | N/A                                                    | N/A                              | 5                                                     | `UNLEASH_RELEASE_TEMPLATES_LIMIT`       |
 
 
 
 ## Overriding the limits
 
-:::info Existing customers above the limits
-Existing hosted customers who are already above the limits will have their limits adjusted to 110% of their maximum values when the limits were introduced.
-:::
-
 With a few exceptions, all the limits can be overridden through the use of their respective environment variables. However, while it is possible to override these limits, we advise against it in most cases. If you feel that you're unable to do what you need to do because of the limits, we'd love to hear from you.
 
 The following resources have a lower limit of 1: