Check the box next to the custom permission level you created, then OK.Click the check box next to the desired Site Security Group, then Edit User Permissions Now, all we have to do is assign the Members Group (or Visitors Group) this custom permission level.Now, our custom permission level has been created! Scroll down to the end of the page and click Create.Next, scroll down to a list of specific permissions and uncheck both View Versions and Delete Versions.Give it a name, you can also specify in the description the specifics of this custom permission level Once the Permission Level has been copied, you can now make changes to it.Instead, just scroll all the way down and choose Copy Permission Level Otherwise, you will mess up the out of the box permission level.
DON’T MAKE ANY CHANGES on the screen that appears next. So go ahead and click on Edit Permission Level To create a custom permission level, I suggest we just copy an existing one and adjust it slightly. From the ribbon, choose Permission Levels. Under Users and Permissions choose Site permissions. Navigate to the root (the very top-level site) of the site collection where your site resides. What you can do is create a custom permission level and not allow access to the older versions. By default, visitors and members of a site (those with Read, Contribute or Edit permission level) can access the previous versions of a document or a list item. It takes a bit more time to set up but is totally worth it. To mitigate the “no versioning for everyone” scenario from above, you might want to consider this other option. There will now be no version history stored or accessible on any of the documents in this document library.Ĭons: No versioning means NO versioning for anyone in that library Option 2: Create a custom permissions level Choose No versioning radio button, then click OK at the bottom. Under Settings, choose Versioning settings. Navigate to the library where you want to disable versioning. When you disable versioning, you only store the latest copy uploaded or modified. By default, major versioning is enabled on all document libraries in SharePoint Online. This can be an easy fool-proof way to prevent old versions from accidentally being retrieved. Click here to read more about the new mandate enforced by Microsoft. Option 1: Disable versioning altogether NOTE: If you are in SharePoint Online, this trick below is now only possible if you opt out of the new minimum of 100 versions on a file. Well, there are a few ways you can achieve this. Out of the box, Version History allows to easily access older versions if need be. As part of their industry regulation, they need to make sure that users cannot accidentally access the previous versions of the document. 
They are using SharePoint Online to store various policies/SOPs and specifications for their engineering practice. I had an interesting request from one of my clients the other day.
0 kommentar(er)
