Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Sign up
Appearance settings

Updated Multi-Team Functionality Clarification #9027

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
CooperWang0912 wants to merge 2 commits into mattermost:master
base: master
Choose a base branch
Loading
from CooperWang0912:CooperWang0912-patch-1
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions source/end-user-guide/collaborate/organize-using-teams.rst
View file Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,14 +22,14 @@ Single team versus multiple teams
Mattermost can be deployed both to a single team and to multiple teams. Currently, we recommend deploying to a single team for the following reasons:

- Single team deployments promote communication across the organization. When you add multiple teams, groups can become isolated.
- We don't yet support search or channels across teams, which can impact the cross-team user experience. This includes general searches, saved posts, and recent mentions.
- Integrations (e.g., webhooks and slash commands) are only persistent across single team deployments.
Comment thread
CooperWang0912 marked this conversation as resolved.

However, some Mattermost customers prefer multiple team deployments for the following reasons:

- Teams are useful when there is a purpose for each of them. For example, one team is used for staff members and another team for external users.
- Performance is better when users are scattered across multiple teams instead of all in the same one. With multiple teams, there is less content to load per team or channel switch and database queries are faster.
- Creating a shared team for all users, and using advanced permissions to control who can create channels and add members to the shared team, improves cross-team collaboration when using multiple teams. Additionally, an annoucement banner can be used to provide system-wide announcements.
- The platform now supports multiple team functionalities including general search, saved posts, and recent mentions across teams.
Comment thread
CooperWang0912 marked this conversation as resolved.

Team sidebar
------------
Expand Down Expand Up @@ -118,4 +118,4 @@ When a team is archived, the team will no longer be visible or accessible in the

.. note::

Archiving a team doesn't remove the team data from the Mattermost database. Teams may still be accessible by using the Mattermost API.
Archiving a team doesn't remove the team data from the Mattermost database. Teams may still be accessible by using the Mattermost API.
Comment on lines 119 to +121
Comment on lines 119 to +121

AltStyle によって変換されたページ (->オリジナル) /