Skip to content
Open
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -9,8 +9,7 @@ Chinese, Japanese and Korean search

.. attention::

Starting in Mattermost v11.9, CJK post search is enabled by default on PostgreSQL.
In Mattermost v11.5 through v11.8, enable the `feature flag <https://developers.mattermost.com/contribute/more-info/server/feature-flags/#changing-feature-flag-values>`_ ``MM_FEATUREFLAGS_CJKSEARCH``.
Starting on Mattermost v11.5, searching for Chinese, Japanese or Korean (CJK) characters can be enabled with the `feature flag <https://developers.mattermost.com/contribute/more-info/server/feature-flags/#changing-feature-flag-values>`_ ``MM_FEATUREFLAGS_CJKSEARCH``.

The general recommendation of `using either Elasticsearch or Opensearch once the server reaches 2.5 million posts <https://docs.mattermost.com/administration-guide/scale/enterprise-search.html#do-i-need-to-use-elasticsearch-or-aws-opensearch>`_ still applies.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ Prerequisites

- :doc:`Attribute-Based Access Control (ABAC) </administration-guide/manage/admin/attribute-based-access-control>` must be enabled by a System Admin in **System Console > System Attributes > Attribute-Based Access**.
- You need Channel Admin permissions and the ``manage_channel_access_rules`` permission.
- Channel access rules are available only for private channels.
- Self-service channel access rules in the **Access Control** tab in Channel Settings are configured for private channels. Membership policies apply to both public and private channels, with different behavior by channel type. See :ref:`Public and private channel behavior <administration-guide/manage/admin/abac-channel-access-rules:public and private channel behavior>`.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Combs7th This sentence is really clunky. Can you please give it another review?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good callout here! I agree.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@claude - Please analyze the sentence above through the lense of Editor Evie, and commit the best possible alternative version that's more clear, concise, and less clunky.

@claude claude Bot Jun 15, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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


Editor Evie review — line 23 rewrite

  • Read the target sentence and surrounding context
  • Load the Editor Evie persona
  • Rewrite the sentence for clarity/concision
  • Commit and push (56a7ce9)

What was clunky

Self-service channel access rules in the Access Control tab in Channel Settings are configured for private channels.

Through Evie's lens, the original had three issues:

  1. Stacked prepositions — "in the … tab in Channel Settings" repeats in back-to-back, which reads awkwardly.
  2. Vague passive verb — "are configured for private channels" buries the actual point. The rules don't get configured for private channels; they simply apply only to them. Readers couldn't tell whether this was a restriction or just a typical use case.
  3. Redundant noun — "channel access rules … in Channel Settings" repeats channel.

Committed rewrite

Self-service access rules in the Access Control tab of Channel Settings apply only to private channels. Membership policies apply to both public and private channels, with behavior that varies by channel type. See :ref:Public and private channel behavior.

Changes: dropped the redundant channel, swapped the second in for of, and replaced the passive "are configured for" with the crisp, accurate "apply only to" — which makes the public/private distinction in the next sentence land cleanly. Also tightened "with different behavior by channel type" → "with behavior that varies by channel type." The :ref: link is unchanged.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@amyblais @wiersgallak - Do you think that wording clean-up above will suffice?

We will still need a dev review from @isacikgoz as well whenever able.


Access Channel Settings
~~~~~~~~~~~~~~~~~~~~~~~~
Expand Down Expand Up @@ -86,6 +86,36 @@ When you save changes that affect membership, a confirmation dialog shows you:
- Option to view the specific users affected
- Confirmation required before applying changes

Public and private channel behavior
-----------------------------------

Membership policies behave differently depending on the type of channel they're applied to:

- **Private channels**: Membership policies are enforced. Users who match the policy's rules are added, and users who don't match the rules are removed during synchronization.
- **Public channels**: Membership policies are advisory. Matching users may be automatically added when auto-add is enabled, but non-matching members are not removed.
- When auto-add is disabled for a public channel, matching channels are surfaced as **recommended** rather than enforcing membership.
- Direct messages and group messages aren't eligible for membership policies.
- Default channels such as **Town Square** and **Off-Topic** are excluded.

.. note::

Public channels with membership policies may appear in **Browse Channels** under **Recommended**, and matching users may be marked **Recommended** in the channel invite flow. See :doc:`Browse channels </end-user-guide/collaborate/browse-channels>` and :doc:`Manage channel members </end-user-guide/collaborate/manage-channel-members>` for the end-user experience.

Channel-level permission policies
---------------------------------

From Mattermost v11.8.0, admins can define channel-level permission rules for file upload and file download based on user attributes and channel role. Applicable roles include **channel admin**, **channel member**, and **channel guest**.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
From Mattermost v11.8.0, admins can define channel-level permission rules for file upload and file download based on user attributes and channel role. Applicable roles include **channel admin**, **channel member**, and **channel guest**.
From Mattermost v11.8.0, channel admins can define channel-level permission rules for file upload and file download based on user attributes and channel role. Applicable roles include **channel admin**, **channel member**, and **channel guest**.


For system-wide permission policies that restrict file upload and download actions, see :ref:`Permission policies <administration-guide/manage/admin/abac-system-wide-policies:permission policies>`.

Simulate access
----------------

From Mattermost v11.8.0, admins can use **Simulate access** in Channel Settings to preview whether selected users can perform actions such as joining a channel, uploading files, or downloading files before saving policy changes.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
From Mattermost v11.8.0, admins can use **Simulate access** in Channel Settings to preview whether selected users can perform actions such as joining a channel, uploading files, or downloading files before saving policy changes.
From Mattermost v11.8.0, admins can use **Simulate access** in Channel Settings to preview whether selected users can perform actions such as uploading files or downloading files before saving policy changes.


- Simulation can evaluate draft rules before they're saved, so you can confirm the intended scope without affecting live channel access.
- Some denied results may indicate that the decision came from another policy. In that case, Mattermost shows that access was denied by another policy without exposing policy details you aren't authorized to see.

Manage team-scoped membership policies in Team Settings
-------------------------------------------------------

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -62,11 +62,21 @@ You can add multiple rules to a single policy, and each rule can include multipl

Select the **Validate syntax** bar to check the syntax of your rule. If the syntax is valid, the bar will turn green and display a message indicating that the syntax is valid. If there are any issues, the bar will turn red and display an error message.

Test rules
~~~~~~~~~~
Simulate access

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we explain these require enabling feature flags?

~~~~~~~~~~~~~~~~

Select **Test access rule** to test the rule against your user base to return how many users would be granted access to the channel based on the current rule. Test your rules to ensure the intended scope and avoid unexpected access changes.

From Mattermost v11.8.0, you can use **Simulate access** to preview allowed and denied outcomes for specific users before saving policy changes:

1. Open the policy editor in the System Console.
2. Select **Simulate access**.
3. Choose the users you want to test.
4. Review the allowed and denied outcomes by action, such as joining a channel or uploading and downloading files.
5. Adjust the rules before saving.

Simulation can test draft policy changes before they affect live channel access or file permissions. Detailed rule and attribute information is shown only when the denial comes from the policy or scope you're editing; otherwise, Mattermost may show that access was denied by another policy.
Comment thread
Combs7th marked this conversation as resolved.

Manage rules
~~~~~~~~~~~~

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -40,11 +40,14 @@ Configure access policies

Once enabled, you have multiple ways to configure access policies in Mattermost:

From Mattermost v11.8.0, admins can configure membership policies for both public and private channels, permission policies for file upload and file download, and simulate policy outcomes before saving.

**System Admins can:**

- Create :doc:`system-wide access policies </administration-guide/manage/admin/abac-system-wide-policies>` that can be assigned across multiple channels in the System Console.
- Create :doc:`system-wide access policies </administration-guide/manage/admin/abac-system-wide-policies>` that can be assigned across multiple channels in the System Console. Membership policies can be applied to both public and private channels, with :ref:`advisory behavior on public channels <administration-guide/manage/admin/abac-channel-access-rules:public and private channel behavior>`.
- Assign :ref:`individual channel policies <administration-guide/manage/admin/abac-system-wide-policies:define access controls per channel>` to specific channels in the System Console.
- Define :ref:`permission policies <administration-guide/manage/admin/abac-system-wide-policies:permission policies>` that restrict actions such as file upload and file download based on user attributes.
- :ref:`Simulate policy outcomes <administration-guide/manage/admin/abac-system-wide-policies:simulate access>` to preview whether selected users can perform actions such as joining a channel or uploading and downloading files before saving policy changes.

**Team Admins can:**

Expand Down
4 changes: 4 additions & 0 deletions source/end-user-guide/collaborate/browse-channels.rst
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,10 @@ Browse channels

From Mattermost v9.1, you can filter the list of channels by public, private, or archived channels, and you can hide all channels you're already a member of.

.. note::

From Mattermost v11.8.0, if your organization uses membership policies, **Browse Channels** may include a **Recommended** filter. Recommended channels are public channels your attributes match. You can still browse and join public channels according to your organization's normal channel permissions.

.. tab:: Mobile

1. Tap the **Plus** |plus| icon located in the top right corner of the app.
Expand Down
12 changes: 11 additions & 1 deletion source/end-user-guide/collaborate/join-leave-channels.rst
Original file line number Diff line number Diff line change
Expand Up @@ -107,4 +107,14 @@ When you leave a private channel, you must be re-added by another channel member

.. image:: ../../images/mobile-confirm-leave-a-channel.jpg
:alt: Tap on Leave to confirm your choice.
:scale: 30
:scale: 30

Leave a public channel added by a membership policy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

From Mattermost v11.8.0, when you leave a public channel you were added to by a membership policy, Mattermost asks you to confirm:

- Choosing **Leave channel** removes you from the channel.
- Choosing **Mute instead** keeps you in the channel and mutes its notifications.

If the channel is already muted, Mattermost shows **Cancel** and **Leave channel** instead of **Mute instead**.
Comment thread
Combs7th marked this conversation as resolved.
5 changes: 4 additions & 1 deletion source/end-user-guide/collaborate/manage-channel-members.rst
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,10 @@ Add members to a channel

Any member of a channel can add other members to public or private channels, unless your system admin has restricted access to do so.

When a channel has :doc:`attribute-based access controls </administration-guide/manage/admin/attribute-based-access-control>` enabled, you'll see details about which user attributes are permitted access to the channel. Only users who meet the requirements appear in search results when adding members to that channel.
When a channel has :doc:`attribute-based access controls </administration-guide/manage/admin/attribute-based-access-control>` enabled, you'll see details about which user attributes are permitted access to the channel. Behavior when adding members depends on the channel type:

- **Private channels with membership policies**: Only users who meet the policy requirements are available to add.
- **Public channels with membership policies**: Users who match the policy may be shown with a **Recommended** tag, but the invite list isn't restricted by the policy.

.. tab:: Web/Desktop

Expand Down
Loading