Add write policy for channels and private groups
This feature is essentially a "force mute" in a meeting room, when you want to enable some people to listen in, but not to speak.
- Add an option to restrict the ability to post to a channel or private group (requires channel header menu redesign--the menu is over the UX guideline of 5-7 options per menu)
- Add the ability to define users who have the ability to post, which would by default include Team Admins. We don't currently have UX for a channel owner or channel creator, but in future Enterprise releases this may be added
- Include UX so that new users understand that they can read but cannot post. This is important in Town Square since it's the largest channel and most likely to be restricted, we need to avoid users joining being completely confused on how to post messages.
This is a complex feature in terms of UX, there's a lot of risk of user confusion, and therefore not a fit for Team Edition, and it could be added to enterprise, academic and non-profit offerings for large orgs.
This feature is under review for Enterprise Edition.
This seems like a duplicate of the popular "Allow a channel to be locked" ( https://mattermost.uservoice.com/forums/306457-general/suggestions/11594328-allow-a-channel-to-be-locked ). If this suggestion fits your needs, please consider upvoting it!
This seems like a duplicate of the popular "Allow a channel to be locked" ( https://mattermost.uservoice.com/forums/306457-general/suggestions/11594328-allow-a-channel-to-be-locked ). If this suggestion fits your needs, please consider upvoting!
"Read Only Channels" or "Comments closed". Good idea.
Please implement a read only channel permission solution. This will allow designated users with proper permissions to post in a given channel, but all others can read the channel. This will be helpful for communities that require FAQS or top-down communications.
It would be nice to have ability to have a channel where only specific person (either a group or say just Team Admins) have ability to speak.
We have few channels that are used for annonucements (like one with food delivery, other with builds etc) that are subscribed by most of the employees, but people still have conversations in it, spamming almost everyone in company with them
Will Fife commented
This would be great! We use the E10 license at work, and could definitely use this to lock down "Town Square"
Apparently I "shared this idea" but this is not my text (someone has edited it).
In particular I disagree with the final paragraph: I don't think it's particularly complex for UX and I think it fits very well with Team Edition.
Wesley Batista commented
I come up here with the same need/idea.
Something like a "read-only channel".
Ben Lambuth commented
This would be very useful for our Announcements channel, so we could restrict users from filling it with chatter and drowning out the actual announcements.
It's more or less the same that :
Hope it will be implemented soon !
Jack McKalling commented
Please implement. Would make organizing channels a lot easier when having a lot of members.
The Doctor Plays Video Games commented
Great idea! Used 3 votes on it!
I think this is a great idea.
This sort of setup would be perfect for any channel I wanted to use for announcements without information getting lost in chat about the announcement cluttering it.
David Cornelson commented
I'd like a way to post information for the team that only I (the admin) can edit. In order to do this, I'd like to lock the channel so everyone can read it, but not edit it except selected users or only the sysadmin.