mirror of
https://github.com/hanzoai/team.git
synced 2026-11-01 07:55:31 +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]>
97 lines
5.8 KiB
Plaintext
97 lines
5.8 KiB
Plaintext
---
|
|
title: "Manage your mobile notifications"
|
|
---
|
|
import Tabs from '@theme/Tabs';
|
|
import TabItem from '@theme/TabItem';
|
|
|
|
<PlanAvailability slug="all-commercial" />
|
|
|
|
## Enable notifications
|
|
|
|
From Mattermost mobile v2.34, the Mattermost **Settings \> Notifications** screen alerts you when notifications are disabled by your device. Follow the link in the notification to enable device-level notifications.
|
|
|
|
From Mattermost v9.9, Mattermost prompts you to enable notifications in the mobile app the first time you open the app.
|
|
|
|
Once Mattermost notifications are enabled at the device level and in the mobile app, you'll start receiving notifications for all Mattermost activity with [badges](#badge-based-notifications), and [push notifications](#push-notifications). See the section below on [customizing your notifications](#customize-your-notifications) based on how you prefer to be notified about Mattermost activity on your mobile device.
|
|
|
|
<Note>
|
|
|
|
You may also need to enable notifications in iOS or Android for Mattermost by changing your device preferences.
|
|
|
|
</Note>
|
|
|
|
## Badge-based notifications
|
|
|
|
Mattermost mobile app icons display numbered badges for unread [direct](/end-user-guide/collaborate/channel-types#direct-message-channels) and [group](/end-user-guide/collaborate/channel-types#group-message-channels) messages, and [@mentions](/end-user-guide/preferences/manage-your-mentions-keywords-notifications), [keywords](/end-user-guide/preferences/manage-your-mentions-keywords-notifications) you're actively watching.
|
|
|
|
<img src="../../images/numbered-badge.png" width="50" alt="A numbered badge means you have at least 1 unread message, @mention, or one of your keywords has triggered a notification." />
|
|
|
|
<Note>
|
|
|
|
- The Mattermost mobile app doesn't display dot badges indicating other unread activity by design. The activity you're directly involved in is prioritized over other activity.
|
|
- Android users may see Mattermost notifications in the Android Notification Shade while the Mattermost icon shows no badge. This is because the Android notification system may also display badges unread activity.
|
|
|
|
</Note>
|
|
|
|
## Push notifications
|
|
|
|
You'll see mobile push notification messages on your device as follows:
|
|
|
|
- **iOS**: On the Lock Screen, Notification Center, and as Banners/Alerts based on your iOS settings.
|
|
- **Android**: On the Lock Screen, Notification Shade, and as Banners/Heads-Up Notifications based on your Android settings.
|
|
|
|
## Customize your notifications
|
|
|
|
You can manage your mobile notifications in both the desktop app and the mobile app.
|
|
|
|
<Tabs>
|
|
<TabItem value="desktop-app" label="Desktop app">
|
|
|
|
In the desktop app, manage your mobile notification preferences by selecting the **Settings** <img src="/img/ui/settings-outline_F08BB.svg" alt="Use the Settings icon to customize your Mattermost user experience." className="theme-icon" /> icon located in the top right corner of the screen, and select **Notifications \> Desktop and mobile notifications**.
|
|
|
|
By default, you receive mobile notifications for @mentions, direct messages, and group messages when your Mattermost availability is [Online, Away, or Offline](/end-user-guide/preferences/set-your-status-availability#set-your-availability). You won't receive Mattermost notifications on your device if you're actively using Mattermost in a web browser.
|
|
|
|
- Want to receive fewer mobile notifications? Under **Trigger mobile notifications when I am**, select **Away or Offline** or **Offline**.
|
|
- Want different desktop and mobile notifications? Select **Use different settings for my mobile devices**, and then select **All new messages**, or **Mentions, direct messages and group messages**.
|
|
|
|
</TabItem>
|
|
<TabItem value="mobile-app" label="Mobile app">
|
|
|
|
In the mobile app, tap your profile picture, then tap **Settings \> Notifications**.
|
|
|
|
- Tap **Mentions** to disable notifications based on keywords that trigger mentions, including first name, username, channel-wide @mentions, and keywords you've specified.
|
|
- Tap **Push Notifications** to choose what to be notified about.
|
|
|
|
You can also [manage email notifications](/end-user-guide/preferences/manage-your-notifications#email-notifications) and [send automatic replies to direct messages](/end-user-guide/preferences/manage-your-thread-reply-notifications#send-automatic-replies-to-direct-messages) directly from your device.
|
|
|
|
</TabItem>
|
|
</Tabs>
|
|
|
|
|
|
### Incoming Call notifications
|
|
|
|
Want to hear a sound on your mobile device when a Mattermost call starts? If your Mattermost admin [enables this Beta feature](/administration-guide/configure/plugins-configuration-settings#enable-call-ringing), select **Call Notifications** to choose the sound that plays when a call is started within a direct or group message you're participating in.
|
|
|
|
<Tip>
|
|
|
|
- From Mattermost mobile app v2.19, incoming call sounds also include device vibration, as well as vibration-only when your device is in silent mode.
|
|
- If you prefer a separate call sound on mobile, your mobile change applies only to your mobile device.
|
|
|
|
</Tip>
|
|
|
|
### Disable all mobile notifications
|
|
|
|
To disable all Mattermost mobile notifications, tap **Push Notifications \> Nothing**.
|
|
|
|
## Frequently asked questions
|
|
|
|
### Are mobile notification counts the same as other Mattermost clients?
|
|
|
|
No. You're only notified of unread threads with @mentions on your mobile device. You're not notified of general unread activity on mobile.
|
|
|
|
### What does a Mattermost icon with an exclamation point mean?
|
|
|
|
|
|
|
|
A Mattermost icon with an exclamation point means that you're logged out of at least 1 Mattermost server you connect to using the mobile app. Log back in to any servers as needed. See the [Connect to multiple workspaces](/end-user-guide/preferences/connect-multiple-workspaces) documentation for details.
|