How can we make Microsoft Teams better?

← Public

Add ability to lock wiki

For certain teams, we would only want a couple of people to be able to edit the wiki page, with the rest having view only. Or at the least, a way to track and approve/ reject proposed edits.

626 votes
Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Simon Goode shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

83 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • anonyme commented  ·   ·  Flag as inappropriate

    We need to make sure that important information are not deleted. Please add this functionality

  • Erin Alomar commented  ·   ·  Flag as inappropriate

    Absolutely vital that editing permissions can be assigned via membership/owner status. While the information shared is vital for the entire team, it is constantly evolving and needs updated frequently...but only by the team owners. Locking tabs will also ensure no edits/deletions of vital information happens mistakenly. This is an absolute must!

  • Jasper Siegmund commented  ·   ·  Flag as inappropriate

    I have tried the method of Jeff Poblocki but there's a few things to consider. At first this appeared to work, but yesterday we found out that in some way users were again able to edit the wiki. The weird thing is that the changes did not appear in the SharePoint library backing it but were visible for other users in Teams. When I removed the changed made, the SharePoint library reflected my update (as I have permissions on it) but not the one of the colleague who's permissions I removed earlier. So this solution is definitely not watertight and it almost appears as if the SharePoint library is storing merely a copy of the content.

    Also, messing up with the permissions on the Wiki library will very likely impact wiki content across channels, be aware of that when making any changes.

    As for the implementation; it would be sufficient for our usecase to have a setting for a team where one can specify who has permission to use each of the tabs (chat, files, wiki). For us this doesn't need to be more fine grained than "only owners" + "owners + members".

  • DizlC commented  ·   ·  Flag as inappropriate

    piling on here. need the ability to restrict edit privs to a subset of users in teams.

  • Carson commented  ·   ·  Flag as inappropriate

    I'm shocked this feature isn't already in existence. I need a way to communicate information that changes every few days and I was hoping this would be my option, but if all my team members can edit it whenever they want, it invalidates everything.

  • Anonymous commented  ·   ·  Flag as inappropriate

    We use Wiki in Healthcare settings to store documents that are browsable. Needless to say the ability of everyone to edit makes this feature useless. There needs to be a toggle to allow and disallow edit. This is a great feature though, overall.

  • Joachim Van Brandt commented  ·   ·  Flag as inappropriate

    It looks like version history is enabled.

    I started to follow Jeff Poblocki's instructions. I couldn't find the "Permissions for this List" as he described - it looks a bit different - but you can find versioning there. At least with this you can restore to previous versions with that and see who your culprit was.

    I'm going to play with the approvals settings to see if those work.

  • MCB commented  ·   ·  Flag as inappropriate

    The Wiki feature is extremely risky to use without this - the ease of editing is both a great feature and an Achilles heel. Any user could accidentally select a large amount of content and delete it - and there is no version history to restore from.

  • ./cb commented  ·   ·  Flag as inappropriate

    Jeff's method works. Thanks mate.

    .. >> Jeff Poblocki commented · March 31, 2020 11:52
    Longer version of the the same thing attached as a rtf file.

    I did a bunch of other testing and also locked out 'files' so that I could put company policy information in there.

    @anonymous.. perms at 'Teams Wiki Data' just don't apply.. I guess they're overridden by the hidden guid.blah.blah@thread.tacv2.wiki (or similar 'odd name') and you must block inheritance before setting the perms there. Again, not my work, I hate trying to fathom the sharepoint permissions nightmare. This is all based on Jeff's comment further down.

    ( can't imagine why that isn't surfaced as a simple perms dialogue in Teams itself, also can't imagine why all these perms are structured in such a complicated and contradictory way when the Active Directory perms structure already exists in the MS Cloud and is both robust and simple /rant).

  • Anonymous commented  ·   ·  Flag as inappropriate

    I did what you describe bellow but it did´nt work. Members still can edit wiki. What is wrong? Is there anything else that must be done?

  • Anonymous commented  ·   ·  Flag as inappropriate

    Open the Team in SharePoint
    Browse to Site Content
    Select Teams Wiki Data
    Select General
    Click the 3 dots at the end of all files in this folder and select Manage Access
    Then you can toggle the options and set members to View Only

← Previous 1 3 4 5

Forum Home

Reference Information for Teams

Public: Wiki

Categories

Feedback and Knowledge Base

(thinking…)

More Teams Information