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]>
130 lines
7.6 KiB
Plaintext
130 lines
7.6 KiB
Plaintext
---
|
|
title: "Connect Microsoft Calendar to Mattermost"
|
|
---
|
|
<PlanAvailability slug="all-commercial" />
|
|
|
|
Connect your Microsoft M365 Calendar to your Mattermost instance to receive daily summaries of calendar events, synchronize your M365 status in Mattermost, and accept or decline calendar invites from Mattermost.
|
|
|
|
## Deploy
|
|
|
|
Setup starts in Microsoft Azure and ends in Mattermost.
|
|
|
|
### Create a Mattermost App in Azure
|
|
|
|
1. Sign in to [portal.azure.com](https://portal.azure.com) using an admin Azure account.
|
|
2. Navigate to [App Registrations](https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RegisteredApps)
|
|
3. Select **New registration** at the top of the page.
|
|
|
|
> 
|
|
|
|
4. Fill out the form with the following values. Select **Register** to submit the form.
|
|
|
|
> - **Name**: Mattermost MS Calendar Plugin
|
|
> - **Supported account types**: Default value (Single tenant)
|
|
> - **Redirect URI**: `https://<MM_SITE_URL>/plugins/com.mattermost.mscalendar/oauth2/complete` Replace `<MM_SITE_URL>` with your Mattermost server's Site URL. Select **Register** to submit the form.
|
|
>
|
|
> 
|
|
|
|
5. Go to **Certificates & secrets** in the left pane.
|
|
|
|
> 
|
|
|
|
6. Select **New client secret \> Add**, and copy the new secret in the bottom right corner of the screen. We'll use this value later in the Mattermost System Console.
|
|
|
|
> 
|
|
|
|
7. Go to **API permissions** in the left pane.
|
|
|
|
> 
|
|
|
|
8. Select **Add a permission**, then **Microsoft Graph** in the right pane.
|
|
|
|
> 
|
|
|
|
9. Select **Delegated permissions**, and scroll down to select the following permissions. Select **Add permissions** to submit the form:
|
|
|
|
> - `Calendars.ReadWrite`
|
|
> - `Calendars.ReadWrite.Shared`
|
|
> - `MailboxSettings.Read`
|
|
>
|
|
> 
|
|
|
|
10. Add application permissions by going to **Add a permission \> Microsoft Graph \> Application permissions**, and select **Add permissions** to submit the form.
|
|
11. Select the following permissions, and then select **Grant admin consent for mattermost** to grant the permissions for the application.
|
|
|
|
> - `Calendars.Read`
|
|
> - `MailboxSettings.Read`
|
|
> - `User.Read.All`
|
|
>
|
|
> 
|
|
>
|
|
> 
|
|
|
|
You're all set for configuration in the Azure portal.
|
|
|
|
### Install the Microsoft Calendar Integration
|
|
|
|
1. Log in to your Mattermost [workspace](/end-user-guide/end-user-guide-index) as a system admin.
|
|
2. In Mattermost, from the Product menu <img src="/img/ui/products_E82F.svg" alt="Navigate between Channels, collaborative playbooks, and boards using the product menu icon." className="theme-icon" />, select **App Marketplace**.
|
|
3. Search for or scroll to Microsoft Calendar, and select **Install**.
|
|
4. Once installed, select **Configure**. You're taken to the System Console, directly to the **Microsoft Calendar** integration page, under **Plugins**.
|
|
|
|
<Note>
|
|
|
|
From Mattermost v9.11.2 (ESR) and Mattermost Cloud v10, this plugin is pre-packaged with the Mattermost Server. If your Mattermost deployment is on a release prior to v9.11.2, download the [latest plugin binary release](https://github.com/mattermost/mattermost-plugin-mscalendar/releases), and upload it to your server via **System Console \> Plugin Management**.
|
|
|
|
</Note>
|
|
|
|
### Enable and configure the Microsoft Calendar Integration in Mattermost
|
|
|
|
1. In Azure, copy the **Application (client) ID** and **Directory (tenant) ID** from the Azure portal.
|
|
|
|
> 
|
|
|
|
2. In Mattermost, go to **System Console \> Plugins \> Microsoft Calendar** to enable this integration.
|
|
3. Copy the **Application (client) ID** and **Directory (tenant) ID** from the Azure portal.
|
|
4. In Mattermost, enter the following values in the fields provided. Select **Save** to apply the configuration:
|
|
|
|
> - **Admin User IDs** - A comma-separated list of [user IDs](/administration-guide/configure/user-management-configuration-settings#identify-a-users-id) for authorized users who can manage this integration.
|
|
> - **Copy plugin logs to admins, as bot messages** - Select the log level for logs.
|
|
> - **Display full context for each admin log message** - Show or hide full context for all log entries.
|
|
> - **Azure - Directory (tenant) ID** - Paste the **Directory (tenant) ID** from the Azure portal.
|
|
> - **Azure - Application (client) ID** - Paste the **Application (client) ID** from the Azure portal.
|
|
> - **Microsoft Office Client Secret** - Copy from the Azure portal (generated in **Certificates & secrets** earlier in these instructions).
|
|
|
|
Notify your teams that they can [connect their Microsoft Office accounts to Mattermost](#connect-a-microsoft-calendar-account-to-mattermost).
|
|
|
|
## Use
|
|
|
|
Users who want to use Microsoft Calendar interconnectivity must connect a Microsoft Office account to Mattermost.
|
|
|
|
|
|
|
|
Once connected, you'll receive direct messages from the Microsoft Calendar bot in Mattermost for Microsoft Calendar activity.
|
|
|
|
|
|
|
|
See your upcoming events for the current day by typing `/mscalendar today` in the message input box.
|
|
|
|
|
|
|
|
A list of all supported slash commands are available by typing `/mscalendar help` in the message input box.
|
|
|
|
|
|
|
|
You can customize your notification preferences by typing `/mscalendar settings` in the message input box.
|
|
|
|
|
|
|
|
## Upgrade
|
|
|
|
We recommend updating this integration as new versions are released. Generally, updates are seamless and don't interrupt the user experience in Mattermost. Visit the [Releases page](https://github.com/mattermost/mattermost-plugin-mscalendar/releases) for the latest release, available releases, and compatibiilty considerations.
|
|
|
|
## Get help
|
|
|
|
Customers with a Mattermost subscription can open a [Mattermost support case](https://support.mattermost.com/hc/en-us/requests/new). Community deployments can report a bug by opening a GitHub issue against the [Mattermost Microsoft Calendar plugin repository](https://github.com/mattermost/mattermost-plugin-mscalendar).
|
|
|
|
For questions, feedback, and assistance, join our pubic [Integrations and Apps channel](https://community.mattermost.com/core/channels/integrations) on the [Mattermost Community Server](https://community.mattermost.com/) for assistance.
|
|
|
|
Mattermost Team Edition and Free customers can visit the Mattermost [peer-to-peer troubleshooting forum](https://forum.mattermost.com/c/trouble-shoot/16) to access the global Mattermost Community for assistance.
|