When you have a multi user direct message and you add new members (as a conversation grows to need more people) you end up creating a new DM with no history. Instead mattermost should provide an option to keep the history available.

Hello, I have the golang bot implemented into a mattermost channel.
It would be helpful to have an option for users to ask the bot questions in a Direct message as opposed to just a public channel.
I feel that this would encourage users to use the bot more and help shy users as well. That way there can be some sort of privacy between users.
Also, a way to have a log for Admins to keep track of what questions are being asked will be helpful in developing the bot further.

We use MM EE integrate with GitLab EE, so "bots" from GitLab post issues / comments / merge requests to our channels. Today I discovered that MM Search feature does not search (or index?) messages send by such bots as it does not consider them as char participants (from: autocomplete does not offer bots' names, only humans). Is there a setting affecting this or it's by design? Thank you.

Channel-specific option to enable/disable notifications from channel-wide mentions "@channel", "@all", and "@here". Currently they can only be globally toggled in "Account Settings" > "Notifcations" > "Words that trigger metnions" > "Channel-wide mentions @channel, @all, @here".

I want notifications for some channels where I'm the main support person and need to respond to all messages, but do not want notifications on other channels that I never need to reference unless I have a question I'll be asking others.

Regex sound Alerts

Ability to create unique sound alerts based on text of message coming in.

The global channel settings aren't flexible enough create teams with differing levels of channel security. Please consider adding the public & private channel settings at the team level.

Simplistic example:

Team A: invite only with the creation of public rooms disabled
Team B: public team, with the creation of public rooms enabled
Team C: public room with the creation of public rooms disabled

In addition to specifying custom data retention policy globally across all teams and channels (see https://mattermost.uservoice.com/forums/306457-general/suggestions/10007076-ee-data-retention-and-prune-reset-clear-channel-c), allow

1) team and system admins set custom policies for individual teams
2) channel, team and system admins set custom policies for individual channels

Sometimes it would be handy to export a list of channel members for example to form an emailing list or something. Can't find a way to do this either on UI or with commandline tools. Ideally it would be configurable to get Name or Email or both.

Support importing of private channels and private messages as these are part of the slack compliance exports.

Sorry if this is already a feature (I'm a Mattermost noob) but I haven't found a way of doing this yet...

If we are going to implement this, we WILL need a way to search all content (Public/Private channels, Direct messages and Archived) for legal queries!

This is a basic requirement of all software we implement within Government!

Note: I am currently using the Team edition as a trial, so maybe it is a feature in the Enterprise version??

Sample use case: Block .exe files from being uploaded to prevent malicious executables from being downloaded.

In addition to .exe, also interested in blocking PDF files and compressed files.

It was nice in Slack to say for the batch of invitees that have been recently invited that they be thrown into channels x, y, z instead of having to manually Add Member to varying channels or ask them to seek out channels and add themselves.

For instances that only use one team, the option to leave the team is not useful.

Please add an option to the system console to hide the button or add a user permission for this function.
The user permission would be the preferred way to handle this to be prepared for growing instances.

We would like the users to focus on channels. Although we do not want to disallow direct messaging at all.

It would be amazing if we could set a direct message limit per day.

For example: User X is allowed to send 20 direct messages per day, while User Y can send unlimited direct messages.

With this feature we don't limit the users too much, but we also make sure that important information is held in the channels.

Considering the benefits of data analytics for such kind of apps, don't you think support for a nosql database would help. Also, if you want to scale it to a million users; will a rdbms solution support that?

Improve search/filter during direct message.
With more than 100 users, it is really tough to find the user for DM through scrolling. Sometimes the user only know the first name and not last name... or worse, can only guess the spelling

Would be great if we could use

"mochi"

to find

"masashi-mochizuki"