Read Only channel
Would like to create a Public/announcements Read Only channel so that only specified members can post. This allows for authorized personnel to make company announcements, but not everyone can post.
(The request for a Public Announcement channel is complete, since the General channel can be controlled by admins and set to read only)
Anonymous
shared this idea
Due to a priority shift this request has slipped to the backlog. I hate to bring bad news. I will continue to provide the feature team your feedback and votes.
Hopefully this will move back up in the queue soon.
-Warren
79 comments
-
Kensley
commented
What is the latest news on this proposal from the Microsoft Team?
-
Russell
commented
Moderation makes some things read only, but not everything in the channel. For example the channel's files tab, what (if anything) does moderation do about them? And other apps/tabs that are added don't allow for moderation. If we could remove or restrict the Files tab, then we could have a public announcement channel...
-
Tim Banting
commented
Would people think this is more, well, Yammer-like? I would like to see Teams and Yammer merge for all collaboration down the line. Is there really a use-case for keeping them separate?
Plus Wiki tab? How very 1990s! - I would like to see this as an alternative to Yammer discovery feed so that a summary of a busy channel can be seen. (Supporting # tags? Word clouds? Sentiment analysis?)
-
Jeff Layton
commented
This is partially enabled already, with channel moderation you can limit who can reply and post, and when you open the files tab in sharepoint you can navigate to the root and then manage access for the particular channel you select and change members to read only, now members can not edit documents.
As for Wiki you can do it like this, pulled from another user on another post:
Dan commented · August 28, 2019 12:58
History and Permissions can be accessed by:1. Select "Open in Sharepoint" from the channel options
2. Go to "Site Contents" on the left-hand side menu
3. Select "Teams Wiki Data" from the contents list
4. Select the channel folderPermissions can be viewed/modified by selecting the opening the "Details Pane" by clicking the "info" icon in the top right
Version history can be viewed/restored by expanding the options menu directly to the right of the wiki name
It doesn't look like it's integrated into the teams desktop app yet, but some limited options ARE available
-
John DeHope
commented
I think the moderation is a start, but there are already so many other features of a channel that moderation doesn't address. I think what everyone wants is one single "read only" checkbox. Moderation makes some things read only, but not everything in the channel. For example if you add files to a channel's files tab, what (if anything) does moderation do about them? Or if you add a planner tab, does moderation make the tasks read only? I don't think it does.
-
NL
commented
Doesn't moderation deal with this issue pretty well?
https://docs.microsoft.com/en-us/microsoftteams/manage-channel-moderation-in-teams -
John DeHope
commented
Hello, just adding my vote here. I'd like to be able to have more control over Member's access. Currently there are a lot of checkboxes that make it easy to control a lot of Member's access. But I'd like one that says "read only". This would let me have a public team that anyone can join, they'd be able to read anything they like, but only Owners would be able to update or add anything. Then I can make a few select core people be Owners and let everyone else be Members. I think having just two levels of access (Members and Owners) is fine for my needs, if I can just cut down to read-only what that lower level of access can do. Thanks!
-
Asen
commented
Any news on this one?
-
Pierre
commented
It is really important that some "stuff" - like Wiki tab - has control on who can edit and delete!!!
-
Seth
commented
The settings to block posts to conversations on General channel are an improvement, but that does not address Files or tab content. For all the same reasons it makes since to control posts to General, a team may want to control edits to a Wiki tab.
-
Anonymous
commented
I want to create a release channel whenever we use Azure Devops to deploy something new. This channel needs to be read only except for AzDO web hook (admin only). It would be cool if people can show their appreciation using emoticons (similar to Discord!)
-
Kathryn Whiteley
commented
A channel owner should be able to control permissions for the channel, including who can post (all members, or only owners?)
*Any* Team should be allowed to have one (or more) read only channels within that Team (not just the org-wide Team).
-
Anonymous
commented
We totally need this. In big organizations that want to be transparent, it would be very practical to be able to follow a discussion and contribute through the "official channels" (i.e. your leader or representative), but avoid 700 people commenting. Read, and tell your rep what you think. Your rep/leader can post, and you can follow the decision-making process. Please, please, let us have this!
-
Steve Thomas
commented
This is an important feature which I hope will be prioritized as soon as possible.
-
Danielle Sawyer
commented
This feature exists (to an extent) already.
Go into Manage Team and then Settings - Under Member Permissions you can set the GENERAL channel in the team to read only except Team Owners. -
Anonymous
commented
at least enable this setting via PowerShell. This feature is already working on the "General" channel, so it sould be easy to allow this to other channels too.
-
Anonymous
commented
it should be treated as Announcement
-
Mikkel Thy Christensen
commented
Our company need this for management to be able to inform in a org-wide channel, without others being able to reply, just read and have the info!
-
Phill
commented
please let us know either this, or pinning, or something..
-
John Elliott
commented
This needs to happen. Again it ties into the difficulties of a allowing "Private Channels". To be perfectly honest, Teams reliance on Sharepoint as it's back-end is severely hampering any ability to develop feature requests into this product.