Integration permission management changes

[Combs7th]

@claude, Let's update the Mattermost Product Documentation to reflect the admin product experience from Mattermost server v11.2 onward captured via engineering PR mattermost/mattermost#34421

Before proposing any changes:

• Summarize what has changed in the product from an admin or system admin perspective.
• Identify which roles or permissions are involved or potentially affected by this change.
• Determine whether this change introduces new capabilities, modifies existing permissions, or clarifies previously implicit behavior.
• Identify the most appropriate existing documentation page(s), especially those related to administration, roles, or permissions.
• Analyze the writing style, tone, structure, headings, and formatting patterns used on those pages.

When drafting updates:

• Match the existing voice and writing patterns of the page as closely as possible.
• Follow the same heading hierarchy and formatting conventions already in use.
• Avoid introducing new sections unless absolutely necessary.
• Do not assume permission or role behavior beyond what is explicitly stated or clearly implied in the PR.

Focus the docs update on:

• What has changed from the admin’s perspective.
• Where this functionality or permission is configured or surfaced in the System Console.
• When or why an admin would need to be aware of this change.
• Any explicit role or permission requirements tied to this capability.

DO NOT suggest changes to the following docs pages:

• changelogs
• important upgrade notes
• version archive
• removed and deprecated features
• unsupported legacy releases

[claude]

Claude finished @Combs7th's task —— View job • claude/issue-8616-20260108-0303 • Create PR ➔

---

Integration permission management changes

I've successfully updated the Mattermost Product Documentation to reflect the admin experience changes from v11.2 onward based on the engineering changes.

Tasks:

• Analyze the engineering PR to understand what changed from admin perspective
• Identify roles/permissions affected by the changes
• Research existing documentation pages for style/structure patterns
• Determine appropriate documentation pages to update
• Draft updates matching existing voice and formatting
• Update documentation files
• Commit and push changes

Summary of Changes Made:

What changed from an admin perspective (v11.2):

• Permission schemes now fully expose controls for managing other users' integrations (Webhooks, Slash Commands, OAuth Apps) in the System Console for greater administrative clarity
• Permissions for managing your own integrations have been renamed for consistency
• A new configuration option allows administrators to enforce Incoming Webhook channel locking

Documentation Updates:

1. Integration Configuration Settings (/source/administration-guide/configure/integrations-configuration-settings.rst):

   • Added new EnforceIncomingWebhookChannelLocking setting documentation with proper formatting and examples

2. Advanced Permissions (/source/administration-guide/onboard/advanced-permissions.rst):

   • Enhanced integration management section to highlight v11.2 improvements for separate own vs. others' integration permissions

3. Incoming Webhooks (/source/integrations-guide/incoming-webhooks.rst):

   • Updated step 4 to reference the new administrative channel locking enforcement capability

The updates follow existing documentation patterns and provide administrators with clear guidance on the new integration permission management capabilities introduced in Mattermost v11.2.