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.

152 comments
-
Joachim Van Brandt commented
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
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.
-
Anand Tiwari commented
Yes this is one of the must-have the functionality we are missing. Please make it available soon.
-
Brenadine Humphrey commented
Please make this work. How is this not even a thing yet?
-
Anonymous commented
A must!
-
Richard commented
Need this feature ASAP! Needs to not be part of the GPO structure.
-
./cb commented
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
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
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 -
Shawn commented
Why is this not a thing yet? Seriously. I need my teachers to be able to see the content but not edit. Come on Microsoft.
-
Charlotte commented
Has this happened yet? I really need this function for sharing simple instructions for my team that I do not want them to edit. I can do it in a word document, but there is a delay for the page to load... wiki page is definitely preferable
-
Jeff Poblocki commented
I had a pretty big need for this as this is how we are going to push out our Distance Learning tutorials. I didn't want users editing or deleting anything as recovery is difficulty and there is no version history. I thought of using OneNote but the Wiki loads so much faster and is more friendly to read on a mobile device.
Anyway I figured out how to accomplish it. Please be warned, I do not know if this procedure has any negative consequences. Please implement at your own risk. The behavior in Teams is not pretty but works. For example, if a user goes to edit text, it will appear to allow them to edit but they will soon get a message that says "Unknown error" and when they click OK, any changes are automatically undone. If a new section is created by a user, it appears (for them) and disappears immediately. The same is true for a new page. Any new content created by an Owner of the Team, shows up as it should without any action needed to be taken.
Finally, here are the steps:
Go to the Teams page on SharePoint
Site Contents
Site Settings
Click Wiki on Sidebar under Recent (it will have an odd name)
All Items > Edit Current View
Click 'Settings' on Title Bar to the left of 'Edit View'
Permissions for this List
Stop Inheriting
Set Members to Restricted ViewClick Wiki on Sidebar under Recent (it will have an odd name)
For Each Item in List > Manage Access > Advanced > Delete Unique PermissionsHope this helps someone.
-
Jessica Garcia commented
Yes please lock Wiki. You can only add so many tabs and Wiki is a great way to condense tabs.
-
Ian McArdle commented
At the very least, a button is needed that can be used to lock/unlock the page for editing. It is too easy to accidentally modify or delete something if the wiki page is always editable!
Of course, if said button could be made available only for certain users that would be even better. -
Thomas Wagner commented
Absolutely essential!
Ideally there would be a second permission option allowing users to make changes but requiring owner approval before publishing.
There should also be an easy way to highlight changes vs. any chosen older version.
Actually, this is needed accross the entire platform especially for documents. -
Joel commented
Essential for online learning communities---please make this right, Microsoft.
-
Jared Holt commented
Adding my vote to enable locking the wiki. Would like to use the Wiki to store "work from home" information that shouldn't be changed.
EDIT - I just learned we should be able to control this via SharePoint. Find the "Teams Wiki Data" for that site, click "Manage Access" from the ellipsis menu, and set Members to "Can view."
EDIT 2 - That didn't work. Sorry.
-
Leo C commented
Urgently needed. NHS Teams are using the wiki for standard responses and important information, needs to be limited write access
-
Charlotte commented
I am using wiki pages in Teams to disseminate training material to our colleagues around the world. It is essential that they canNOT edit the wiki pages. Please make this change!
-
Mike Bruse commented
yep, I am doing the same thing. Posting internal guidelines on the wiki but would like to lock it in case someone deletes it accidentally.