Sometimes it so happens that a user cannot view the values of a managed metadata column, even if the user has been granted permissions to the library or file. This simply means that the user is still missing permissions, how strange this may sound. The cause? SharePoint operates with a hidden list in which it stores all metadata for the impacted sitecollection. And as it may turn out, your user doesn’t have access to it!
In some cases, when you work with Excel-documents, you’ll stumble upon the Excel-error “Cannot perform this operation. The file has been deleted or someone else has it checked out.” somewhere down the line. Now, there could be a tiny chance that the file you’re working on actually has been deleted or checked out by someone else. But chances are much higher that the error is caused by something else.
Let’s say you have a blog site rolled out. And all company users are granted access through the visitors group. You have assigned read permissions to this group, to make sure everybody can read the blog posts. So far so good, all users can read your blog!
There is a good chance that you set up your blog like this to prevent all users from creating new blog posts, as you want to limit this right to a certain amount of people. That can make perfect sense, only are you hereby preventing all users to comment on your blog posts too. While it can be a good idea to limit the amount of blog posters, you might want to give all people a chance to comment on those posts nonetheless. In this post I’ll show you how to do this.