Add blog post about system-wide policies#3326
Conversation
Co-authored-by: BornToBeRoot <16019165+BornToBeRoot@users.noreply.github.com>
Co-authored-by: BornToBeRoot <16019165+BornToBeRoot@users.noreply.github.com>
|
@copilot why did you update the yarn lock? |
Co-authored-by: BornToBeRoot <16019165+BornToBeRoot@users.noreply.github.com>
The |
| } | ||
| ``` | ||
|
|
||
| A `config.json.example` file is included in the application directory for reference. Simply rename it to `config.json` and set your desired policy values. Property names follow the pattern `Section_SettingName` — see the [settings documentation](https://borntoberoot.net/NETworkManager/docs/category/settings) for available policy names. |
There was a problem hiding this comment.
@copilot use this link: https://borntoberoot.net/NETworkManager/docs/system-wide-policies and adjust the sentence because the policy names are not there.
There was a problem hiding this comment.
Updated the link to point to https://borntoberoot.net/NETworkManager/docs/system-wide-policies and adjusted the sentence to remove the reference to policy names since they're not listed there. See f81162c.
…t sentence Co-authored-by: BornToBeRoot <16019165+BornToBeRoot@users.noreply.github.com>
|
@copilot Update the blog post based on the following docs: https://borntoberoot.net/NETworkManager/docs/system-wide-policies Also update the date to 19.02.2026 and that this feature is available since the pre-release version 2026.02.19.0 and can now be tested. |
…date date to 2026-02-19 Co-authored-by: BornToBeRoot <16019165+BornToBeRoot@users.noreply.github.com>
Updated the blog post in
Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
BornToBeRoot
left a comment
BornToBeRoot
left a comment
There was a problem hiding this comment.
@copilot review the comments, check the provided docs again.
|
|
||
| ## Request More Policies | ||
|
|
||
| Additional policy options will be added in future releases to provide more granular control over application behavior. If you have specific requirements for system-wide policies in your organization, please submit a feature request via the [GitHub issue tracker](https://github.com/BornToBeRoot/NETworkManager/issues/new/choose). |
There was a problem hiding this comment.
Added "to help us prioritize" to the sentence. See ab8173e.
| - Scripts and deployment toolkits — PowerShell scripts, PSAppDeployToolkit | ||
| - Manual deployment — hand-copy for small-scale rollouts | ||
|
|
||
| 4. **Verification** — Launch the application, navigate to Settings > [Update](https://borntoberoot.net/NETworkManager/docs/settings/update) (e.g., "Check for updates at startup"), and verify the shield icon and the administrator message appear and that the control is disabled. |
There was a problem hiding this comment.
@copilot update this... maybe with:
Navigate to Settings > Update (e.g., "Check for updates at startup")
Verify the shield icon and the administrator message appear and that the control is disabled
There was a problem hiding this comment.
Updated the verification step to a multi-line list matching the suggested wording. See ab8173e.
|
|
||
| Property names follow the pattern `Section_SettingName`. You can find the available policy names and values in the corresponding [setting's documentation](https://borntoberoot.net/NETworkManager/docs/category/settings). | ||
|
|
||
| ### Available Policies |
There was a problem hiding this comment.
@copilot It's not just this policy availble. Use this policy as an example. Until the release there will be more available, so keep this generic.
There was a problem hiding this comment.
Renamed the section to "Example Policy" and reworded to present Update_CheckForUpdatesAtStartup as just one example rather than the only available policy. See ab8173e.
…cation steps, add prioritize wording Co-authored-by: BornToBeRoot <16019165+BornToBeRoot@users.noreply.github.com>
All three review comments addressed in |
Changes proposed in this pull request
Website/blog/2026-02-19-system-wide-policies/covering system-wide policies: what they are, how to configureconfig.json, deployment methods (GPO, SCCM, Intune, scripts), and how to request additional policies via GitHub issues.Update_CheckForUpdatesAtStartuppolicy as a generic example with values and config snippet from the settings/update docs.system-wide-policy-indicator.pngscreenshot from docs.Related issue(s)
Copilot generated summary
Copilot summary
Adds a new Docusaurus blog post explaining system-wide policies for enterprise deployments. The post is aligned with the official documentation pages (system-wide-policies, settings, settings/update) and covers: introduction to policies, configuration via
config.json, an example policy (Update_CheckForUpdatesAtStartup) kept generic since more policies will be available by release, deployment methods, step-by-step verification instructions, and how to request additional policies to help prioritize future development. Includes the existing UI screenshot showing the policy indicator (shield icon + admin message).To-Do
Contributing
By submitting this pull request, I confirm the following:
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.