General
Please search for existing ideas before posting a new idea.
20 results found
-
Support import from Slack of private messages and private channels
Support importing of private channels and private messages as these are part of the slack compliance exports.
34 votesThank you for nominating the feature! It is now available in Mattermost 5.14.
-
Channel-specific option for Notifications from Channel-wide mentions "@channel", "@all", and "@here"
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.
23 votesThis has been completed, more details here: https://docs.mattermost.com/help/settings/channel-settings.html#ignore-mentions-for-channel-here-and-all.
-
More robust CLI utility
My shop is very Linux and command line heavy. We would like to see the [install dir]/bin/platfrom utility expanded to include more features, which can then be scripted. The first such feature we would like to see would be the ability to list users from the utility.
45 votesThis use is resolved with our new mmctl CLI utility tool. You can learn more at https://docs.mattermost.com/administration/mmctl-cli-tool.html
The utility tool is also open sourced for anyone who would like to contribute more features to it: https://github.com/mattermost/mmctl
Thank you everyone who upvoted and participated to this feature proposal!
-
Only admin or manager should be able to create channels
All member by default after invited, can create channel, private groups etc.. how to stop this? Only admin should be able to create channels and private groups..
155 votesThere was some back and forth among designers about the risk of this feature being detrimental to the concept of a “team”.
If a few people on a team need to talk about temporary topics like “New logo project”, or “Spring 2016 offsite planning”, it seems easiest for them to create a private group for the discussion and archive it when they were done (note: Channels aren’t ever deleted, all information is archived, so there’s no data loss issue: https://docs.mattermost.com/help/getting-started/organizing-conversations.html#deleting-a-channel).
An option to restrict this feature could degrade the user experience. People would have to talk about niche topics inside other channels, distracting teammates who aren’t involved, or clutter the public channel list with overly narrow topics.
Despite these problems, there’s a case to be made for large organizations where social policy doesn’t scale, so the option has been added to Enterprise Edition and kept the complexity out of…
-
EE: Data retention and prune/reset/clear channel content options
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
219 votesThis feature ships in BETA with v4.3 on October 16th.
-
Teams displayed as tabs instead of a list
It would be GREAT to display the teams as tabs instead of a list.
The benefit here is if something is mentioned in a channel within that team, you could flash/graphically activate the tab to notify the user that there is activity.
The way it is right now, it's very confusing to have to click down through the list of teams to find active conversations.
1 voteThis feature is complete and shipped with Mattermost v3.6
-
Google Apps sign-in
Ability to use Google Apps SSO with ability to restrict account creation to a list of domains, similar to email-based sign-on.
3 votesSingle-sign-on to Google’s proprietary SaaS service now available in commercial Enterprise Edition: https://docs.mattermost.com/deployment/sso-google.html
-
Add IT policy option to disable or enable join/leaves messages
Provide System Console policy option to enable or disable join/leave messages for very large channels
31 votesOffered in Mattermost 3.5 in E10 and higher
-
Restrict team by email
It is currently possible to restrict account creation to specific email domains via “Settings > Users and Teams > Restrict account creation to specified email domains”; however, once a user has an account, they can be invited to any team, or join any open team.
We would like to be able restrict individual teams to an email domain too. Specifically, we have a group of external contractors who have access to their own team, but we don’t want them to accidentally end up in any of our other teams.
For example, team “Foo” would only allow members from @foo.com, and…
75 votesMattermost 5.4 has added a new setting to restrict teams by email domain
Huge thanks for Gabe (@gvengel) for your contribution, and for everyone nominating this feature.
-
RestrictPublicChannelManageMembers
It would be cool, if you added a policy for RestrictPublicChannelManageMembers as it already exists for RestrictPrivateChannelManageMembers.
The idea is that not everyone should be able to remove other users from public channels.
Even if there is no banning, removed users wont get notified of their removal and it results into trolling to join all public channels and remove all members from all public channels.Especially, if there are quite a few public channels, it really hurts to have to rejoin all the channels, just because some troll kicked everyone off.
3 votesThank you for the suggestion! This is now available in Mattermost v5.0 and later in Enterprise Edition as part of the Advanced Permissions feature set: https://docs.mattermost.com/deployment/advanced-permissions.html
-
EE: Allow administrators to turn off the ability to create channels to normal users
I would like to add the ability for administrators to completely turn off the ability to create channels for regular users at the site and team levels.
This way, an organization can ensure that only an approved set of channels are created and used.
1 voteThis feature is available in Enterprise Edition: https://docs.mattermost.com/administration/config-settings.html#enable-public-channel-creation-for
-
Add possiblility for a default team when using external auth (like LDAP)
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.
19 votesThis use case is now available with AD/LDAP Groups, available in Mattermost Cloud and Mattermost Self-Managed E20.
Learn more at:
- Cloud: https://docs.mattermost.com/cloud/cloud-user-management/cloud-groups.html
- Self-Managed E20: https://docs.mattermost.com/deployment/ldap-group-sync.html -
Add ability for administrators to restrict archiving of channels
Users are prevented from archiving Town Square, but users are able to archive any other channel
54 votesSeveral options were considered for this feature, including:
- Separate permissions for archiving, renaming, modifying and creating channels
- Adding a new role for managing channels
- Offering individual permissions for manipulating channelsApplying the fast, obvious, forgiving design principle we arrived at the least complex solution of the options, which was to combine restrictions for creating, renaming and updating channel information, in addition to restricting archiving.
The goal was to keep things simple, so that users either “can do everything” or “can do nothing” and aren’t confused about their permissions.
This feature has been added as an optional IT policy in Mattermost E10.
This was also considered for Team Edition, but it didn’t seem appropriate for a “virtual office” where everyone knew each other well. It would be like having locks on the conference room doors to keep people from erasing things off the whiteboards.
-
Allow channel headers to be locked down
In channels with 200+ members, people sometimes mess up with the channel headers and this is unwanted when important announcements are being made up there. I think the "topic" should be able to be locked down and write-able only by admins, just like on irc.
Maybe a global option to lock the headers to channel creators? Or allow certain people to change the headers (permissions?).
3 votes -
Search in System Console
The system console is starting to get very large, and it might be a useful feature to get to a setting quickly via search, similar to search in smartphone settings.
1 vote -
link
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.
25 votesThis feature is complete and shipped with v4.4 on November 16th.
-
Provide option to authenticate using a SAML based iDP
Many organizations are using SAML iDP's, like SecureAuth, PingFederate and Okta, to manage authentication of their users. The ability to allow organizations to select this authentication option would make this more appealing.
3 votesThanks Nicholas, SAML authentication is shipping in v3.2 to be released July 16 as part of Enterprise Edition.
-
Horizontal scaling for large enterprise deployments
For use in very large enterprise deployments exceeding the capacity of a single Mattermost server and needing high availability and set up of redundant proxies, databases and application servers.
Should include availability of enterprise support, advisory and hardware-sizing guidance.
5 votesNow available in E20: https://docs.mattermost.com/deployment/cluster.html
-
EE: Message Editing & Deletion configure option
Enable configuration of editing and deleting options in Enterprise Edition
Under "System Console > Policy"
Setting one (with radio buttons):
Allow users to edit their messages:
[ x ] Any time
[ ] Never
[ ] ___ minutes after posting //Where ___ is a text input box where they can enter a number of minutesHelp Text: After posting a message, set the length of time the author has to edit it.
- Setting two (with radio buttons):
Allow which users to delete messages:
[ x ] Only Team Administrators and System Administrators
[ ] Message authors can delete their own…50 votesNow available in Mattermost 3.7 as after of policy features in E10 and higher.
-
Integration with LDAP / Active Directory
Posting from Kaushik Chakraborty's original request in old feature request forum:
For Mattermost to matter inside enterprises, users should have ability to use their existing AD credentials for login. The profile management could happen like it is within MM.
Creating sign-ups for large groups within an enterprise is a massive operational hassle and it would miss all the facilities / advantages of single-sign on.Also, additional requests for LDAP from GitHub discussion: https://github.com/mattermost/platform/issues/78
128 votesSupport for Microsoft Active Directory and LDAP now available in [Mattermost Enterprise Edition](http://docs.mattermost.com/deployment/sso-ldap.html)
- Don't see your idea?