Creating & managing groups - private, and public
Groups:
Terms:
Drupal Commons is based on the concept of creating Groups, associating members with those Groups, then controlling access to content based on membership.
So, when you creating a group, there are several things to do:
- Create a group by visiting /groups, and clicking the link Add a new group. By default, any authenticated user can create a group.
- Some sites may not want to permit any authenticated member to create a group. To limit group creation, visit the page /admin/user/permissions, find the row for "create group content", and make sure that the checkboxes on this row are checked-on for only the roles you wish to be able to create a Group.
- Fill out the form with details for your new group. You can optionally upload an image to be used for this group (and it's avatar where groups are listed).
- Set the privacy level. Groups can have three different levels of security & privacy:
- Public, listed. This is the default. If the checkbox for "List in groups directory" is checked, the group will be listed on the /groups page, and the group will be visible to all users.
- Private, unlisted. This is the opposite level of security; in this case, no users can see the group unless they are a member. Non-members attempting to visit the URL for a group of this type will not be able to see the group or its content. To get this, uncheck the "List in groups directory" checkbox, and then check the "Private group" checkbox.
- Public, unlisted. This is a middle-ground; in this case, the group is not listed in the groups directory (/groups), which obscures it from being easily found. However, if a user knows the URL of that group (or if there is a link to it coming from somewhere else), a user can visit this group's home page and see it's content. To get this, uncheck the "List in groups directory" checkbox and do NOT check the "Private group" checkbox.
- Set the policy for joining the group. Group creators can set up groups to handle membership four different ways:
- Open. In this case, any authenticated site member can join the group unilaterally. A "Join" link will be presented adjacent to group names on the /groups page and in the action block at the upper-right corner of a Group home page.
- Moderated. In this case, any authenticated site member can apply to join a group, but one of the group's administrators must approve the application. The "Join" link will be shown at the same places as the "Open" case, but when a member applies to join, the administrators are notified (on the Group home page) of the application, which they must approve, reject, or ignore.
- Invite-only. In this case, the no "join" link ever appears; a group administrator must manually take action to add a member to a group. This is done by clicking the "xx Members" link in the Action block (upper right corner of the Group home page), then clicking the Add Members tab, then entering the usernames of the members to be added. Those members are notified (at next login) that they have an outstanding invitation to join the group. When they click the link to handle this, they can accept, or decline the invitation. If they accept, they can later unilaterally decide to leave the group.
- Closed. This case is almost the same as the Invite-only case, except that the added-user does not have the option to opt-out of the group, nor can they unilaterally leave a group. The Group administrator is in total control of group membership.


Comments
private but listed?
Is it possible to create a private group, but list it in the groups directory lists to non-members?
Does not appear to be one
This is an interesting request; I've never heard it before.
This functionality is probably one of those rare cases where there is NOT "a module for that" (in the classic Drupal phrasing). It probably means adding this code to Organic Groups.
My bet is that nobody will add it to the Drupal 6 version of OG; if anywhere, I bet it gets done for the (new) OG in D7.
Here's the use case: I am Joe
Here's the use case:
I am Joe User, I go to the site and am wondering what groups exist. All groups (even private) are listed. If I click on a private group, I get access denied with an option to request membership. The content inside the private group is not visible to me, and does not show up in search results.
This is exactly how Atlassian Confluence works - it's a good model.
and I need the opposite!
The home page contains a block listing the newest groups and another listing the most active groups. I don't want private groups to be listed in either block. And I don't want the group to show up in search results for people who aren't members of the group.
Interesting point
This is controllable pretty simply by changing the Filters in the view (og_most_active) to add a filter for Organic Groups: Group Private: No. You can either add it to the Default display for the view, or to specific block displays, depending on the behavior you want.
don't forget search results
Thanks for the input, Jay. I had looked into that, but realized that that's not going to filter out private groups from search results.
I think private groups should provide what I'm looking for "out of the box", but I think it's not working for me because I'm also using the Workflow module (I want new groups to be approved before they can be used) - and I think there's an access control conflict.
Quick chip in ...
This is still a very old issue regarding also earlier version of Drupal as you can see from the posting date.
Just FYI some links:
View Frontpage for anonymous visitors that have no view-content permissions.
Anonymous content type?
Exist any way to control anonymous node access in Drupal 6.x yet?
Anyway after many attempt to focus this to all developers with some dedicated issues I got the idea/suggestion that in future Drupal versions may be considered the option of creating a dedicated content-type for all kind of posting (especially: front-page, access-denied, page-not-found, privacy, disclaimers, about etc etc..) that IMHO could have some special properties strict-related with:
For the above mentioned case about "General Group Information" this content type may be attachable or implemented also in OG module.
Considerations:
I continue to wonder why there where never seriously reactions and discussions feedback from the developers and it's so obvious that a related solution would considerably help the quality of usability and management of basic Drupal and in general often created content on a web site.
adding and removing a community manager
Loving the community functionality of DC!
Can anyone tell me how to add and remove a community manager from a group AFTER that group has been created?
Many thanks! (Sorry if I'm overlooking the documentation. I've been searching to no avail.)
Figured it out!
Installed the Group Admin module.
which module is that exactly
which module is that exactly?
How to get approval from admin when a new group is created ?
Hi All,
I have a requirement like when we give permission for other users( apart from admin) to create groups, the group should be approved by admin before publishing. I have installed organic group and tried to do the same, but no luck so far.
Can any one knows how to get approve if any other user creates groups. Its about creating groups not group post.
If its not possible through organic group module, can i achieve the same with any other module ?
Thanks
Moderation Module
Hi there,
I believe simple solution to your problem could be Moderation module.
http://drupal.org/project/moderation
If that does not work, I would suggest workflow module, but it requires more customization although it is more robust
http://drupal.org/project/workflow
Hope it helps
Issues with Groups That Need Attention
I made a recent post about issues with Group Types and Invitations that I and others feel require serious attention. I'm linking it here since it's directly related and could use more feedback both from the maintainers and others who view the Groups documentation.
Inaccuracy
P.S. This following description in this documentation is inaccurate for 1.3 and, in some cases 1.4
Clicking the Add Members tab and entering user names adds people DIRECTLY to the group. They don't have to click on any link or message. This means that the tab is certainly aptly named, but the group is NOT. It is not "invite only", it is "add only". Further, this methodology has a great potential for abuse. Someone could create a group, add everyone to the group, proceed to spam, etc. My understanding is that a message is at least SENT in 1.4 (one of the bug fixes), but I've not read anything that suggests this methodology has been changed.
This is also not an ideal way for this function to work since the Admin of the group has to do this via username (i.e. they cannot alternately use email). It certainly not at all efficient for the Admin to have to remember and type in usernames to add people to the group, especially if the list is sizable.
Hi Icarus, I was alerted by
Hi Icarus,
I was alerted by your OG observations and took some extra effort to look into issues. I know it is a can of worms that nobody wants to touch, but nonetheless it is imperative to start looking into redisign of OG or look for an alternative solution from the scratch. I took some time to analyze the public and moderated group workflow and came with following conclusions. It is more than enough to start debate and I have not done the same for invite only and private groups, but intend to do so when time allows me to do so. It is by far the largest problem with DC and instrumental to its success/failure. It is in no way Acquia's fault, but something that only they can resolve if possible. I am rather disappointed at people that created and maintain OG. They are fast to brag about how they did miracles for Economist Magazine and whom not rather than taking some time to face the critique of their mediocre work at best. I do not see a point of developing D7 version since D6 is fundamentally flawed and I can't see how it will be any better if they are not willing to face the music. Nobody likes critique and ignorance seems to be bliss. Anyhow, this is the image of some of my conclusions.
https://picasaweb.google.com/102649247313375566845/DropBox#5577874175238997986
Admins Aren't Notified of New Group Members??
Yet another area needing attention with regards to Groups.
Progress on mixed public / private site
My site is focused on supporting a private community through various private groups. However, there is also a public front page that provides announcements from authorized members to the anonymousnpublic.
Using the force login option wouldn't allow anonymous users to see the full text of public announcements (discussions), so that wasn't an effective solution.
However, the announcements module seems to do the trick. I can allow anonymous users to see the full text of an announcement by adding announcements/* as an exception to force login. So far, thisnappears to be a workable solution.