Groups Specific Permissions
Written Steps
In this video we will allow a group to have permissions that are different from all other groups on the site.
Before we begin, I’m going to enable the “Basic Page” content type to be able to be posted to a group. I have shown you two ways to do this for the “Article” content type in the videos “Organic Groups Basics” and “Organic Groups Field Settings”. You can follow those steps to do the same thing for the “Basic Page” content type.
Now that that is done, we see that we can now create a “Basic page” inside our groups.
Let's view the permissions for Group #2.
- Go to "Group #2"
- Click on the "Group" tab
- Click on "Permissions"
Here we can see the "Page Manager" role we just created. I'm going to give the following permissions to "Page Manager":
- Edit own Basic page content
- Edit any Basic page content
- Delete own Basic page content
- Delete any Basic page content
In order for this to mean anything, we need to have a user with this role. So I’ll go to “Group #2” and click on the “People” tab, and give Chelsea the role “Page Manager”
Now when Chelsea goes to Group #2 she has the option to post a basic page. I'll create one now.
- Title: Basic Page #1
- Body: (Lorem Ipsum)
- Groups audience: Group #2
- (Save)
Note: She doesn't have the option to make this private because we didn't put that field to the "Basic page" content type. (This is covered in the video: "Organic Groups field settings".
Let's make Chelsea a member of "Group #1". When we do that, you can see that she can post a "Basic page" here as well because she is a member of the group, and has the site-wide permission "Basic page: create content". If you want to specify which members can post to your group, and what they can post, watch the video "Organic Groups Create Permissions".




Comments
OG Private content - how to block from views and search API
Hi there! Problem: I've been using OG, have article content type private and everything is fine, but:
* when doing views listing, it still displays titles of private node even to non-members
* -||- the same applies to search results with Search API
Any idea how to make them respect privacy?
Hmm...
I haven't had any issues with this. So, my first guess would be to check your views settings. But unfortunately that's only a guess...