diff --git a/content/en/docs/refguide/modeling/menus/help-menu/_index.md b/content/en/docs/refguide/modeling/menus/help-menu/_index.md
index 6c505e0dc83..9f96aad74fb 100644
--- a/content/en/docs/refguide/modeling/menus/help-menu/_index.md
+++ b/content/en/docs/refguide/modeling/menus/help-menu/_index.md
@@ -20,7 +20,7 @@ The **Help** menu items are described in the table below:
| **Help Contents** | Opens the home page of the documentation in the default web browser. |
| **Ask a Question** | Opens the Mendix Community in the default web browser. |
| **Submit Feedback...** | Opens the [Help us improve](/refguide/feedback-survey/) dialog to gather input on your experience using Mendix Studio Pro. |
-| **Support Tools** | Provides tools that can be used to share with Mendix Support, especially when you encounter issues with performance or high memory consumption. Support tools include the following:
**Log Level** – allows changing the minimum level (severity) of logging entries that Studio Pro will add to the log file. The following levels are available:
Trace
Debug
Info
Warning
Error
Critical
[Performance Logging](/refguide/performance-logging/) – logs performance measurements to key functionalities (such as opening and closing microflow editors and moving items around in the App Explorer) that can help identify performance degradations.
[Profiling](/refguide/profiling/) – runs a performance profiler session from within Studio Pro without installing the actual profiler on your machine or captures a memory snapshot. For more information, see [Profiling](/refguide/profiling/).
**Tool Windows** > **Background Jobs** – shows a pane containing information about current and previous background tasks.
**Tool Windows** > **Project Context** – shows a pane containing information about part of the background memory of Studio Pro.
**Tool Windows** > **Web Processes** – provides a real-time, read-only view of all web views running in Studio Pro, showing each view's process ID, name, CPU, and memory usage. It helps users identify performance issues and report problematic web views to the Support team. This feature is only available for Windows.
**Enable Responsiveness Monitor** - detects when the application becomes unresponsive and writes diagnostic information to the log file.
**Enable Simple Progress Dialog** – enables the simplified version of the dialog that appears while Studio Pro is executing an operation (for example, saving a document).
**Optimize MPR** – starts an action that will remove allocated memory resources clean from a project file (.mpr) if they are from no longer required.
**Convert to Full Clone** – starts an action that will turn a [partially cloned](/refguide/clone-type/) application into full one.
**Fetch Repository** – starts an action that will fix a corrupted repository. This option is available for a partially-cloned repository only.
**Collect Version Control Data** – helps you to collect basic version control data kept in the logs of Studio Pro.
[Capture Maia Agent Session](/refguide/maia-make/#save-maia-session) – captures a Maia Session to help analyze Maia's responses and behavior for troubleshooting or support purposes.
**Collect Support Information** – helps collect information that assists the Support team in finding the root causes of issues.
**Contact Support** – opens the Mendix Support page to help users report issues.
|
+| **Support Tools** | Provides tools that can be used to share with Mendix Support, especially when you encounter issues with performance or high memory consumption. Support tools include the following:
**Log Level** – allows changing the minimum level (severity) of logging entries that Studio Pro will add to the log file. The following levels are available:
Trace
Debug
Info
Warning
Error
Critical
[Performance Logging](/refguide/performance-logging/) – logs performance measurements to key functionalities (such as opening and closing microflow editors and moving items around in the App Explorer) that can help identify performance degradations.
[Profiling](/refguide/profiling/) – runs a performance profiler session from within Studio Pro without installing the actual profiler on your machine or captures a memory snapshot. For more information, see [Profiling](/refguide/profiling/).
**Tool Windows** > **Background Jobs** – shows a pane containing information about current and previous background tasks.
**Tool Windows** > **Project Context** – shows a pane containing information about part of the background memory of Studio Pro.
**Tool Windows** > **Web Processes** – provides a real-time, read-only view of all web views running in Studio Pro, showing each view's process ID, name, CPU, and memory usage. It helps users identify performance issues and report problematic web views to the Support team. This feature is only available for Windows.
**Enable Responsiveness Monitor** - detects when the application becomes unresponsive and writes diagnostic information to the log file.
**Enable Simple Progress Dialog** – enables the simplified version of the dialog that appears while Studio Pro is executing an operation (for example, saving a document).
**Optimize MPR** – starts an action that will remove allocated memory resources clean from a project file (.mpr) if they are from no longer required.
**Convert to Full Clone** – starts an action that will turn a [partially cloned](/refguide/clone-type/) application into full one.
**Fetch Repository** – starts an action that will fix a corrupted repository. This option is available for a partially-cloned repository only.
**Collect Version Control Data** – helps you to collect basic version control data kept in the logs of Studio Pro.
[Capture Maia Agent Session](/refguide/maia-make/#save-maia-session) – captures a Maia Session to help analyze Maia's responses and behavior for troubleshooting or support purposes.
[Collect Support Information](/refguide/collect-support-information/) – helps collect information that assists the Support team in finding the root causes of issues.
**Contact Support** – opens the Mendix Support page to help users report issues.
|
| **Open Log File Directory** | Opens the log files written by Studio Pro. Studio Pro retains these logs for the last 30 days, with files organized from most recent to oldest. You can use log files to diagnose issues or share them with Mendix Support when you submit a ticket. |
| **Welcome** | Opens the **Welcome** page, which displays information about the current Studio Pro version and includes links to release notes, Mendix platform blogs, Maia Learn, and Maia Chat. |
| **About Mendix Studio Pro** | Displays information about the current version of Mendix Studio Pro. |
diff --git a/content/en/docs/refguide/modeling/menus/help-menu/collect-support-information.md b/content/en/docs/refguide/modeling/menus/help-menu/collect-support-information.md
new file mode 100644
index 00000000000..0fd96334a9b
--- /dev/null
+++ b/content/en/docs/refguide/modeling/menus/help-menu/collect-support-information.md
@@ -0,0 +1,127 @@
+---
+title: "Collect Support Information"
+url: /refguide/collect-support-information/
+description: "Describes how to collect support information from Studio Pro, including device-specific information from the Make It Native app for native mobile apps."
+---
+
+## Introduction
+
+When you report an issue to Mendix Support, it helps to share details about your environment. **Collect Support Information** gathers these details in one place: information about your computer, Studio Pro, and your app, together with the Studio Pro log files.
+
+If your app has a native mobile profile, Studio Pro can also include device-specific information from the Make It Native app running on your phone or tablet. This information includes the device model, the operating system, network status, and the recent client logs of your app. It helps Support reproduce problems that only occur on a specific device or only at runtime.
+
+To start collecting support information, click **Help** > **Support Tools** > **Collect Support Information…**.
+
+## What Is Collected
+
+### Studio Pro and Computer Information
+
+The following information is always included:
+
+* System information (operating system, processor, screens, and so on)
+* CPU, memory, graphics, and disk information
+* Java and .NET information
+* Open panes and session length
+* Project information
+
+### Device Information from the Make It Native App {#device-information}
+
+When your app has a native mobile profile and a device is connected, the following information is added to the report:
+
+| Section | Contents |
+| --- | --- |
+| **Device** | Model, manufacturer, operating system and version, whether the device is an emulator or simulator, total memory, free disk space, and battery level |
+| **Network** | Connection type and whether the device is connected to a network |
+| **App** | App version, build number, bundle version, runtime URL, whether the app is a developer app, and the database name |
+| **Locale** | Device languages and time zone |
+| **Logs** | The most recent client log entries generated by the app on the device |
+
+{{% alert color="info" %}}
+Information that is not available on a device is shown as `N/A` in the report. For example, network information is only available when the app runs in the Make It Native app.
+{{% /alert %}}
+
+The client logs are kept in a limited buffer on the device. Only the most recent entries are collected (up to 500 entries or 200 KB). If the log was shortened, the report states how many entries were available in total.
+
+## Prerequisites
+
+To include device-specific information in the report, the following conditions must be met:
+
+* Your app has a native mobile profile.
+* The Studio Pro native packager is running. This is the case when you view your app on a device through Studio Pro.
+* The Make It Native app, or a custom developer app, is running on your device and is connected to the runtime of your app.
+
+If one of these conditions is not met, you can still collect the other support information, but the device-specific information will not be included.
+
+## Collecting Support Information
+
+1. Click **Help** > **Support Tools** > **Collect Support Information…**.
+1. Depending on your app and device, one of the following happens:
+
+ * **Your app has no native mobile profile:** Studio Pro starts collecting information straight away.
+ * **Your app has a native mobile profile and a device is connected:** Studio Pro starts collecting information straight away and includes device-specific information. A **Gather Native Device Information** step appears in the progress dialog.
+ * **Your app has a native mobile profile, but no device is connected:** Studio Pro displays a dialog explaining that the Make It Native app is not currently connected. For more information, see [Collecting Without a Connected Device](#no-device).
+
+1. Wait for Studio Pro to finish gathering the information. You can cancel the process at any time from the progress dialog.
+1. Review the report in the **Support Information** dialog.
+
+### Collecting Without a Connected Device {#no-device}
+
+If your app has a native mobile profile but no device is connected, Studio Pro shows the following message:
+
+> The Make It Native app is not currently connected. You can continue collecting support information, but device-specific information will not be included.
+>
+> To include device-specific information, connect the Make It Native app before continuing.
+
+You can choose between the following options:
+
+* **Continue** – collects the support information without device-specific information
+* **Cancel** – closes the dialog and does not collect any information
+
+To include device-specific information:
+
+1. Click **Cancel**.
+1. Connect the Make It Native app to the runtime of your app. For more information, see [Getting Started with Mobile](/refguide/mobile/getting-started-with-mobile/).
+1. Reproduce the scenario you want to report, so that the app generates the relevant logs.
+1. Run **Collect Support Information…** again.
+
+{{% alert color="info" %}}
+The device logs only contain entries from the time the app was connected. Connect the app and repeat the problematic scenario before you collect the support information, otherwise the logs may not contain the information that Support needs.
+{{% /alert %}}
+
+## Working with the Report
+
+The **Support Information** dialog shows the collected information as text. You can do the following:
+
+* **Copy to Clipboard** – copies the report so you can paste it into a support ticket or message
+* **Save** – asks you to select a folder and saves a `Support_Information__