Skip to content
Open
Changes from 1 commit
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
3 changes: 1 addition & 2 deletions source/end-user-guide/collaborate/organize-using-teams.rst
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,6 @@ 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:
Expand Down Expand Up @@ -118,4 +117,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