Update Desktop App managed configuration docs for macOS MDM

[Combs7th]

@claude - Please review the following Mattermost Desktop engineering PR for product documentation impact:

mattermost/desktop#3692

Goal:
Draft a minimal Mattermost Product Documentation update for the Desktop App admin/deployment docs covering macOS MDM-managed configuration support from Mattermost Desktop v6.2.0 onward.

Scope:

• User/admin-facing docs only.
• Focus on what admins can now do, not implementation details.
• Do not document code structure, policyConfigLoader internals, tests, or refactor details.
• Do not modify changelogs, upgrade notes, version archive, deprecated/removed feature pages, or unsupported-release docs.

Likely doc touchpoint:

• Desktop MSI installer / group policy / managed deployment docs, likely:
  source/deployment-guide/desktop/desktop-msi-installer-and-group-policy-install.rst

Required output:

1. Confirm the exact PR evidence that supports a docs update.
2. Identify the exact docs page/file to update.
3. Provide a ready-to-apply docs patch or before/after copy.
4. Keep the update short and admin-facing.

Suggested framing:
Admins can manage supported Desktop App organization-level configuration on macOS using MDM preference files, in addition to Windows group policy support.

[claude]

Claude finished @Combs7th's task in 3m 52s —— View job • claude/issue-8960-20260512-1624 • Create PR ➔

---

Task progress

• Read the target docs file
• Examine related Desktop deployment docs for context
• Attempt to fetch Mattermost Desktop PR I want edit/delete message's addtional file #3692 (blocked — see note below)
• Draft a minimal, admin-facing macOS MDM section
• Commit and push the patch
• Provide PR creation link

Summary

I drafted a short, admin-facing docs update for source/deployment-guide/desktop/desktop-msi-installer-and-group-policy-install.rst documenting macOS MDM-managed configuration support from Mattermost Desktop v6.2.0. Branch: claude/issue-8960-20260512-1624.

1) PR evidence

I was unable to independently fetch mattermost/desktop#3692 from this runner — gh, curl, and WebFetch are all blocked in the sandbox. The draft below relies on the framing already authored in this issue:

Admins can manage supported Desktop App organization-level configuration on macOS using MDM preference files, in addition to Windows group policy support.

Before merging, please verify against the PR:

• That v6.2.0 is the correct first-supported Desktop version.
• That the supported settings on macOS are exactly the same list as the Windows GPOs (EnableServerManagement, DefaultServerList, EnableAutoUpdates) — if the PR adds/omits any keys on macOS, the bullet list will need a tweak.
• Whether the PR introduces a specific preference domain or example payload (e.g. com.mattermost.Mattermost.plist) that admins would benefit from seeing in the docs. I deliberately omitted plist/key specifics rather than guess.

2) Doc page identified

source/deployment-guide/desktop/desktop-msi-installer-and-group-policy-install.rst — matches the touchpoint named in the issue. No existing macOS MDM content lives in source/deployment-guide/desktop/ (verified by grep), so this is a net-new section.

3) Patch (before / after)

Intro paragraph (added line under the existing intro):

This page provides guidance on installing the desktop app MSI and use Group Policies in Windows for Mattermost Enterprise or Professional. The MSI installer package can be downloaded `here <https://github.com/mattermost/desktop/releases/latest>`_.

From Mattermost Desktop v6.2.0, admins can also manage supported Desktop App organization-level configuration on macOS using MDM preference files, in addition to Windows group policy support. See the `macOS MDM-managed configuration <#macos-mdm-managed-configuration>`__ section below for details.

New section appended to the end of the page:

macOS MDM-managed configuration
-------------------------------

From Mattermost Desktop v6.2.0, admins can manage supported Desktop App organization-level configuration on macOS using MDM preference files, in addition to Windows group policy support.

To apply managed configuration on macOS, deploy a configuration profile for the Mattermost Desktop App through your MDM solution (for example, Jamf, Intune, Kandji, or Workspace ONE). The Desktop App reads the managed values on launch; restart the app for changes to take effect.

Supported settings mirror the Windows group policies listed earlier on this page, including:

- ``EnableServerManagement``
- ``DefaultServerList``
- ``EnableAutoUpdates``

4) Scope check

• User/admin-facing only — yes (capability + how to deploy, no code internals).
• No mention of policyConfigLoader, refactor, or tests.
• No changes to changelogs, upgrade notes, version archive, deprecated/removed features, or unsupported-release pages.
  · Branch

[Combs7th]

@claude - You were looking at the wrong PR. Please try again with this PR:

mattermost/desktop#3692

[claude]

Claude finished @Combs7th's task in 1m 46s —— View job

---

Same constraint as last run — I still cannot fetch mattermost/desktop#3692

The URL you re-shared is the same one I had before, so to be straightforward: I never read the PR in the prior run. This sandbox blocks gh, curl, and WebFetch against github.com/mattermost/desktop, so the previous patch was built from the framing in your issue body, not from PR evidence. That's almost certainly why it didn't line up with the actual change — version, framing, and supported keys were guesses, not verified facts.

I don't want to push another speculative patch onto a new branch. Two options to move forward:

---

Option A — You paste the PR evidence and I draft accurately

The minimum I need from mattermost/desktop#3692 to write copy I can stand behind:

1. PR title and a 2–3 sentence summary of what it actually does (verbatim from the description is best).
2. First-supported Desktop version (e.g. v6.2.0 — but only if that's what the PR/milestone says).
3. macOS preference domain (e.g. com.mattermost.Mattermost) and how admins are expected to deliver it (configuration profile / MDM, defaults write, etc.).
4. The list of managed keys honored on macOS. Specifically: does the PR honor the same keys as the existing Windows GPOs (EnableServerManagement, DefaultServerList, EnableAutoUpdates), or a different/expanded set? This was a guess last time.
5. Anything else admin-facing — e.g. a sample plist payload the PR ships, MDM solutions called out (Jamf, Intune, Kandji, Workspace ONE), behavior on app launch vs. restart.

A direct copy-paste of the PR description and the diff of any user-facing files (e.g. README, deployment docs in mattermost/desktop, or a sample .plist) is the fastest path.

Option B — I produce a conservative skeleton with placeholders

I can commit a section that establishes that macOS MDM-managed configuration is supported and points to the Windows GPO list as the canonical source of supported settings, but explicitly leaves the version number, preference domain, and key list as TODO for you to fill in. Lower risk of being wrong, but you'd still need to edit before publish.

---

Target page (unchanged from last run)

source/deployment-guide/desktop/desktop-msi-installer-and-group-policy-install.rst — confirmed. The Windows GPO list at lines 60–71 (EnableServerManagement, DefaultServerList, EnableAutoUpdates) is the natural anchor a macOS section should reference, regardless of which keys the PR ultimately supports.

State of this branch

claude/issue-8960-20260512-1630 currently has no commits beyond master. The earlier speculative patch is on a different branch (claude/issue-8960-20260512-1624) and is not affecting this one — if it shouldn't be merged, please ignore/close that branch.

Task list

• Attempt to fetch mattermost/desktop#3692 again (blocked — same as before)
• Confirm target docs page is correct
• Confirm this branch is clean (no speculative patch carried over)
• Awaiting PR evidence from you (Option A) or your go-ahead on a TODO-marked skeleton (Option B)
  · claude/issue-8960-20260512-1630

[Combs7th]

@claude - Answers for the macOS managed config docs PR:

PR title:
MM-46859 Refactor RegistryConfig into policyConfigLoader, include macOS CFPref support

Summary:
This PR adds support for macOS MDM-managed Desktop App configuration using CFPreferences. It allows organizations to preconfigure the same managed configuration items currently used with Windows GPO, including predefined servers, server management controls, and auto-updater controls. The PR includes a sample plist and local testing instructions.

First-supported Desktop version:
Mattermost Desktop v6.2.0, based on the PR milestone.

macOS preference domain / delivery method:
[NOT PRESENT IN PR — REQUIRES HUMAN JUDGMENT]
PR evidence shows a testing path of /Library/Managed Preferences/Mattermost.Desktop.plist, but the README also references com.Mattermost.Desktop as the bundle ID. Do not publish the exact preference domain until Devin confirms the correct value.

Managed keys honored on macOS:
The PR says macOS managed preferences use the same keys as Windows GPO:

• DefaultServerList
• EnableServerManagement
• EnableAutoUpdater

Admin-facing behavior:

• The PR includes a sample plist at resources/mac/mdm/example-managed-preferences.plist.
• The sample plist includes DefaultServerList, EnableServerManagement, and EnableAutoUpdater.
• The testing README says to copy the plist into Managed Preferences, ensure it is readable, then launch or relaunch the Desktop App.
• No specific MDM vendors are called out in the PR evidence.
• No production configuration profile payload is included beyond the sample plist/testing instructions.

Docs guidance:
Keep the public docs minimal. Add that from Mattermost Desktop v6.2.0, admins can manage supported Desktop App configuration on macOS using managed preferences/MDM, using the same supported keys as Windows GPO. Avoid publishing the exact preference domain until confirmed.

[claude]

Claude finished @Combs7th's task in 1m 47s —— View job • claude/issue-8960-20260512-1639 • Create PR ➔

---

Task list

• Read PR evidence from your comment
• Read target docs page and confirm anchors
• Check repo for existing macOS MDM content (none in deployment-guide/desktop/)
• Draft minimal admin-facing macOS MDM section
• Apply edit, commit, push to claude/issue-8960-20260512-1639

Summary

Committed a short, admin-facing macOS MDM section to source/deployment-guide/desktop/desktop-msi-installer-and-group-policy-install.rst (commit f9dd597). The section is appended after Advanced MSI options so the Windows MSI/GPO flow is left intact.

Applied patch

macOS managed configuration (MDM)
---------------------------------

From Mattermost Desktop v6.2.0, admins can manage supported Desktop App
configuration on macOS using managed preferences delivered through an MDM
solution, in addition to the Windows group policy support described above.
macOS managed preferences support the same configuration items as the
Windows group policies listed in the `Install group policy files locally
<#install-group-policy-files-locally>`__ section, including predefined
server lists, server management controls, and update notification controls.

To apply managed configuration on macOS, deploy a configuration profile
that sets the supported keys to client Macs through your MDM solution.
The Mattermost Desktop App reads managed preference values on launch;
restart the app after changing managed configuration for new values to
take effect.

Editorial decisions (please verify before merge)

1. No preference domain published. Per your guidance, the exact domain (Mattermost.Desktop vs com.Mattermost.Desktop) is omitted until confirmed.
2. No key names re-listed in the macOS section. Instead, the section links to the existing Windows GPO key table as the source of truth. This deliberately sidesteps a discrepancy worth flagging:
   • The Windows GPO table on this page (line 70) lists the update-notification key as EnableAutoUpdates (plural, trailing s).
   • Your PR-evidence note lists the macOS key as EnableAutoUpdater (singular, trailing r).
   • If these are genuinely different identifiers on the two platforms, the macOS section will eventually need to spell out its own key names rather than defer to the Windows table. If it's a typo in one place, that should be reconciled first. Worth getting Devin to confirm the exact macOS key spelling before any follow-up edit that names keys.
3. No testing path published. The PR's /Library/Managed Preferences/Mattermost.Desktop.plist and the sample resources/mac/mdm/example-managed-preferences.plist are dev/test artifacts, not admin-facing deployment instructions, so they're excluded.
4. No MDM vendor names (Jamf, Intune, Kandji, Workspace ONE) — none are called out in the PR, so the docs stay vendor-neutral.
5. Scope — no changelog, upgrade-notes, version-archive, deprecated, or unsupported-release pages were touched. The earlier speculative branch claude/issue-8960-20260512-1624 is untouched by this commit — if it should be discarded, please close/delete it separately.
   · claude/issue-8960-20260512-1639