mirror of
https://github.com/hanzoai/team.git
synced 2026-09-30 01:57:35 +00:00
b5f007d35e
* 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]>
51 lines
6.3 KiB
Plaintext
51 lines
6.3 KiB
Plaintext
---
|
|
title: "Purpose-Built Collaboration"
|
|
---
|
|
From large-scale logistics operations to critical infrastructure defense, organizations are under pressure to act faster, with fewer resources and greater operational complexity. But legacy chat platforms and multi-purpose messaging tools can't keep pace with dynamic, high-stakes workflows. They lack the integration depth, security controls, and mission-specific configurability needed for real-time operational success.
|
|
|
|
Mattermost provides a purpose-built collaboration platform designed for technical, operational, and industrial teams. It brings people, tools, and workflows together in a secure, extensible environment—streamlining coordination, improving decision velocity, and increasing resilience. Whether coordinating a global logistics chain, managing operational technology (OT) in the field, or running a security operations center, Mattermost adapts to your environment—not the other way around.
|
|
|
|
|
|
|
|
The following mission-ready collaboration capabilities are available:
|
|
|
|
## Global Logistics Coordination
|
|
|
|
Coordinating logistics across continents, agencies, and time zones requires a secure, unified platform that centralizes communications and aligns stakeholders.
|
|
|
|
**Benefits**
|
|
|
|
- **Enable real-time coordination** across supply chains, procurement, and field units with [channel-based messaging](/end-user-guide/messaging-collaboration) and [playbook-driven workflows](/end-user-guide/workflow-automation) that standardize communication and reduce friction.
|
|
- **Connect systems across logistics networks** by integrating ERP, fleet tracking, maintenance management, and transportation tools via [webhooks, APIs, and plugins](/integrations-guide/integrations-guide-index).
|
|
- **Preserve operational continuity** during outages or disruptions using [self-hosted deployments](/deployment-guide/server/server-deployment-planning#deployment-options) and [high availability architecture](/administration-guide/scale/high-availability-cluster-based-deployment) that eliminate reliance on third-party cloud services.
|
|
- **Support multilingual coordination** with [localized UI options](/end-user-guide/preferences/manage-your-display-options#language) in 20+ languages to ensure inclusive collaboration across global teams.
|
|
|
|
## Operational Technology and ICS Collaboration
|
|
|
|
OT and field operations in energy, utilities, manufacturing, and transportation sectors demand secure, real-time communication across widely distributed assets and personnel. From remote substations and industrial facilities to on-site emergency repair teams, teams must coordinate without exposing sensitive control systems or violating compliance standards.
|
|
|
|
Mattermost enables secure collaboration across OT environments and field operations, even under disconnected, air-gapped, or constrained network conditions.
|
|
|
|
**Benefits**
|
|
|
|
- **Enable compliant, real-time OT communications** across operational zones and facilities using [secure, on-prem collaboration](/deployment-guide/server/server-deployment-planning#deployment-options) that keeps data within your control perimeter.
|
|
- **Support field teams with hardened mobile access** using [EMM-based app provisioning](/deployment-guide/mobile/deploy-mobile-apps-using-emm-provider), [biometric authentication](/deployment-guide/mobile/mobile-security-features#biometric-authentication), [jailbreak detection](/deployment-guide/mobile/mobile-security-features#jailbreak-and-root-detection), and [ID-only push notifications](/administration-guide/configure/push-notification-server-configuration-settings#id-only-push-notifications)—ensuring that only authorized, uncompromised devices can access operational data.
|
|
- **Integrate with industrial monitoring systems** like SCADA, PI historians, and plant analytics using [alert-driven webhook and plugin integrations](/integrations-guide/integrations-guide-index) that push system events to relevant mobile or desktop channels.
|
|
- **Ensure system and network isolation** with [air-gapped deployment support](/deployment-guide/reference-architecture/deployment-scenarios/air-gapped-deployment) that allows full collaboration within OT enclaves and disconnected environments.
|
|
- **Prevent mobile data leakage** via [remote wipe capabilities](/security-guide/mobile-security#mobile-device-management-mdm)) and [screenshot/screen recording prevention](/deployment-guide/mobile/mobile-security-features#screenshot-and-screen-recording-prevention) for mobile devices used in the field.
|
|
|
|
## Technical Operational Command Centers
|
|
|
|
Engineering, infrastructure, and security teams manage increasingly complex environments. Whether responding to incidents, deploying software, or monitoring infrastructure, they need customizable workspaces that reduce cognitive load and integrate the tools they trust.
|
|
|
|
**Benefits**
|
|
|
|
- **Accelerate decision-making and incident response** using [Collaborative Playbooks](/end-user-guide/workflow-automation) to automate workflows for triage, patching, code releases, and security alerts.
|
|
- **Customize your collaboration environment** with [theming](/end-user-guide/preferences/customize-your-theme), [custom branding](/administration-guide/configure/custom-branding-tools), and [channel templates](/end-user-guide/messaging-collaboration) to mirror internal teams and operational domains.
|
|
- **Extend platform capabilities** with [slash commands, bots, and custom plugins](/integrations-guide/integrations-guide-index) that connect Mattermost to CI/CD systems, alerting frameworks, ticketing platforms, and internal tools.
|
|
- **Increase usability and team cohesion** with [custom emojis](/end-user-guide/collaborate/react-with-emojis-gifs#upload-custom-emojis), shared terminology, and [real-time messaging](/end-user-guide/messaging-collaboration) optimized for platform engineers, DevSecOps teams, and field service managers.
|
|
|
|
## Get Started
|
|
|
|
[Talk to an Expert](https://mattermost.com/contact-sales/) to create a secure, purpose-built collaboration environment aligned with your mission. Whether supporting distributed logistics, managing ICS environments, or running an operational command center, Mattermost adapts to your workflows—so your teams can move faster, respond smarter, and deliver with confidence.
|