EE: Single-Channel Guests for non-team members
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.
This is now available in Beta in E10 and E20: https://docs.mattermost.com/deployment/guest-accounts.html.
We need this feature very much so! I can assure you that this is required by many others too!
Max Lapshin commented
Hi. I have enterprise license for mattermost. We need this feature very much!
Vladimir Vlach commented
We are currently looking for a solution to replace Slack with another product. Only feature we are looking for is Guest feature. Having this in Enterprise product indicates to us, that all great features will be paid. Not a good signal.
Only product we found is Twist, which gives you guests for free.
TJ Nassar commented
This has been open since 2015. Is there any movement on this at all please. It's making it increasingly difficult for us to keep using Mattermost (which we love!). I'd also like to echo other users in that it should absolutely not be limited to the enterprise version. It's the smaller companies and those that rely on your Team Edition that would benefit the most from this.
Perhaps you could offer it as a one time add-on or yearly subscription?
Michael Borohovski commented
This would be incredibly useful for us as well - is there a rough ETA for when this will happen? A year and quarter perhaps?
How do you not have this as a feature yet, this is critical for businesses to work with outside vendors.. Without it, we cannot move to your platform. Agreed, with other comments as well. Should not be for enterprises, this is a feature smaller companies use.
This is perhaps *the* feature that makes/breaks our case for moving to Mattermost from Slack. We have a lot of customers/contractors/consultants that we do not want to give full access to all channels, but rather restrict to the channel(s) that are relevant for them. It all boils down to a security compliance question, really.
Slack and MS Teams has it, so in order to be a viable alternative, this needs to be in place imho. Whether or not to include it in the Team and/or E10/E20 editions is another discussion.
Just chiming in here that this would be an increadibly useful team edition feature...
I totally agree with the comments that this should be a Team Edition feature. We're already doing it by having a separate team for external people, but it's an awkward workaround for a small company--basically, everyone in the company is in both teams just to enable us to have one channel that we can invite non-employees to. Not to mention that we have to configure the email domain for every outsider we want to invite.
Small teams and sole proprietors need it even more than deep-pocketed enterprises.
I think this should definitely make it into Team Edition. The main use case for us would be to have a channel for communicating with potential team members during the interview process. As a small non-profit do we really have to count as an enterprise to allow our team to grow, while keeping our communications on a single platform?
Small teams need this feature a lot. We are four people, and are using other people to work with us - and allowing them to see just one channel is really important and needed !
Nate Gardner commented
This feature is free in Discord and works quite well. As a member of a small startup (25 people) we frequently want to invite non-members to our Slack server without giving them full permissions. To do this, we ended up creating a second Slack server just for communicating with non-members. We would switch to Mattermost in a heartbeat if this was available for free. Even if this was in E10, we would probably buy. But E20? No way. We're not enterprise. We're a humble group of geeks. Can't be bothered! Please listen to your users.
As you can see by the number of votes, your users would not be confused by this feature. I love your sentence that starts with: "We think of this as a feature for corporate compliance, and feel it would confuse Team Edition if it were added." <-- This is soo oldschool product development. I think, I feel ... listen to the customer
Tejay Cardon commented
So, this has been "planned" for over a year and has more than 500 votes. Any chance it's actually going to get scheduled and worked on someday?
Željko Trogrlić commented
This feature is critical for Scrum teams as Product Owner is often external.
Pascal Diener commented
It's really annoying and not understandable why this Feature only comes to E20 and not E10. As already written, it's possible to do this as well with Private Groups, but that's as well not the meaning of such a tool!
It is a Feature which could be hardly used by smaller companies, where I see E10. It makes no sense to add full User for example for external temporary workers or to get a Customer into a discussion.
Wish would be to have it in Team Edition, but it could be a compromise to have it in E10.
To push it into E20 is just a reason to don't choose Mattermost.
It's unclear to moe whether or not this feature has already been implemented in enterprise edition?
We too would love this feature. We currently pay for Slack and use the single channel users for managing contractors. But we'd really love to support a Go based and self hosted solution and are looking to move to MatterMost, but this is a bit of a deal breaker currently. Is there a timeline for this feature?
I find the planned response for "Enterprise Edition" ONLY, absurd. Sure backing on your Manifesto about teams is a great fallback (for the response), But your neglecting the teams that have to work with other entities and new potential teammates.
This feature is basically already possible if you make all your "Channels" -> "Private Groups"... So what are you gaining by not letting this be a real feature?
You are losing startups / small businesses from adopting this platform to run their "Team" because of this real world scenario.
Enterprise Edition should focus on TRUE Enterprise requirements and not hinder the startup / small business "Teams".