Skip to main content

How SharePoint Community Membership Works

Community site template is a new feature in SharePoint 2013. It provides a forum experience in SharePoint.
Microsoft also mentions about four types of Communities and membership permissions. Details can be found here.

I'm producing the table mentioned in the above link, as this is the topic of today's post.

Private communityA community for sensitive information where you want to limit participation to specific users or groups.Grant Member permission only to those individuals or groups who are appropriate.None
Closed communityEveryone can view the content but only members with approved membership requests can contribute.Grant Visitor permissions to everyone. Require explicit requests to join.Enable access requests
Open community with explicit membershipEveryone can view the site and receives automatic approval upon joining.Grant Visitor permissions to everyone. Require explicit requests to join.Enable auto approval
Open communityEveryone has membership and can contribute to the community without having to explicitly join.Grant Member permissions to all.None

When I went through this table, it was not easy (my own observation) to understand the concept behind these types of communities. So I had to try each option to understand how Community Membership actually works. After trying out the possibilities, I thought I should explain in a better way. The end result is the below image.

I hope this image is self-explanatory, provided you have at least seen basics of Community. If you feel that this image is not accurate/complete or some details can be elaborated, please leave a comment.


Popular posts from this blog

How to update Person field with multiple values using REST API

Person or Group field in SharePoint is similar to a Lookup field. When you are updating this field using REST API, you need to append "Id" to the name of the column in the body construct. For example, the body construct looks like this: data: { "__metadata": { "type": "SP.Data. ListName ListItem" }, "Title": "First Item", " PeopleField Id": "4" }; The highlighted portions should be replaced by the actual List Name and Column Name. In the above example, the REST call is updating a List item with Title and People columns. How to get the value for user ID ("4" in the above example) needs a separate explanation and that will be my next post! The above example works fine if Person field is configured to accept only one value. If we change the Person field to accept multiple values, how do we pass more than one value in the REST call? Since we normally separate user names with semicolon in peop

All about SharePoint List View Styles

Sometimes, there are out of the box features which we tend to ignore and later when we do apply, we are more than happy about the feature which is readily available in SharePoint. One such feature is List View Style. I never thought I would write a post on this. However, whenever I spoke about this with users, people were excited to see the result. That prompted me to write this post. Instead of getting into only theory part, I will basically take use cases where these styles can be applied and also touch up on on some minor limitations with certain style. When you are creating/modifying a List view, you will get an option to select View Style. As shown below, there are 8 options available and Default is always set if you ignore this style. List of View Styles I will take typical Contact List and Announcement List to explian about these styles. Let us go one by one. Default: This view, as name suggest, is the default style in a view. This is one of the widely seen style

How to get Search Refiners using REST API

As Title says this blog is about getting SharePoint Search Refiners using REST API. I could not find examples in internet for getting refiners and how to read refiner JSON data. So I did kind of research and trials and finally I was able to get the refiners using REST API. I assume that you are already familiar with fetching search results using REST API. If not, I suggest to read this fantastic post by Chris O'Brien . I have extended the example given in this blog to refiners. Let us first understand how to frame REST query to get refiners. The syntax of the URL is http://[your site]/_api/search/query?querytext='SharePoint'&refiners='[refiner]' To get refiners, refiners keyword should be passed as a parameter along with the actual refiner that we need. Before I show an example, let us first check how XML response would look like if you don't add this keyword. Without Refiner As marked in Red, if we don't pass refiner as parameter, Refinemene