Files
team/docs/main/administration-guide/configure/optimize-your-workspace.mdx
b5f007d35e docs: fix broken path links, anchors, and tab rendering from RST-to-MDX migration (#37433)
* docs: resolve cross-file anchor mismatches from RST-to-MDX migration

The Sphinx-to-Docusaurus migration converted `:ref:`/`{ref}` links using
naive text-slugification, so anchors that pointed to headings in a
different file (e.g. release-summary tables linking into their
respective changelog pages) were emitted as same-page fragments and
silently resolved to nothing.

Built a label registry from the original Sphinx `.. _label:` / `(label)=`
targets to recover the true source file for each cross-reference, then
rewrote the affected links to point at the correct file + heading
anchor. Fixes 282 broken cross-file anchors, primarily in the mobile/
desktop/server release-summary pages, plus assorted same-page anchor
mismatches caught by re-auditing after the prior admonition/anchor fix.

* docs: manually resolve remaining anchor mismatches after cross-file audit

Hand-verified fixes for anchors that fuzzy-matching alone couldn't
safely resolve (confirmed against actual heading text/context, and in a
few cases against the original RST source, before applying):

- Typos and dropped words carried over from the original Sphinx docs
  (e.g. "bot-acocunts", "auto-follow-all-new-channel-threads" ->
  "follow-all-new-channel-threads").
- Sphinx auto-generated duplicate-heading IDs (#id1/#id3/#id4) resolved
  to their real target headings.
- Numbered-step TOC links in enterprise-roll-out-checklist.mdx that
  dropped the leading "N. " used in the actual heading slugs.
- Push-notification docs pointing at the wrong file entirely
  (environment-configuration-settings instead of
  push-notification-server-configuration-settings).
- SAML "saml-enterprise" label resolved to its true cross-file target
  (authentication-configuration-settings#saml-2-0), recovered from the
  original RST label definition that the automated registry missed
  because it sat after an RST transition marker.
- sso-saml-technical references converted from broken same-page/
  malformed-path anchors to correct page links.

* docs: fix SAML 2.0 anchor slug (saml-2-0 -> saml-20)

github-slugger strips periods rather than hyphenating them, so "SAML
2.0" slugifies to saml-20, not saml-2-0 as previously fixed.

* docs: fix broken path links found during docs/main migration cleanup

* docs: convert div.tab blocks to Docusaurus Tabs/TabItem components

* docs: restore missing Kubernetes deployment architecture diagrams

The RST-to-MDX migration never copied over the AWS/Azure/Oracle
architecture diagrams referenced by the deployment-architecture-at-scale
page, leaving broken images in each Tabs/TabItem.

* docs: fix 7 anchor mismatches from the fragment/heading audit

Covers three root causes from the anchor mismatch breakdown:
- Fragment repeated the target page's own title instead of a real
  heading, so the link is simplified to point at the bare page.
- Heading exists verbatim but lives on a sibling settings page
  (experimental-configuration-settings, push-notification-server-
  configuration-settings) rather than environment-configuration-settings.
- A page path was mistakenly pasted into a same-page #fragment instead
  of being used as a real cross-page link.

* docs: fix 8 anchor slugs that were close but didn't match the real heading

Repoints links whose fragment was a plausible guess (typo, reworded
heading, or wrong section) at the actual auto-generated slug of the
target heading, confirmed by inspecting each target page directly.

* docs: merge split Tabs blocks so tabs render horizontally

The div.tab conversion script split some sibling tab groups into
separate single-item Tabs blocks whenever a stray blockquote marker
sat between them, causing them to render stacked instead of as one
horizontal tab bar. Merges the MySQL/PostgreSQL and Team/Enterprise
Edition tab groups back into single Tabs blocks.

* docs: remove Azure tab and restore Kubernetes deploy content

The Mattermost Operator, Azure, and Oracle platform tabs on the
Kubernetes deployment guide were split across two separate Tabs
blocks (rendering stacked instead of as one tab bar) and all three
tab bodies were empty because the migration never flattened the
original RST include directives. Removes the unsupported Azure tab
and restores the Mattermost Operator and Oracle content from the
pre-migration RST sources as a single merged Tabs block.

* addresscoderabbitreview

* docs: unify Linux/Kubernetes/Containers deploy pages and fix FIPS/STIG placement

Kubernetes and Containers duplicated full install content across a top-level
page (Tabs) and orphaned sidebar subpages that nothing linked to. Reworked
both to follow the Linux page's pattern: shared content on the landing page,
platform-specific instructions live once in their own subpage.

Also removed configure-fips-at-install-time.mdx, which claimed FIPS is
available for native Linux installs — FIPS/STIG in Mattermost is a container
image property (Chainguard-based build), not available outside Docker/
Kubernetes. Consolidated all FIPS/STIG references onto
containers/fips-stig.mdx and pointed the Mattermost Operator subpage (not
Oracle OKE, which doesn't expose image selection) at it.

* docs: fix review findings — image alt text, Important callout markup, typo

- Replace generic alt="image" on scaling diagrams with descriptive text
  identifying cloud provider and user scale.
- Convert raw div.important markup in deploy-containers.mdx to the
  repo's <Important> component, matching usage elsewhere in the file.
- Fix "Matermost" typo in manage-your-display-options.mdx.

---------

Co-authored-by: Hanzo Dev <[email protected]>
2026-07-10 14:50:13 +03:00

131 lines
5.5 KiB
Plaintext

---
title: "Optimize your Mattermost workspace"
---
<PlanAvailability slug="all-commercial" />
With workspace optimizations, system admins can review their workspace health and growth scores, then take advantage of recommended actions for ensuring their workspace is running smoothly and teams are maximizing productivity.
System admins can access their workspace optimization page in the System Console by selecting the **Product** <img src="/img/ui/products_E82F.svg" alt="Navigate between Channels, collaborative playbooks, and boards using the product menu icon." className="theme-icon" /> menu, selecting **System Console**, and going to **Reporting \> Workspace Optimization**.
![Review your workspace health and growth scores, then take advantage of recommended optimizations.](/images/workspace-optimization.png)
## How is the overall score calculated?
The highest score possible is 100. Your score is calculated based on the type of issue reported and the level of potential security risk introduced to your Mattermost deployment if ignored.
Each item on the dashboard is calculated based on its individual impact score. These differ depending on whether they're problems, warnings, or suggestions. For example, if SSL encryption isn't configured in your workspace, Mattermost reports that as a problem, which reduces your score until it's addressed.
Warnings impact your score less than problems, and suggestions have the least impact on your score.
Want to improve your overall workspace optimization score? Take action towards the problems, warnings, and suggestions reported on this dashboard. We recommend the following workspace optimizations.
## Recommendations
The following optimization areas can alert you to workspace suggestions, warnings, or problems that may require your attention:
<table style={{width: '100%'}}>
<colgroup>
<col style={{width: '7%'}} />
<col style={{width: '34%'}} />
<col style={{width: '57%'}} />
</colgroup>
<tbody>
<tr>
<td rowspan="2"><blockquote>
<p>Optimization category</p>
</blockquote>
<dl>
<dt>=======================</dt>
<dd>
<p>Mattermost release</p>
</dd>
</dl></td>
<td rowspan="2"><blockquote>
<p>Suggestions, Warnings, or Problems Detected</p>
</blockquote>
<dl>
<dt>==========================================================================================================</dt>
<dd>
<p>Are you on the latest Mattermost release?</p>
</dd>
</dl></td>
<td rowspan="2"><blockquote>
<p>Additional Information |</p>
</blockquote>
<dl>
<dt>======================================================================================================================================================================+</dt>
<dd>
<p>You're notified when updates are available. | See the <a href="mm-doc:%2Fadministration-guide%2Fupgrade%2Fupgrading-mattermost-server">Upgrade Mattermost</a> product documentation for details on upgrading your workspace. |</p>
</dd>
</dl></td>
</tr>
<tr>
</tr>
<tr>
<td>Configuration issues</td>
<td><ul>
<li><strong>SSL</strong>: Should your workspace be more secure with SSL?</li>
<li><strong>Session Length</strong>: The default value may not provide an optimal user experience.</li>
<li><strong>File Storage</strong>: Write access to the configured file storage location is required.</li>
</ul></td>
<td><dl>
<dt>See the product documentation to learn more: |</dt>
<dd>
<div class="line-block"></div>
</dd>
</dl>
<ul>
<li><a href="mm-doc:%2Fadministration-guide%2Fonboard%2Fssl-client-certificate">Set up SSL</a> |</li>
<li><a href="mm-ref:administration-guide%2Fconfigure%2Fenvironment-configuration-settings%3Asession%20lengths">Configure session length</a></li>
<li><dl>
<dt><a href="mm-ref:administration-guide%2Fconfigure%2Fenvironment-configuration-settings%3Afile%20storage">Configure file storage</a></dt>
<dd>
<h3 id="section">|</h3>
</dd>
</dl></li>
</ul></td>
</tr>
<tr>
<td>Workspace access</td>
<td>Is the Mattermost workspace accessible to users?</td>
<td>If your web server settings don't pass a live URL test, your workspace may not be accessible to others. | See the <a href="mm-ref:administration-guide%2Fconfigure%2Fenvironment-configuration-settings%3Aweb%20server">Web server configuration settings</a> product documentation to learn more:</td>
</tr>
<tr>
<td>Search performance</td>
<td>As your user base grows, is search getting slower?</td>
<td>See the <a href="mm-doc:%2Fadministration-guide%2Fscale%2Fenterprise-search">Enterprise search</a> product documentation to learn more. |</td>
</tr>
<tr>
<td>Data privacy</td>
<td>Do you need more control and insights into your data?</td>
<td><dl>
<dt>See the product documentation to learn more: |</dt>
<dd>
<div class="line-block"></div>
</dd>
</dl>
<ul>
<li><a href="mm-doc:%2Fadministration-guide%2Fcomply%2Fdata-retention-policy">Data Retention</a> |</li>
<li><a href="mm-doc:%2Fadministration-guide%2Fcomply%2Fcompliance-export">Compliance Export</a> |</li>
</ul></td>
</tr>
<tr>
<td>User authentication</td>
<td><ul>
<li><strong>AD/LDAP</strong>: As your user base grows, would you benefit from easier onboarding, automated deactivations, and role assignments?</li>
<li><strong>Guest accounts</strong>: Do you want to control user access to channels and teams with guest accounts?</li>
</ul></td>
<td><dl>
<dt>See the product documentation to learn more: |</dt>
<dd>
<div class="line-block"></div>
</dd>
</dl>
<ul>
<li><a href="mm-ref:administration-guide%2Fconfigure%2Fauthentication-configuration-settings%3Aad%2Fldap">AD/LDAP</a></li>
<li><a href="mm-doc:%2Fadministration-guide%2Fonboard%2Fguest-accounts">Guest accounts</a> |</li>
</ul></td>
</tr>
</tbody>
</table>