This commit is contained in:
Paolo Matarazzo 2025-03-05 07:06:14 -05:00
parent 6ea14739d0
commit 14bd4a8ee3

View File

@ -9,7 +9,7 @@ ms.author: paoloma
# Configure the Settings page visibility
*Settings* is a Windows application that offers a unified interface to manage the system settings. In certain scenarios, you might want to restrict access to specific settings pages to ensure a more controlled and secure environment. This is especially beneficial for devices used in specific environments, such as kiosks or student devices, where limiting access to certain settings can prevent unauthorized changes and maintain a consistent user experience.
*Settings* is a Windows application that offers a unified interface to manage the system settings. In certain scenarios, you might want to restrict access to specific Settings pages to ensure a more controlled and secure environment. This is especially beneficial for devices used in specific environments, such as kiosks or student devices, where limiting access to certain options can prevent unauthorized changes and maintain a consistent user experience.
:::image type="content" source="images/settings-page-visibility.png" alt-text="Screenshot of the Settings app configured with a policy setting to limit the categories displayed." border="false":::
@ -17,23 +17,27 @@ This article explains how to configure the Settings app and how to implement the
## Page visibility list policy setting
You can configure the visibility of settings pages using the *page visibility list* policy setting. This policy allows you to block a given set of pages from the Settings app. Blocked pages aren't visible in the app and can't be accessed through direct navigation via Uniform Resource Identifier (URI), context menu in Explorer, or other means. Direct navigation to a blocked page results in the first page of Settings displayed instead.
You can configure the visibility of Settings pages using the *page visibility list* policy setting. This policy allows you to block a given set of pages from the Settings app. Blocked pages aren't visible in the app and can't be accessed through direct navigation via Uniform Resource Identifier (URI), context menu in Explorer, or other means. Direct navigation to a blocked page results in the first page of Settings displayed instead.
The page visibility list policy setting has two modes:
The page visibility list policy has two modes:
- Specify a list of settings pages to show. In this case, the policy string must begin with `showonly:`. After this, the policy string must contain a semicolon-delimited list of settings page identifiers. The identifier for any given settings page is the published URI for that page, minus the `ms-settings:` protocol part
- Specify a list of pages to hide. In this case, the policy string must begin with `hide:`. After this, the policy string must contain a semicolon-delimited list of settings page identifiers. The identifier for any given settings page is the published URI for that page, minus the `ms-settings:` protocol part
- **Show Specific Pages**
- Start the policy string with `showonly:`
- Follow it with a list of Settings page identifiers, separated by semicolons
- **Hide Specific Pages**
- Start the policy string with `hide:`
- Follow it with a list of Settings page identifiers, separated by semicolons
> [!NOTE]
> For the list of categories and page identifiers that can be configured, see [ms-settings: URI scheme reference](https://go.microsoft.com/fwlink/?linkid=2102995#ms-settings-uri-scheme-reference).
> The identifier for any Settings page is the published URI for that page, minus the `ms-settings:` protocol part. For the list of categories and page identifiers, see [ms-settings: URI scheme reference](https://go.microsoft.com/fwlink/?linkid=2102995#ms-settings-uri-scheme-reference).
## Examples
To specify that only the **About** and **Bluetooth** pages should be shown (their respective URIs are `ms-settings:about` and `ms-settings:bluetooth`) and all other pages hidden:
Show only the **About** and **Bluetooth** pages. Their respective URIs are `ms-settings:about` and `ms-settings:bluetooth`:
`showonly:about;bluetooth`
To specify that only the Bluetooth page (URI `ms-settings:bluetooth`) should be hidden:
Hide only the Bluetooth page, which has the URI `ms-settings:bluetooth`:
`hide:bluetooth`
@ -55,7 +59,7 @@ Alternatively, you can configure devices using a [custom policy][INT-1] with the
| Setting |
|--|
|- **OMA-URI:** `./Device/Vendor/MSFT/Policy/Config/Settings/PageVisibilityList`<br>- **Data type:** string<br>- **Value:** List of URIs to show or hide, separated by semicolons.<br><br>or<br><br>- **OMA-URI:** `./User/Vendor/MSFT/Policy/Config/Settings/PageVisibilityList`<br>- **Data type:** string<br>- **Value:** List of URIs to show or hide, separated by semicolons.|
|- **OMA-URI:** `./Device/Vendor/MSFT/Policy/Config/Settings/PageVisibilityList`<br>- **Data type:** string<br>- **Value:** List of URIs to show or hide, separated by semicolons.<br><br>Or<br><br>- **OMA-URI:** `./User/Vendor/MSFT/Policy/Config/Settings/PageVisibilityList`<br>- **Data type:** string<br>- **Value:** List of URIs to show or hide, separated by semicolons.|
#### [:::image type="icon" source="../images/icons/group-policy.svg" border="false"::: **GPO**](#tab/gpo)
@ -63,7 +67,7 @@ Alternatively, you can configure devices using a [custom policy][INT-1] with the
| Group policy path | Group policy setting | Value |
| - | - | - |
| **Computer Configuration\Administrative Templates\Control Panel**<br><br>or<br><br>**User Configuration\Administrative Templates\Control Panel** | Settings Page Visibility | **Enabled**|
| **Computer Configuration\Administrative Templates\Control Panel**<br><br>Or<br><br>**User Configuration\Administrative Templates\Control Panel** | Settings Page Visibility | List of URIs to show or hide, separated by semicolons.|
[!INCLUDE [gpo-settings-2](../../../includes/configure/gpo-settings-2.md)]
@ -71,7 +75,7 @@ Alternatively, you can configure devices using a [custom policy][INT-1] with the
## User Experience
By controlling the visibility of Settings pages, you can create a customized user experience tailored to your organization's specific needs. Once the policy is applied, users will have access only to the Settings pages you have explicitly allowed, ensuring a focused and streamlined interface.
By controlling the visibility of Settings pages, you can create a customized user experience tailored to your organization's specific needs. Once the policy is applied, users have access only to the Settings pages you explicitly allow, ensuring a focused and streamlined interface.
<!--links-->