mirror of
https://github.com/hanzoai/team.git
synced 2026-10-30 14:49: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]>
232 lines
12 KiB
Plaintext
232 lines
12 KiB
Plaintext
---
|
||
title: "Troubleshoot notifications"
|
||
---
|
||
import Tabs from '@theme/Tabs';
|
||
import TabItem from '@theme/TabItem';
|
||
|
||
<PlanAvailability slug="all-commercial" />
|
||
|
||
The Mattermost notifications you receive depend on your [Mattermost preferences](#check-your-mattermost-preferences), the [Mattermost client](#check-your-mattermost-client-settings) you're using, and the [operating system (OS)](#check-your-operating-system-settings) you're running Mattermost on.
|
||
|
||
## Send yourself a test notification
|
||
|
||
From Mattermost v10.3, you can send yourself a test notification by selecting **Settings** <img src="/img/ui/settings-outline_F08BB.svg" alt="Use the Settings icon to customize your Mattermost user experience." className="theme-icon" />, and going to the **Notifications** options.
|
||
|
||
Under **Troubleshooting notifications** select the **Send a test notification** option. If notifications are working, you'll receive a system-bot direct message in Mattermost confirming that notifications are working.
|
||
|
||
If you don't receive a system-bot direct message, see the following sections for troubleshooting steps you can follow to ensure you're receiving the notifications you want.
|
||
|
||
## Check your Mattermost preferences
|
||
|
||
Start by ensuring that your Mattermost preferences have notifications enabled.
|
||
|
||
<Tabs>
|
||
<TabItem value="desktop" label="Desktop">
|
||
|
||
1. Select **Settings** <img src="/img/ui/settings-outline_F08BB.svg" alt="Use the Settings icon to customize your Mattermost user experience." className="theme-icon" /> in the top right corner of Mattermost.
|
||
2. Select **Desktop and mobile notifications**.
|
||
|
||
If **Send notifications for** is set to **Nothing**, then Mattermost notifications are currently disabled. Select either the **All new messages** or **Mentions, direct messages, and group messages** option instead, and save your changes.
|
||
|
||
|
||
|
||
</TabItem>
|
||
<TabItem value="web" label="Web">
|
||
|
||
1. Select **Settings** <img src="/img/ui/settings-outline_F08BB.svg" alt="Use the Settings icon to customize your Mattermost user experience." className="theme-icon" /> in the top right corner of Mattermost.
|
||
2. Select **Desktop and mobile notifications**.
|
||
|
||
If **Send notifications for** is set to **Nothing**, then Mattermost notifications are currently disabled. Select either the **All new messages** or **Mentions, direct messages, and group messages** option instead.
|
||
|
||
</TabItem>
|
||
<TabItem value="mobile" label="Mobile">
|
||
|
||
1. Tap on your profile picture in the bottom right corner of Mattermost.
|
||
2. Tap **Settings** <img src="/img/ui/settings-outline_F08BB.svg" alt="Use the Settings icon to customize your Mattermost user experience." className="theme-icon" />.
|
||
3. Tap **Notifications**.
|
||
4. Tap **Push Notifications**.
|
||
5. Ensure that **All new messages** or **Mentions, direct messages, and group messages** option is selected.
|
||
6. Under **Trigger push notifications when…**, select **Online, away or offline** to always receive notifications.
|
||
|
||
</TabItem>
|
||
</Tabs>
|
||
|
||
|
||
We recommend checking your Mattermost client settings next.
|
||
|
||
## Check your Mattermost client settings
|
||
|
||
<Tabs>
|
||
<TabItem value="desktop" label="Desktop">
|
||
|
||
Ensure notifications are enabled in your Mattermost server connection.
|
||
|
||
1. Select the Mattermost Server option in the top left of the desktop app, then edit the server details.
|
||
2. Under **Permissions**, enable **Notifications** and save your changes.
|
||
|
||
|
||
|
||
</TabItem>
|
||
<TabItem value="web" label="Web">
|
||
|
||
If you prefer to use Mattermost in a web browser, you must grant notification permissions for Mattermost in the web browser. If you don't, the web browser can block you from receiving Mattermost notifications.
|
||
|
||
Select the **Chrome**, **Edge**, **Firefox**, or **Safari** tab below based on your preferred web browser:
|
||
|
||
<Tabs>
|
||
<TabItem value="chrome" label="Chrome">
|
||
|
||
Grant notification permissions for Mattermost in your Chrome web browser.
|
||
|
||
1. From the Chrome menu, select **Settings**.
|
||
2. Select **Privacy and Security** in the left pane.
|
||
3. Expand **Site settings**.
|
||
4. Under **Permissions**, expand **Notifications**.
|
||
5. Enable the **Sites can ask to send notifications** option, and add your Mattermost workspace URL to the **Allowed to send notifications** list.
|
||
|
||
</TabItem>
|
||
<TabItem value="edge" label="Edge">
|
||
|
||
Grant notification permissions for Mattermost in your Edge web browser.
|
||
|
||
1. From the Edge menu, select the **Settings and more (...)** option.
|
||
2. Select **Cookies and Site Permissions** in the left pane.
|
||
3. Under **All Permissions**, **select Notifications**.
|
||
4. Add your Mattermost workspace URL to the **Allow** section.
|
||
|
||
</TabItem>
|
||
<TabItem value="firefox" label="Firefox">
|
||
|
||
Grant notification permissions for Mattermost in your Firefox web browser.
|
||
|
||
1. From the Firefox menu, select **Settings**.
|
||
2. Select **Privacy and Security** in the left pane.
|
||
3. Under **Permissions**, select the **Settings** option for **Notifications**.
|
||
4. Enable notifications for your Mattermost workspace URL in the **Permissions** list.
|
||
|
||
</TabItem>
|
||
<TabItem value="safari" label="Safari">
|
||
|
||
Grant notification permissions for Mattermost in your Safari web browser.
|
||
|
||
1. From the Safari menu, select **Preferences**.
|
||
2. Select **Websites** and select **Notifications** in the left pane.
|
||
3. Enable notifications for your Mattermost site.
|
||
|
||
</TabItem>
|
||
</Tabs>
|
||
|
||
</TabItem>
|
||
<TabItem value="mobile" label="Mobile">
|
||
|
||
Ensure that your mobile device isn't blocking device settings. Visit the **Android** or **iOS** tab below based on your mobile device type.
|
||
|
||
<Note>
|
||
|
||
From Mattermost mobile v2.34, if your device has notifications disabled, a banner displays in the Mattermost mobile **Settings \> Notifications** screen with a quick link to help you restore device-level notifications.
|
||
|
||
</Note>
|
||
|
||
<Tabs>
|
||
<TabItem value="android" label="Android">
|
||
|
||
Ensure that your Android device isn't blocking Mattermost notifications by granting notification permission for Mattermost in device settings.
|
||
|
||
1. Open the Android **Settings app**, and tap **Application Manager**.
|
||
2. Locate **Google Play Services** and enable notifications for it.
|
||
3. Locate **Mattermost** and enable notifications for it.
|
||
|
||
Also ensure that your Android device isn't set to **Do Not Disturb** mode which is designed to block notifications. See the [Android help](https://support.google.com/android/answer/9069335#zippy=%2Cturn-interruptions-back-on) documentation to learn more.
|
||
|
||
</TabItem>
|
||
<TabItem value="ios" label="iOS">
|
||
|
||
Ensure that your iOS device isn't blocking Mattermost notifications by granting notification permission for Mattermost in device settings.
|
||
|
||
1. Open the iOS **Settings app** and tap **Notifications**.
|
||
2. In the list of apps, tap **Mattermost**.
|
||
3. Enable the **Allow notifications** toggle and set **Notification Delivery** to **Immediate Delivery**.
|
||
|
||
Also ensure that your iOS device isn't set to **Do Not Disturb** mode or a **Focus mode** designed to block notifications. See the [iOS support](https://support.apple.com/en-ca/105112) documentation to learn more.
|
||
|
||
</TabItem>
|
||
</Tabs>
|
||
|
||
</TabItem>
|
||
</Tabs>
|
||
|
||
|
||
We recommend checking your operating system settings next.
|
||
|
||
## Check your Operating System settings
|
||
|
||
The operating system you're running Mattermost on can also block Mattermost notifications. Select the **Linux**, **macOS**, or **Windows** tab based on your operating system:
|
||
|
||
<Tabs>
|
||
<TabItem value="windows" label="Windows">
|
||
|
||
If you're using Mattermost on a Windows machine, you must enable notifications from Mattermost and turn off both Do Not Disturb mode and Focus Assist. If you don't, Windows can block you from receiving Mattermost notifications.
|
||
|
||
1. Open **Windows Settings** and go to **System \> Notifications & actions**.
|
||
2. Ensure that **Get notifications from apps and other senders**, is enabled.
|
||
3. Find Mattermost in the list and enable notifications.
|
||
|
||
Also ensure that Windows’ **Do Not Disturb** mode and **Focus Assist** is turned off. See the Windows support docmentation on [Do Not Disturb mode](https://support.microsoft.com/en-us/windows/turn-off-notifications-in-windows-during-certain-times-81ed1b25-809b-741d-549c-7696474d15d3) and [Focus Assist](https://support.microsoft.com/en-us/windows/make-it-easier-to-focus-on-tasks-0d259fd9-e9d0-702c-c027-007f0e78eaf2) to learn more.
|
||
|
||
</TabItem>
|
||
<TabItem value="linux" label="Linux">
|
||
|
||
If you're using Mattermost on a Linux machine, you must enable pop-up notifications from Mattermost and turn off Do Not Disturb mode. If you don't, Linux can block you from receiving Mattermost notifications.
|
||
|
||
1. Open **Settings**, then go to **Notifications**.
|
||
2. Enable the **Show Pop-up Notifications** option.
|
||
3. Enable the **Show Notification Center** to review and manage your Mattermost notifications.
|
||
|
||
Also ensure that **Do Not Disturb** mode is turned off.
|
||
|
||
</TabItem>
|
||
<TabItem value="macos" label="macOS">
|
||
|
||
If you're using Mattermost on a macOS machine, you must enable application notifications for Mattermost and turn off focus mode. If you don't, macOS can block you from receiving Mattermost notifications.
|
||
|
||
1. Open **System Settings** and go to **Notifications**.
|
||
2. Under **Application Notifications**, ensure notifications are enabled.
|
||
|
||
Also ensure that macOS’ **Focus mode** is turned off. See the Apple Support [Focus mode](https://support.apple.com/en-ca/guide/mac-help/mchl999b7c1a/mac) documentation to learn more.
|
||
|
||
</TabItem>
|
||
</Tabs>
|
||
|
||
|
||
## Frequently Asked Questions
|
||
|
||
### What determines if a desktop notification should be triggered?
|
||
|
||
Desktop notifications are triggered under to following conditions. Click to expand the flow chart.
|
||
|
||
<img src="../../images/desktop_notification_chart.png" width="239" height="232" alt="A flow diagram shows how Mattermost Desktop App notifications are triggered when a message is posted." />
|
||
|
||
### What determines if an email notification should be triggered?
|
||
|
||
Email notifications are triggered under to following conditions. Click to expand the flow chart.
|
||
|
||
<img src="../../images/email_notification_chart.png" width="239" height="232" alt="A flow diagram shows how Mattermost email notifications are triggered when a message is posted." />
|
||
|
||
### What determines if a mobile push notification should be triggered?
|
||
|
||
Mobile push notifications are triggered under to following conditions. Click to expand the flow chart.
|
||
|
||
<img src="../../images/push_notification_chart.png" width="239" height="232" alt="A flow diagram shows how Mattermost mobile push notifications are triggered when a message is posted." />
|
||
|
||
### Are mobile push notifications free?
|
||
|
||
Yes, push notifications are free if you compile your own [push-proxy service](https://github.com/mattermost/mattermost-push-proxy). Push notifications are also free if you use the hosted Test Push Notification Service (TPNS) provided by Mattermost, Inc.
|
||
|
||
TPNS, hosted at [https://push-test.mattermost.com](https://push-test.mattermost.com), offers transport-level encryption, but not production-level service level agreements (SLAs).
|
||
|
||
If you need production-level SLAs for push notifications, you can either compile your own push-proxy service, with your own key, or you can use a paid option and become a Mattermost Professional subscriber [agreeing to our Conditions of Use](https://mattermost.com/terms-of-use/), which enables you to use a production-level Hosted Push Notification Service (HPNS) at `https://push.mattermost.com`.
|
||
|
||
Learn more about [our push notification service](/administration-guide/configure/environment-configuration-settings#enable-push-notifications).
|
||
|
||
[Book a live demo](https://mattermost.com/request-demo/) or [talk to a Mattermost expert](https://mattermost.com/contact-sales/) to explore tailored solutions for your organization's secure collaboration needs. Or try Mattermost yourself with a [1-hour preview](https://mattermost.com/sign-up/) for instant access to a live sandbox environment.
|