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]>
364 lines
21 KiB
Plaintext
364 lines
21 KiB
Plaintext
---
|
||
title: "Make calls"
|
||
---
|
||
import Tabs from '@theme/Tabs';
|
||
import TabItem from '@theme/TabItem';
|
||
|
||
<PlanAvailability slug="all-commercial" />
|
||
|
||
Using a web browser, the desktop app, or the mobile app, you can [join a call](#join-a-call) or [start a call](#start-a-call), [share your screen](#share-your-screen), raise your hand, [react using emojis](#react-using-emojis) during a call, [chat in a thread](#chat-in-a-call), and continue working in Mattermost during a call.
|
||
|
||
<Note>
|
||
|
||
- All Mattermost customers can start, join, and participate in 1:1 audio calls with optional screen sharing.
|
||
- For group calls up to 50 concurrent users, Mattermost Enterprise, Professional, or Mattermost Cloud is required.
|
||
- Enterprise customers can also [record calls](#record-a-call), enable [live text captions](/end-user-guide/collaborate/make-calls#live-captions-during-calls) during calls, and [transcribe recorded calls](#transcribe-recorded-calls). We recommend that Enterprise self-hosted customers looking for group calls beyond 50 concurrent users consider using the [dedicated RTCD service](/administration-guide/configure/calls-deployment-guide).
|
||
- Mattermost Cloud users can start calling right out of the box. For Mattermost self-hosted deployments, System admins need to enable and configure the plugin [using the System Console](/administration-guide/configure/plugins-configuration-settings#calls).
|
||
|
||
</Note>
|
||
|
||
<PlanAvailability slug="academy-calls" />
|
||
|
||
## Join a call
|
||
|
||
To join a call, select **Join call** in a channel, group message, or direct message. Any active team member in a channel or message can join a call, whether it's a public or private channel, or a group or direct message.
|
||
|
||
<Tip>
|
||
|
||
- You can share a call's link to use in a meeting request or share with other people. The link is unique to each channel, and contains the channel's ID, so it doesn't change between calls. Use the `/call link` slash command to generate a shareable link. The call link is valid for long as the channel is active. When a channel is archived or deleted, the share link becomes invalid.
|
||
- If someone from outside of the organization wants to join a call, you need to provide them with a guest account, and add them to the channel. Users who are archived or not registered can't join a call.
|
||
|
||
</Tip>
|
||
|
||
From Mattermost v9.4:
|
||
|
||
- You can join the same call using a web browser, the desktop app, and the mobile app. You can mute, unmute, react, share your screen, and configure voice settings independently for each Mattermost client you're using. You'll appear multiple times as a call participant in the call widget when you join one call on multiple clients.
|
||
- You'll see incoming call notifications for direct and group messages when a new call is started. Multiple calls will result in multiple incoming call notifications. If you're already in a call, and you receive a new incoming call notification, Mattermost prompts you to **Join** the incoming call, or dismiss the notification.
|
||
|
||
## Start a call
|
||
|
||
<Tabs>
|
||
<TabItem value="web-desktop" label="Web/Desktop">
|
||
|
||
To start a call, select **Start call** in the channel header. When you start a call, you become the call host by default. See the [host controls](#host-controls) section below for details on host controls available to ensure calls run smoothly.
|
||
|
||
<Tip>
|
||
|
||
- When you start a call in a channel, you're muted by default. In a direct or group message you're unmuted by default.
|
||
- You can move the call widget to a different area of your screen.
|
||
- Alternatively, you can start a call using the `/call start` slash command.
|
||
|
||
</Tip>
|
||
|
||
</TabItem>
|
||
<TabItem value="mobile" label="Mobile">
|
||
|
||
To start a call, go the channel info menu. Then tap **Start Call**.
|
||
|
||
|
||
|
||
After starting the call, audio will come through the device's speaker or a Bluetooth device, if connected. On Android, audio output will automatically switch to a Bluetooth device if one is connected during a call. You can tap the **Speaker** icon to manually select the output device.
|
||
|
||
On iOS, audio will automatically come through a connected device. You can override this behavior by tapping the **Speaker** button. Audio will then come through the speaker. However, you cannot manually select an output device on iOS at this time.
|
||
|
||
</TabItem>
|
||
</Tabs>
|
||
|
||
|
||
## Host controls
|
||
|
||
From Mattermost v9.9, and Mattermost mobile v2.17, call host controls are available and include the ability to [transfer host duties](#transfer-host-duties), [remove call participants](#remove-call-participants), [stop a screen share](#stop-a-screen-share), [mute or unmute participants](#mute-participants), [lower raised hands](#lower-raised-hands), and [end the call for everyone](#end-the-call-for-everyone).
|
||
|
||
Host controls are available to call hosts and admins in both the call widget by selecting the **More** <img src="/img/ui/dots-horizontal_F01D8.svg" alt="Use the More icon to access additional message options." className="theme-icon" /> icon next to a participant's name, and in the expanded the call window as hosts hover over a call participant in the list.
|
||
|
||
### Transfer host duties
|
||
|
||
Transfer host duties to another call participant by accessing the host controls and selecting **Make host**. Once host duties are transferred to someone else, you can't access host controls unless they're transferred back to you. System admins can change the host at any time.
|
||
|
||
### Remove call participants
|
||
|
||
Remove a call participant from an active call by accessing the host controls and selecting **Remove from call**, then confirm by selecting **Yes, remove**. The call participant is notified that they've been removed from the call by the host.
|
||
|
||
### Stop a screen share
|
||
|
||
Stop a call participant's screen share by accessing the host controls and selecting **Stop screen share**.
|
||
|
||
### Mute participants
|
||
|
||
Invite muted participants to unmute their microphone by accessing the host controls and selecting **Ask to unmute**. The call particpant is prompted to decide whether unmute or stay muted.
|
||
|
||
You can mute the microphone of specific particpants by accessing the host controls and toggling the particpant's mute icon. Mute all call particpants by selecting **Mute all**.
|
||
|
||
### Lower raised hands
|
||
|
||
Lower a raised hand by accessing the host controls and selecting **Lower hand**. The participant is notified that their hand was lowered by the host.
|
||
|
||
### End the call for everyone
|
||
|
||
From Mattermost v10.2 and mobile v2.19, call hosts who choose to leave a call are prompted to confirm whether they want to leave or end the call for all participants.
|
||
|
||
## Share your screen
|
||
|
||
During a call, call participants can share their screen with other call participants, unless your system admin has [disabled your ability to do so](/administration-guide/configure/plugins-configuration-settings#allow-screen-sharing).
|
||
|
||
<Note>
|
||
|
||
Screensharing is available in the Mattermost desktop app or a web browser. The ability to screenshare using the mobile app isn't supported.
|
||
|
||
</Note>
|
||
|
||
To share your screen:
|
||
|
||
1. In the call widget, select **Start presenting**.
|
||
2. Select the screen you want to share.
|
||
3. To stop sharing, select the **Stop presenting** icon or the **Stop sharing** option.
|
||
|
||
### Share audio during screen sharing
|
||
|
||
From Mattermost Calls plugin v1.9.0, you can share audio along with your screen during screen sharing. To enable this feature, you must first turn on the **Share sound with screen** preference in your Calls settings by going to **Settings \> Plugin Preferences \> Calls**. This setting is stored locally on each client and is not synchronized across devices.
|
||
|
||
<Note>
|
||
|
||
Audio sharing support varies by platform and browser:
|
||
|
||
**Web browsers:**
|
||
|
||
- **Chrome-based browsers only** (Google Chrome, Chromium, Microsoft Edge): When sharing a browser tab, you'll have the option to include audio from that tab. On Windows only, you can also share system sounds when sharing the entire screen.
|
||
- **Other browsers**: Audio sharing is not supported.
|
||
|
||
**Desktop app:**
|
||
|
||
- **Windows and Linux**: System audio is shared when sharing the entire screen.
|
||
- **macOS**: Audio sharing is not supported due to system limitations.
|
||
|
||
</Note>
|
||
|
||
## React using emojis
|
||
|
||
All call participants can use emojis to react during a call.
|
||
|
||
<Tabs>
|
||
<TabItem value="web-desktop" label="Web/Desktop">
|
||
|
||
Expand the call window using the arrows in the top-right of the call widget. From there, select the emoji icon to access frequently-used emojis or select additional emojis from the emoji picker.
|
||
|
||
</TabItem>
|
||
<TabItem value="mobile" label="Mobile">
|
||
|
||
Expand the call window using the arrows in the top-right of the active call banner. From there, select **React**.
|
||
|
||
|
||
|
||
</TabItem>
|
||
</Tabs>
|
||
|
||
|
||
## Chat in a call
|
||
|
||
A chat thread is created automatically for every new call.
|
||
|
||
<Tabs>
|
||
<TabItem value="web-desktop" label="Web/Desktop">
|
||
|
||
Open the chat thread in the widget by selecting the **Gear** <img src="/img/ui/settings-outline_F08BB.svg" alt="Use the Settings icon to customize your Mattermost user experience." className="theme-icon" /> icon, then select **Show chat thread**. Alternatively, expand the call window using the arrows in the top-right of the call widget. From there, select the chat icon to access the chat thread.
|
||
|
||
</TabItem>
|
||
<TabItem value="mobile" label="Mobile">
|
||
|
||
Expand the call window using the arrows in the top-right of the active call banner. Then select **More \> Call Thread**.
|
||
|
||
|
||
|
||
</TabItem>
|
||
</Tabs>
|
||
|
||
|
||
## Record a call
|
||
|
||
<PlanAvailability slug="ent-plus" />
|
||
|
||
From Mattermost v7.7, if you're the host of a meeting, you can record the call, unless your system admin has [disabled the host's ability to do so](/administration-guide/configure/plugins-configuration-settings#enable-call-recordings).
|
||
|
||
Call recordings include audio, any screen sharing during the call, and text transcriptions, when [enabled](/administration-guide/configure/plugins-configuration-settings#enable-call-transcriptions).
|
||
|
||
The default setting for a recording is 60 minutes, but your system admin may [change the recording duration](/administration-guide/configure/plugins-configuration-settings#maximum-call-recording-duration) as needed. You'll receive a reminder 10 minutes before the recording limit is reached. If your call is going to continue beyond the recording limit, allow the first recording to complete, then start a new recording immediately after.
|
||
|
||
When you stop recording, the recording file is posted in the call thread as an MP4 file attachment. It's available to all users in the channel both during the call, and after the call has ended.
|
||
|
||
To record a call:
|
||
|
||
<Tabs>
|
||
<TabItem value="web-desktop" label="Web/Desktop">
|
||
|
||
1. Select **Start call** in the header of the channel, group message, or direct message.
|
||
2. Select the pop-out icon.
|
||
3. In the call widget, select the **Record** button.
|
||
4. To stop recording, select the **Record** button again.
|
||
|
||
</TabItem>
|
||
<TabItem value="mobile" label="Mobile">
|
||
|
||
To start recording, use the `/call recording start` slash command. When you're finished recording, use the `/call recording stop` slash command.
|
||
|
||
|
||
|
||
|
||
|
||
Alternatively, expand the call window using the arrows in the top-right of the active call banner. Then select the **Record** button. To finish, tap on **Stop Recording** button.
|
||
|
||
|
||
|
||
|
||
|
||
</TabItem>
|
||
</Tabs>
|
||
|
||
|
||
## Live captions during calls
|
||
|
||
<PlanAvailability slug="ent-plus" />
|
||
|
||
From Mattermost v9.7, and Mattermost mobile app v.2.16, all call participants can display real-time text captions by selecting the **More** <img src="/img/ui/dots-horizontal_F01D8.svg" alt="Use the More icon to access additional message options." className="theme-icon" /> icon and **Show live captions** when the call is being recorded, and when [live captions are enabled](/administration-guide/configure/plugins-configuration-settings#enable-live-captions). Live captions can be helpful in cases where noise is preventing you from hearing the audio of participants clearly.
|
||
|
||
By default, live captions display in English. Your Mattermost system admin can [specify a different language for live captions](/administration-guide/configure/plugins-configuration-settings#live-captions-language) in the System Console.
|
||
|
||
<Note>
|
||
|
||
- The ability to enable live captions during Mattermost calls is currently in [Beta](/administration-guide/manage/feature-labels#beta).
|
||
- Your system admin must enable [call recordings](/administration-guide/configure/plugins-configuration-settings#enable-call-recordings) to enable live captions.
|
||
|
||
</Note>
|
||
|
||
## Transcribe recorded calls
|
||
|
||
<PlanAvailability slug="ent-plus" />
|
||
|
||
From Mattermost v9.4, and Mattermost mobile app v.2.13, call recordings can include text captions, and a transcription text file can be generated, unless your system admin has [disabled the ability to transcribe call recordings](/administration-guide/configure/plugins-configuration-settings#enable-call-transcriptions).
|
||
|
||
When call recording stops, the transcription file is posted in the call thread as a TXT file attachment. It's available to all users in the channel both during the call, and after the call has ended. Additionally, users viewing the call recording can show or hide text captions using the Closed Captioning option in the video player.
|
||
|
||
<Note>
|
||
|
||
- The ability to enable recorded call transcriptions is currently in [Beta](/administration-guide/manage/feature-labels#beta).
|
||
- Your system admin must enable [call recordings](/administration-guide/configure/plugins-configuration-settings#enable-call-recordings) to enable recorded call transcriptions.
|
||
|
||
</Note>
|
||
|
||
## Frequently asked questions
|
||
|
||
### Can I set a ring tone for incoming calls?
|
||
|
||
Yes! From Mattermost v8.0 and Calls v0.17.0, desktop app and web users can go to **Settings \> Notifications \> Desktop Notifications** to enable Mattermost to alert you to incoming calls through direct or group messages with a specific ring tone and a desktop notification, unless the system admin has [disabled your ability to do so](/administration-guide/configure/plugins-configuration-settings#enable-call-ringing).
|
||
|
||
### Is video supported?
|
||
|
||
The integration currently supports only voice calling and screen sharing. We're considering video support in the future.
|
||
|
||
### Can I password-protect a call?
|
||
|
||
No. Any member with sufficient permission to access the channel can join the call.
|
||
|
||
### Is there encryption?
|
||
|
||
Media (audio/video) is encrypted using security standards as part of WebRTC. It's mainly a combination of DTLS and SRTP. It's not e2e encrypted in the sense that in the current design all media needs to go through Mattermost which acts as a media router and has complete access to it. Media is then encrypted back to the clients so it's secured during transit. In short: only the participant clients and the Mattermost server have access to unencrypted call data.
|
||
|
||
### Are there any third-party services involved?
|
||
|
||
The only external service used is Mattermost official STUN server (`stun.global.calls.mattermost.com`) which is configured as default. This is primarily used to find the public address of the Mattermost server. The only information sent to this service is the IP addresses of clients connecting as no other traffic goes through it. It can be removed in the System Console if you want to provide an `ICE Host Override` setting instead.
|
||
|
||
## Troubleshooting
|
||
|
||
### My audio doesn't work when I join a call
|
||
|
||
If you can hear the other participants in the call but they can't hear you, select the Gear icon <img src="/img/ui/settings-outline_F08BB.svg" alt="Use the Settings icon to customize your Mattermost user experience." className="theme-icon" /> next to the call end button in the widget. From there, you can check and change your audio output and microphone settings. Select <img src="/img/ui/settings-outline_F08BB.svg" alt="Use the Settings icon to customize your Mattermost user experience." className="theme-icon" /> again to close the menu. Alternatively, you can [manage your audio and microphone preferences](/end-user-guide/preferences/manage-your-plugin-preferences) in **Settings**.
|
||
|
||
### My call is disconnected after a few seconds
|
||
|
||
This is usually a sign that the underlying UDP channel has not been established and the connection times out after ~10 seconds. When the connection has been established correctly an `rtc connected` line should appear in the client-side logs (JS console). There isn't a single solution as it depends on your infrastructure/deployment specifics. However, if you're a system or network admin, you may need to open up the UDP port or configure the network accordingly.
|
||
|
||
### I can't screen share using Mattermost desktop on macOS
|
||
|
||
There's a known bug on macOS with some versions of Chrome (which is used by Mattermost desktop). If you've given screen sharing permissions to Mattermost desktop, and are still unable to screen share, do the following:
|
||
|
||
1. Quit Mattermost.
|
||
2. Open Terminal.
|
||
3. In the terminal, run: `tccutil reset ScreenCapture Mattermost.Desktop`
|
||
4. Restart Mattermost and start a call.
|
||
5. Select **Screen share** and give it permissions again.
|
||
6. Restart Mattermost again.
|
||
|
||
If the issue persists please post on the Mattermost Community Server in the [Developer: Calls](https://community.mattermost.com/core/channels/developers-channel-call) channel to troubleshoot further.
|
||
|
||
## Debugging
|
||
|
||
If you experience issues with calls, collecting information is helpful as you can share it with us for debugging purposes.
|
||
|
||
As with any other issue, but more importantly with calls, it’s very useful to let us know the date and time that the problem occurred, with as much detail as possible so that information can be cross-checked with server logs. Also please include any reproduction steps if applicable. Other important information includes:
|
||
|
||
- Browser/app version
|
||
- Operating system type and version
|
||
|
||
### JS console logs
|
||
|
||
#### Web app
|
||
|
||
<table>
|
||
<colgroup>
|
||
<col style={{width: '13%'}} />
|
||
<col style={{width: '86%'}} />
|
||
</colgroup>
|
||
<thead>
|
||
<tr>
|
||
<th>Browser</th>
|
||
<th>Action</th>
|
||
</tr>
|
||
</thead>
|
||
<tbody>
|
||
<tr>
|
||
<td><strong>Chrome</strong></td>
|
||
<td>CMD+OPTION+J (macOS) CTRL+SHIFT+J (Windows, Linux, ChromeOS)</td>
|
||
</tr>
|
||
<tr>
|
||
<td><strong>Firefox</strong></td>
|
||
<td>CMD+SHIFT+J (macOS)/CTRL+SHIFT+J (Windows, Linux, ChromeOS)</td>
|
||
</tr>
|
||
<tr>
|
||
<td><strong>Safari</strong></td>
|
||
<td>Enable Developer Menu in <strong>Safari > Preferences > Advanced > Show Develop Menu in Menu Bar</strong>. Then <strong>Develop > Show Javascript Console</strong>. Right-click on the console and select <strong>Save to file</strong> to download the logs.</td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
|
||
#### Desktop app
|
||
|
||
In the top menu bar of the app, select **View \> Developer Tools \> Developer Tools for Current Tab**. In the logs that are generated, right-click and select **Save as** to download the logs.
|
||
|
||
#### Mobile app
|
||
|
||
You can access and share debug logs from **Account screen \> Settings \> Report a problem**.
|
||
|
||
### Call stats dump
|
||
|
||
In cases where there are audio/video issues, difficulty in hearing other participants, and/or stuttering video and/or choppy audio, run the `/call stats` slash command in the channel where the call is currently active. This returns a JSON object via an ephemeral message. Additionally, run the `/call logs` command to review the client logs for the last call session.
|
||
|
||
You can run this command in an active call or after leaving the call in question. However, we will only save data for the last joined call so joining again will delete the previous call's feedback.
|
||
|
||
### WebRTC internals (Chrome and Firefox only)
|
||
|
||
This is an additional method for Chrome and Firefox users in cases where there are audio/video issues, difficulty in hearing other participants, and/or stuttering video and/or choppy audio.
|
||
|
||
#### Chrome browser (recommended)
|
||
|
||
Open `chrome://webrtc-internals/` in the browser that you're using for the active call.
|
||
|
||
#### Firefox browser
|
||
|
||
Open `about://webrtc` in the browser that you're using for the active call.
|
||
|
||
### Share information
|
||
|
||
Debug information is helpful to our community as there may be other community members having the same issue as you. We recommend that debug information be shared in either of the two options below:
|
||
|
||
- Post in [Developers: Calls](https://community.mattermost.com/core/channels/developers-channel-call) channel: prefer this method when possible but keep in mind the channel is public.
|
||
- Post in [Team: Calls](https://community.mattermost.com/private-core/channels/calls-team) channel: use this channel if posting sensitive information.
|