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]>
164 lines
7.7 KiB
Plaintext
164 lines
7.7 KiB
Plaintext
---
|
||
title: "Connect to multiple Mattermost workspaces"
|
||
---
|
||
import Tabs from '@theme/Tabs';
|
||
import TabItem from '@theme/TabItem';
|
||
|
||
<PlanAvailability slug="all-commercial" />
|
||
|
||
Using the Mattermost desktop or mobile app, you can connect to multiple Mattermost servers from a single interface, and manage system permissions.
|
||
|
||
## Add a server
|
||
|
||
<Tabs>
|
||
<TabItem value="web-desktop" label="Web/Desktop">
|
||
|
||
The **Server** list is located in the top left corner of the window and displays all servers available. Drag to reorder the servers in the list. You can also navigate the server options using [keyboard shortcuts](/end-user-guide/collaborate/keyboard-shortcuts).
|
||
|
||
<Note>
|
||
|
||
If you're using the desktop app prior to release v5.0, individual servers display as separate tabs at the top of the window instead of the top left corner of the window as a list, and servers are managed by going to **… \> File \> Settings** on Windows and **Mattermost \> Preferences** on Mac.
|
||
|
||
</Note>
|
||
|
||
1. Select **Add a server**.
|
||
|
||
> 
|
||
|
||
2. Enter the server URL. Server URLs must begin with either `http://` or `https://`.
|
||
|
||
> <div class="tip">
|
||
>
|
||
> <div class="title">
|
||
>
|
||
> Tip
|
||
>
|
||
> </div>
|
||
>
|
||
> Can't find your Mattermost server URL? Ask your company’s IT department or your Mattermost system admin for your organization’s **Mattermost Site URL**. It’ll look something like `https://example.com/company/mattermost`, `mattermost.yourcompanydomain.com`, or `chat.yourcompanydomain.com`. These URLs could also end in `.net`.
|
||
>
|
||
> </div>
|
||
|
||
3. Enter the server's Display Name.
|
||
4. \[Desktop only\] If your server requires an authentication secret, you'll be prompted to enter it when you connect. Enter the secret provided by your administrator and select **OK**.
|
||
5. Select **Add**.
|
||
|
||
</TabItem>
|
||
<TabItem value="mobile" label="Mobile">
|
||
|
||
Tap the **Servers** <img src="/img/ui/server-variant_E81F.svg" alt="Access server connection options using the Servers icon." className="theme-icon" /> icon located in the top left corner of the window to access all available servers and to add new servers.
|
||
|
||
1. Tap **Add a server**.
|
||
2. Enter the server URL. Server URLs must begin with either `http://` or `https://`.
|
||
|
||
<Tip>
|
||
|
||
Can't find your Mattermost server URL? Ask your company’s IT department or your Mattermost system admin for your organization’s **Mattermost Site URL**. It’ll look something like `https://example.com/company/mattermost`, `mattermost.yourcompanydomain.com`, or `chat.yourcompanydomain.com`. These URLs could also end in `.net`.
|
||
|
||
</Tip>
|
||
|
||
3. Enter the server's Display Name.
|
||
4. Optionally toggle the **Advanced Options** section to enter an **Authentication secret**. This is an additional security measure that some organizations use. Your system admin can provide you with the secret if required.
|
||
|
||
> <img src="../../images/mobile-server-add-psk.jpg" width="300" alt="Mobile app server setup screen showing the optional authentication secret field." />
|
||
|
||
5. Tap **Done**.
|
||
|
||
</TabItem>
|
||
</Tabs>
|
||
|
||
|
||
## Edit a server
|
||
|
||
<Tabs>
|
||
<TabItem value="web-desktop" label="Web/Desktop">
|
||
|
||
1. Hover over a server and select the **Edit** icon.
|
||
|
||
> 
|
||
|
||
2. Modify the server's display name or URL, then select **Save**.
|
||
|
||
> \[Desktop only\] To update an authentication secret, connect to the server. If the secret has changed, you'll be prompted to enter the new one provided by your system admin.
|
||
|
||
</TabItem>
|
||
<TabItem value="mobile" label="Mobile">
|
||
|
||
1. Swipe left on an existing server entry to reveal additional options. Tap **Edit**.
|
||
|
||
> <img src="../../images/swipe-left-to-remove.gif" width="300" alt="In the Mattermost mobile app, swipe left on an existing server connection entry to edit the connection." />
|
||
|
||
2. Modify the server's display name or authentication secret, and then tap **Save**.
|
||
|
||
> <img src="../../images/mobile-edit-server.jpg" width="300" alt="Mobile app edit server screen showing display name fields." />
|
||
>
|
||
> To view or update the authentication secret, expand the **Advanced Options** section. If a secret is currently configured, it will be pre-filled in the field.
|
||
|
||
</TabItem>
|
||
</Tabs>
|
||
|
||
|
||
## Remove a server
|
||
|
||
Removing a server from your desktop app doesn't delete its data. You can add the server back any time.
|
||
|
||
<Tabs>
|
||
<TabItem value="web-desktop" label="Web/Desktop">
|
||
|
||
1. Hover over a server and select **Remove**.
|
||
|
||
> 
|
||
|
||
2. Select **Remove** when prompted to confirm.
|
||
|
||
</TabItem>
|
||
<TabItem value="mobile" label="Mobile">
|
||
|
||
Tap the **Servers** <img src="/img/ui/server-variant_E81F.svg" alt="Access server connection options using the Servers icon." className="theme-icon" /> icon located in the top left corner of the window to access all available servers and to add new servers.
|
||
|
||
Swipe left on an existing server entry to reveal additional options. Tap **Remove**.
|
||
|
||
<img src="../../images/swipe-left-to-remove.gif" width="400" alt="In the Mattermost mobile app, swipe left on an existing server connection entry to delete the connection." />
|
||
|
||
</TabItem>
|
||
</Tabs>
|
||
|
||
|
||
## Switch between workspaces
|
||
|
||
Select a workspace from the **Servers** list in the top left of the desktop app. See [keyboard shortcuts](/end-user-guide/collaborate/keyboard-shortcuts) for more navigation options.
|
||
|
||
## Manage system permissions
|
||
|
||
From Mattermost desktop v5.9, you can manage system permissions when creating or managing existing Mattermost server connections, including: microphone access, camera access, notifications, and location.
|
||
|
||
Granting a system permission sets it to **Accept**, and revoking it sets it to **Always Deny**.
|
||
|
||
|
||
|
||
<Note>
|
||
|
||
- You can't manage system permissions when using the Mattermost mobile app.
|
||
- You'll be prompted to accept or deny notifications after adding a new server connection, and any time you open the desktop app if you haven't explicitly accepted or denied system permissions.
|
||
- You may also need to enable notifications for Mattermost within your operating system preferences.
|
||
|
||
</Note>
|
||
|
||
## Open multiple workspace contexts
|
||
|
||
From desktop v6.0, you can keep multiple workspaces open at the same time and work across them without constant switching to improve situational awareness and operational efficiency. This capability is especially useful for organizations that operate in distributed or multi-domain environments, as it enhances cross-system interoperability and command-level situational awareness.
|
||
|
||
Select the **New tab** <img src="/img/ui/plus_F0415.svg" alt="The Plus icon provides access to channel and direct message functionality." className="theme-icon" /> icon at the top of the desktop app to open a new tab for the current workspace. You can drag and drop to reorder the tabs in the main desktop window.
|
||
|
||
Open internal Mattermost links in a new tab or window by right-clicking on the link and selecting **Open in new tab** or **Open in new window**.
|
||
|
||
- Convert tabs to new windows by right-clicking the tab label and selecting **Move to new window**.
|
||
- Convert pop-out windows back to tabs in the main window by right-clicking on the window title and selecting **Move to main window**.
|
||
- Close pop-out windows by right-clicking on the window title and selecting **Close window**.
|
||
|
||
<Tip>
|
||
|
||
You can manage windows and tabs from the Desktop app's **File** menu, and review all open tabs from the **Windows** menu.
|
||
|
||
</Tip>
|