This video will briefly discuss the general OG settings found at admin/config/group/settings.
- Go to "Configuration => OG settings" (admin/config/group/settings)
Group manager full permissions
This will decide whether or not group managers should have all permissions within their groups. This can be useful when users are creating groups on your site, but you don't want them to have full permissions in the groups they create.
- If the box is checked, the group manager will have all permissions, regardless of what roles they have.
- If the box is unchecked, group managers will only have the permissions associated with the roles they have. Thus being equal to any other member of the group.
And just to clarify, a “group manager” is the user who creates the group.
Strict node access permissions
- If the box is checked, any role with the Edit any page content permission who is not a member of a group would be denied access to modify page content in that group.
- If the box is unchecked, users with site-wide permissions like “Article: Edit any content” will be given access to modify articles posted to groups even they don't have the OG permission to do so.
Admin people View
This is the View that is used on the “people” pages inside groups. For example, I can go to “Group #2” and click the “Group” tab, and then click the “People” tab. The table at the bottom of the page is simply a view that comes with Organic Groups. You could clone this view and modify it, or create a new one from scratch and select to use that view here.
Group Manager Default Roles
By default, when a user creates a group, they do not have any group roles. If you have enabled “Group manager full permissions” above, this won’t really do anything useful. However, if you disable that option, you could select a role here to automatically apply to users when they create a group. This could be useful if you don’t want users to have permission to change the group’s permissions, or add new users, for example, but do want them to be able to create, edit and delete content inside their own groups. In this scenario, you could create a new group role for this purpose, or change the permissions of the “administrator member” role to suit your needs.
This will simply use the core’s queue process to perform tasks such as deleting memberships when groups are deleted.