diff --git a/doc/qtcreator/src/debugger/qtquick-debugger-example.qdoc b/doc/qtcreator/src/debugger/qtquick-debugger-example.qdoc
index dd63e607b10..51afd4ba68f 100644
--- a/doc/qtcreator/src/debugger/qtquick-debugger-example.qdoc
+++ b/doc/qtcreator/src/debugger/qtquick-debugger-example.qdoc
@@ -49,6 +49,13 @@
     For more information about all the options you have, see
     \l{Debugging Qt Quick Projects}.
 
+    \if defined(qtdesignstudio)
+    \note In this section, you are using advanced menu items. These are not
+    visible by default. To toggle the visibility of advanced menu items, see
+    \l{Customizing the Menu}.
+
+    \endif
+
     The Same Game demo shows how to write a game in QML, using JavaScript for
     all the game logic. Open the demo project in \QC to debug it:
 
diff --git a/doc/qtcreator/src/debugger/qtquick-debugging.qdoc b/doc/qtcreator/src/debugger/qtquick-debugging.qdoc
index 6f6ca89f450..02897e71a94 100644
--- a/doc/qtcreator/src/debugger/qtquick-debugging.qdoc
+++ b/doc/qtcreator/src/debugger/qtquick-debugging.qdoc
@@ -48,6 +48,12 @@
     For an example of how to debug Qt Quick Projects, see
     \l{Debugging a Qt Quick Example Application}.
 
+    \if defined(qtdesignstudio)
+    \note In this section, you are using advanced menu items. These are not
+    visible by default. To toggle the visibility of advanced menu items, see
+    \l{Customizing the Menu}.
+    \endif
+
     \section1 Setting Up QML Debugging
 
     \if defined(qtcreator)
diff --git a/doc/qtcreator/src/qtquick/qtquick-profiler.qdoc b/doc/qtcreator/src/qtquick/qtquick-profiler.qdoc
index 8711cbbb51a..990acc587fa 100644
--- a/doc/qtcreator/src/qtquick/qtquick-profiler.qdoc
+++ b/doc/qtcreator/src/qtquick/qtquick-profiler.qdoc
@@ -80,6 +80,12 @@
     {Chrome Trace Format Viewer}.
     \endif
 
+    \if defined(qtdesignstudio)
+    \note In this section, you are using advanced menu items. These are not
+    visible by default. To toggle the visibility of advanced menu items, see
+    \l{Customizing the Menu}.
+    \endif
+
     \section1 Using QML Profiler
 
     To monitor the performance of an application in the QML Profiler:
diff --git a/doc/qtcreator/src/user-interface/creator-ui.qdoc b/doc/qtcreator/src/user-interface/creator-ui.qdoc
index 43645074980..67e4f7a5f50 100644
--- a/doc/qtcreator/src/user-interface/creator-ui.qdoc
+++ b/doc/qtcreator/src/user-interface/creator-ui.qdoc
@@ -132,6 +132,27 @@
                 \uicontrol Keyboard
     \endtable
 
+    \if defined(qtdesignstudio)
+    \section1 Customizing the Menu
+
+    By default, top-level menu items \uicontrol Build, \uicontrol Debug, and
+    \uicontrol Analyze are not visible. These menu items contain options for
+    advanced functionality.
+
+    To toggle the visibility of these menu items:
+    \list 1
+      \li Go to \uicontrol Tools > \uicontrol Options.
+      \li On the \uicontrol Environment tab, select
+      \uicontrol{Qt Design Studio Configuration}.
+      \li Clear the checkbox for the items that you want to be visible.
+    \endlist
+
+    \image studio-menu-item-visibility.png
+
+    You need to restart \QDS to apply changes made to these settings.
+
+    \endif
+
     \section1 Switching UI Themes
 
     Themes enable you to change the appearance of the UI from dark to light,
diff --git a/doc/qtdesignstudio/images/studio-menu-item-visibility.png b/doc/qtdesignstudio/images/studio-menu-item-visibility.png
new file mode 100644
index 00000000000..c36525fbe1b
Binary files /dev/null and b/doc/qtdesignstudio/images/studio-menu-item-visibility.png differ
diff --git a/doc/qtdesignstudio/src/developers/studio-designer-developer-workflow.qdoc b/doc/qtdesignstudio/src/developers/studio-designer-developer-workflow.qdoc
index e636251eac1..629642abd70 100644
--- a/doc/qtdesignstudio/src/developers/studio-designer-developer-workflow.qdoc
+++ b/doc/qtdesignstudio/src/developers/studio-designer-developer-workflow.qdoc
@@ -30,6 +30,10 @@
 
     \title Designer-Developer Workflow
 
+    \note In this section, you are using advanced menu items. These are not
+    visible by default. To toggle the visibility of advanced menu items, see
+    \l{Customizing the Menu}.
+
     \QDS enables designers and developers to work together on common
     projects to develop applications. Designers use the \l{Design Views}{views}
     in the \uicontrol Design mode to modify \l{UI Files}{UI files} (\e .ui.qml),
diff --git a/doc/qtdesignstudio/src/overviews/qtquick-export.qdoc b/doc/qtdesignstudio/src/overviews/qtquick-export.qdoc
index 2aed8fea62d..f3042336bb8 100644
--- a/doc/qtdesignstudio/src/overviews/qtquick-export.qdoc
+++ b/doc/qtdesignstudio/src/overviews/qtquick-export.qdoc
@@ -30,6 +30,10 @@
 
     \title Exporting Components
 
+    \note In this section, you are using advanced menu items. These are not
+    visible by default. To toggle the visibility of advanced menu items, see
+    \l{Customizing the Menu}.
+
     \l{glossary-component}{Components} contained in \l{UI Files}
     {UI files} (.ui.qml) can be exported to JSON metadata format and PNG assets.
 
diff --git a/doc/qtdesignstudio/src/qtdesignstudio-packaging.qdoc b/doc/qtdesignstudio/src/qtdesignstudio-packaging.qdoc
index 8f43fca3902..d908bd0dba1 100644
--- a/doc/qtdesignstudio/src/qtdesignstudio-packaging.qdoc
+++ b/doc/qtdesignstudio/src/qtdesignstudio-packaging.qdoc
@@ -30,6 +30,10 @@
 
     \title Packaging Applications
 
+    \note In this section, you are using advanced menu items. These are not
+    visible by default. To toggle the visibility of advanced menu items, see
+    \l{Customizing the Menu}.
+
     When you are ready to deliver your application to users or upload it to
     app stores, you can use \QDS to create suitable packages that contain all
     the necessary files, such as fonts, images, components, and modules.