Update system-wide-policies.md

Author: BornToBeRoot

Website/docs/system-wide-policies.md

@@ -24,6 +24,16 @@ The `config.json` file uses a simple JSON structure to define policy values. An
 
 **File Format:**
 
+```json
+{
+  "Policy_Name1": true,
+  "Policy_Name2": "ExampleValue"
+}
+```
+
+
+**Example:**
+
 ```json
 {
   "Update_CheckForUpdatesAtStartup": false
@@ -54,50 +64,14 @@ Controls whether the application checks for updates at startup for all users.
 - `false` - Force disable automatic update checks at startup for all users
 - Omit the property - Allow users to control this setting themselves
 
-**Example (disable updates):**
-
-```json
-{
-  "Update_CheckForUpdatesAtStartup": false
-}
-```
-
-**Example (enable updates):**
-
-```json
-{
-  "Update_CheckForUpdatesAtStartup": true
-}
-```
-
-:::tip Use Case
-
-This is particularly useful for enterprise deployments where you want to:
-- Ensure consistent update check behavior across all users
-- Prevent users from being prompted about updates when you manage updates centrally
-- Enforce update checks to ensure users are notified of important security updates
-
-:::
-
-## User Experience
-
-When a setting is controlled by a system-wide policy:
-
-1. **Settings UI**: The toggle/control for the setting is disabled
-2. **Visual Indicator**: An orange shield icon appears next to the setting
-3. **Administrator Message**: The text "This setting is managed by your administrator" is displayed
-4. **Value Display**: The UI shows the value set by the administrator (enabled or disabled)
-
-This provides clear feedback to users about which settings are under administrative control and what values are being enforced.
-
 ## Deployment
 
 For enterprise deployments:
 
 1. **Create the configuration file**: 
    - Use the `config.json.example` as a template
    - Rename it to `config.json`
-   - Set your desired policy values
+   - Set your desired policy values (you find them in the corresponding setting's documentation)
 
 2. **Deploy to installation directory**:
    - Place the `config.json` file in the same directory as `NETworkManager.exe`
@@ -106,13 +80,12 @@ For enterprise deployments:
 
 3. **Deploy methods**:
    - Group Policy (copy file to installation directory)
-   - Configuration management tools (Ansible, SCCM, etc.)
-   - MSI deployment scripts
-   - Manual deployment for small-scale rollouts
+   - Configuration management tools (SCCM, Intune, etc.)
+   - Scripts/Deployment tools (PowerShell, PSAppDeployToolkit, etc.)   
 
 4. **Verification**:
    - Launch the application
-   - Navigate to Settings > Update
+   - Navigate to a setting that is controlled by the policy (e.g., "Check for updates at startup")
    - Verify the shield icon and administrator message appear
    - Confirm the toggle reflects the policy value and is disabled