For IT policy compliance, offer the ability to invite non-team members users to Mattermost as "single-channel guests" to have access to read and write to one channel and direct message any other users in that channel.

Potential scenarios include opening discussions with non-team members, including customers, vendors, partners and interview candidates.

Add support for a generic OAuth2 provider for Mattermost Enterprise Edition, in addition to other single-sign-on features for enterprises.

For compliance, add the ability to delete specific messaging entries from the user interface, including:

- Clear a specific channel of all its content
- Delete all posts from a specific user
- Delete all posts from a specific user in a specific channel
- Delete all posts from/before/after a specific date
- Configure a data retention time

For organizations with advanced compliance requirements, this feature should enable a System Administrator to omit the inclusion of message contents in email notifications.

Team Communication would benefit a lot of a screen sharing functionality. It should contain a "request remote control" functionality to hold team meetings, feature explanations etc directly in Mattermost.

Atlassian Crowd is the SSO and central user-manager for all Atlassian Products. Its provides an REST and SOAP API.

Following features would be nice:
- Synchronize users with crowd
- Use crowd Cookie to authenticate user

Also see:
- Atlassican Crowd Features: https://www.atlassian.com/software/crowd/overview/key-features
- Atlassican Crowd Pricing: https://www.atlassian.com/software/crowd/pricing

I got asked by a colleague if it is possible to sort the Users because he had about 60+ Users in the Direct Messages section.

It would be nice if you can sort it by a specified department (or Position) or that you can create User groups (with specific permissions for example) and that they get sorted in categories like this.

An other way could be that everyone can create custom folders with users in it and can expand it if needed.

In corporate environments it is sometimes necessary on legal grounds to check an employees communication. Usually the management asks the IT therefor to deliver ones communication. Currently an administrator is neither able to view the existing private chats from any user nor is there an export function to extract all users content from the database

Preview of links from websites.
Post an URL to an website or articel and get meta information from the source.
Teasing of the information (show meta description) and perhaps existing pictures of this page.

Same to the slack behavior.

Currently only System Admins can see individual team statistics information but it would be helpful to allow team admins to see their own team's statistics.

When people create new channels within a team, it would be great to have a popup that shows team members within the channel a screen something like "New Channels created since your last visit, refresh, etc..."

What we are finding is people are creating new channels within Teams, yet no one knows about them unless they click on the More link within the team.

We use LDAP auth and users are able to login without being member of any team. We are now running a cronjob ensuring every user is part of our company wide team.

We would like the possibility to have mattermost assign newly logged in users to a default team.

Support for 2 Factor Authentication using yubikey (https://www.yubico.com/products/yubikey-hardware/) in addition to the software MFA available in Enterprise Edition: https://docs.mattermost.com/deployment/auth.html

I want to see if the opponent reads the message what i sent in DirectMessage.
If opponent read the direct message what i sent, the read sign is shown to me.
If opponent reads the message what i sent, then i want to see read mark on DirectMessage.

It would be great to be able to purge users who have not logged into the site in a definable window.

A companies security policy often has rules stating that a password may not be reused. To facilitate this many applications have a feature that allows the administrator to state how many passwords the application should remember until a password can be reused. Think, for example, a maximum of 10 password that the application must remember.