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]>
80 lines
7.0 KiB
Plaintext
80 lines
7.0 KiB
Plaintext
---
|
||
title: "Set your status and availability"
|
||
---
|
||
import Tabs from '@theme/Tabs';
|
||
import TabItem from '@theme/TabItem';
|
||
|
||
<PlanAvailability slug="all-commercial" />
|
||
|
||
Let your team know whether you're available by setting a [custom status](/end-user-guide/preferences/set-your-status-availability#set-a-custom-status) and your [availability](/end-user-guide/preferences/set-your-status-availability#set-your-availability) in Mattermost.
|
||
|
||
## Set a custom status
|
||
|
||
Set a custom status to display a descriptive status message and optional emoji next to your name in Mattermost. Other members can see your status anywhere they can see your name, such as the channel sidebar and in conversations. To set a custom status in Mattermost:
|
||
|
||
<Tabs>
|
||
<TabItem value="web-desktop" label="Web/Desktop">
|
||
|
||
1. Select your profile picture, then select **Set a custom status**.
|
||
2. Choose from a list of suggested statuses, or enter a new emoji and status. The Speech bubble emoji 💬 is used by default if you don't specify an emoji. A custom status can be a maximum of 100 characters in length.
|
||
3. Specify when to clear your custom status.
|
||
4. Select **Set Status**.
|
||
|
||
</TabItem>
|
||
<TabItem value="mobile" label="Mobile">
|
||
|
||
1. Select your profile picture, then select **Set a status**.
|
||
2. Choose from a list of suggested statuses, reuse a recent status, or tap to enter a status and select an emoji. The Speech bubble emoji 💬 is used by default if you don't specify an emoji. A custom status can be a maximum of 100 characters in length.
|
||
3. Specify when to clear your custom status.
|
||
4. Tap **Done**.
|
||
|
||
</TabItem>
|
||
</Tabs>
|
||
|
||
|
||
<Tip>
|
||
|
||
- Custom statuses are enabled by default in Mattermost. System admins can disable this feature by going to **System Console \> Site Configuration \> Users and Teams \> Enable Custom Statuses**. Disabling this feature also removes the `Update your status` prompts in Mattermost.
|
||
|
||
</Tip>
|
||
|
||
### Clear a custom status
|
||
|
||
To clear a custom status, select your profile picture, then select **Clear Status**, or select the **Clear** option next to your current status.
|
||
|
||
|
||
|
||
## Set your availability
|
||
|
||
To set your availability, select your profile picture, then specify your availability as **Online**, **Away**, **Do Not Disturb**, or **Offline**.
|
||
|
||
<table>
|
||
<colgroup>
|
||
<col style={{width: '100%'}} />
|
||
</colgroup>
|
||
<tbody>
|
||
<tr>
|
||
<td><blockquote><p><strong>Availability</strong> | <strong>Description</strong> |</p></blockquote><dl><dt>==================+======================================================================================================================================+</dt><dd><dl><dt><a href="mm-subst:online">online</a> | Online: |</dt><dd><div class="line-block"> |<br />- Set automatically for you when you're active on Mattermost using a browser, the desktop app, or the mobile app. |<br />- When using the desktop app, any mouse or keyboard activity keeps your availability set to <strong>Online</strong>. |<br />- By default, notifications are sent to the browser, the desktop app, and the mobile app. |</div></dd></dl></dd></dl></td>
|
||
</tr>
|
||
<tr>
|
||
<td><dl><dt><a href="mm-subst:away">away</a> | Away: |</dt><dd><div class="line-block"> |<br />- Set automatically for you when you've been inactive for more than 5 minutes. System admins can change this |<br /> value using an experimental configuation setting called |<br /> `user status away timeout <mm-ref:administration-guide%2Fconfigure%2Fexperimental-configuration-settings%3Auser%20status%20away%20timeout>`\_\_. |<br /> |<br />- You're inactive in Mattermost when you're not: typing in or navigating between channels, switching to |<br /> another browser tab, or when you've minimized or moved the browser window to the background. |<br /> |<br />- You can manually set yourself as <strong>Away</strong> any time. |<br />- By default, notifications are sent to your Mattermost mobile app. |</div></dd></dl></td>
|
||
</tr>
|
||
<tr>
|
||
<td><dl><dt><a href="mm-subst:dnd">dnd</a> | Do Not Disturb: |</dt><dd><div class="line-block"> |<br />- Set your availability as <strong>Do Not Disturb</strong> any time you don't want notifications for a period of time. |</div></dd></dl></td>
|
||
</tr>
|
||
<tr>
|
||
<td><dl><dt><a href="mm-subst:offline">offline</a> | Offline:</dt><dd><div class="line-block"> |<br />- Set automatically for you when you exit the Mattermost desktop app or close the browser window, sleep or |<br /> lock your computer, or on mobile when you change apps, close the Mattermost mobile app, or lock your |<br /> mobile device screen. |<br />- You can manually set yourself as <strong>Offline</strong> any time. |<br />- By default, notifications are sent to your Mattermost mobile app. |</div></dd></dl></td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
|
||
Other members can see your availability anywhere they can see your name, such as the channel sidebar, within conversations, and within direct messages.
|
||
|
||
### Set your availability as Do Not Disturb
|
||
|
||
Set your availability to **Do Not Disturb** to disable all desktop, email, and push notifications when you are unavailable or need to concentrate.
|
||
|
||
You can specify how long to disable notifications by selecting a preset expiration, by setting a custom expiration, or by setting your status as **Don't clear**. Your availability automatically reverts to its previous setting once the expiration is reached (this may take up to five minutes).
|
||
|
||
|