From ea7ca0d564836be9cf345f6baf083ea16f825267 Mon Sep 17 00:00:00 2001 From: Jesse Hallam Date: Fri, 12 Jun 2026 12:04:20 -0300 Subject: [PATCH 1/3] Remove CJK search feature flag mention now that it defaults to true (#9029) * Remove CJK search feature flag mention now that it defaults to true * Clarify CJK search defaults to true on v11.9, flag-gated on v11.5-v11.8 * Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- .../configure/enabling-chinese-japanese-korean-search.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/administration-guide/configure/enabling-chinese-japanese-korean-search.rst b/source/administration-guide/configure/enabling-chinese-japanese-korean-search.rst index 4fbb66e3ac9..3eebe335612 100644 --- a/source/administration-guide/configure/enabling-chinese-japanese-korean-search.rst +++ b/source/administration-guide/configure/enabling-chinese-japanese-korean-search.rst @@ -9,7 +9,8 @@ Chinese, Japanese and Korean search .. attention:: - Starting on Mattermost v11.5, searching for Chinese, Japanese or Korean (CJK) characters can be enabled with the `feature flag `_ ``MM_FEATUREFLAGS_CJKSEARCH``. + 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 `_ ``MM_FEATUREFLAGS_CJKSEARCH``. The general recommendation of `using either Elasticsearch or Opensearch once the server reaches 2.5 million posts `_ still applies. From fca7c9af6ea9408fac2e56a0bade15bce6389a72 Mon Sep 17 00:00:00 2001 From: "claude[bot]" <41898282+claude[bot]@users.noreply.github.com> Date: Sat, 13 Jun 2026 00:37:18 +0000 Subject: [PATCH 2/3] Document v11.8 classification markings and banners Add an end-user Classification markings section to display-channel-banners.rst and an admin Classification Markings section to site-configuration-settings.rst, covering global and channel-level classification banners in the web and desktop apps. Classification markings are informational only and don't control access. Co-authored-by: Combs7th --- .../configure/site-configuration-settings.rst | 29 +++++++++++++++++++ .../collaborate/display-channel-banners.rst | 9 ++++++ 2 files changed, 38 insertions(+) diff --git a/source/administration-guide/configure/site-configuration-settings.rst b/source/administration-guide/configure/site-configuration-settings.rst index 0865920b739..70a9a86099a 100644 --- a/source/administration-guide/configure/site-configuration-settings.rst +++ b/source/administration-guide/configure/site-configuration-settings.rst @@ -18,6 +18,7 @@ Review and manage the following site configuration options in the System Console - `Public Links <#public-links>`__ - `Notices <#notices>`__ - `Connected Workspaces <#connected-workspaces>`__ +- `Classification Markings <#classification-markings>`__ .. tip:: @@ -2589,6 +2590,34 @@ Member sync batch size ---- +Classification Markings +----------------------- + +From Mattermost v11.8, system admins can configure classification markings in the System Console by going to **Site Configuration > Classification Markings**. + +Classification markings define reusable classification levels that can be displayed as global or channel-level banners in the web and desktop apps. Each classification level includes a name, color, and rank order. You can select a preset, such as US DoD, NATO, UK GSCP, Canada, or Australia PSPF, or define custom classification levels. + +.. note:: + + Classification markings are informational only and aren't tied to access control decisions at this time. + +Configure classification markings: + +1. Go to **System Console > Site Configuration > Classification Markings**. +2. Enable **Enable classification markings**. +3. Select a **Classification preset**, or create custom classification levels. +4. Configure classification level names, colors, and rank order. +5. Optionally enable the **Global Classification Banner** under **Global Classification Indicators**. +6. Select the **Banner visibility**: + + - **Top only** + - **Top and bottom** + +7. Select the **Global classification level** to display. +8. Select **Save**. + +---- + config.json-only settings ------------------------- diff --git a/source/end-user-guide/collaborate/display-channel-banners.rst b/source/end-user-guide/collaborate/display-channel-banners.rst index c522ebc2cf6..699351e0303 100644 --- a/source/end-user-guide/collaborate/display-channel-banners.rst +++ b/source/end-user-guide/collaborate/display-channel-banners.rst @@ -36,3 +36,12 @@ Disable the **Channel Banner** option in the channel settings to remove the bann .. tip:: System admins can grant any user the ability to create and manage channel banners by assigning the **Manage Channel Banners** permission in the System Console. See the :doc:`advanced permissions ` documentation for details. + +Classification markings +----------------------- + +From Mattermost v11.8, system admins can configure classification markings that display as global or channel-level banners in the web and desktop apps. See the :ref:`Classification Markings ` configuration documentation for setup details. + +Classification markings use predefined or custom classification levels, including the classification name and banner color. These markings are informational only and don't control access to channels, messages, files, or other Mattermost resources. + +When a channel classification is applied, Mattermost displays the selected classification as the channel banner. Classification markings take priority over a custom channel banner when both are configured for the same channel. From e92bcfa99d2a57acea1b5bc8dbad25bd5c3406f4 Mon Sep 17 00:00:00 2001 From: Combs7th <147677911+Combs7th@users.noreply.github.com> Date: Fri, 12 Jun 2026 17:54:49 -0700 Subject: [PATCH 3/3] Removing unintended commits --- .../configure/enabling-chinese-japanese-korean-search.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/source/administration-guide/configure/enabling-chinese-japanese-korean-search.rst b/source/administration-guide/configure/enabling-chinese-japanese-korean-search.rst index 3eebe335612..4fbb66e3ac9 100644 --- a/source/administration-guide/configure/enabling-chinese-japanese-korean-search.rst +++ b/source/administration-guide/configure/enabling-chinese-japanese-korean-search.rst @@ -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 `_ ``MM_FEATUREFLAGS_CJKSEARCH``. + Starting on Mattermost v11.5, searching for Chinese, Japanese or Korean (CJK) characters can be enabled with the `feature flag `_ ``MM_FEATUREFLAGS_CJKSEARCH``. The general recommendation of `using either Elasticsearch or Opensearch once the server reaches 2.5 million posts `_ still applies.