To create groups in Drupal we have at this moment the Group module and the Organic Groups module.

From the Group module page:

The Group module allows you to create arbitrary collections of your content and users on your site and grant access control permissions on those collections

From the Organic Group module page:

Enable users to create and manage their own 'groups'. Each group can have subscribers, and maintains a group home page where subscribers communicate amongst themselves.

What are the features of Group versus Organic Group?

  • Isn't this an opinion-based question ?
    – mchar
    Commented Apr 11, 2016 at 13:35
  • 1
    @mchar I don't think this because this is based in facts. You can say Group have this functionalities, but Organic Group don't have it. So with Group you can do this kind of things but not with Organic Group. Commented Apr 11, 2016 at 13:44
  • Thanks for the clarifications, I was just asking, I didn't know that modules comparison is accepted, now I know!
    – mchar
    Commented Apr 11, 2016 at 14:59
  • @AdrianCidAlmaguer : have you noticed that your question here also illustrates the 4th bullet I mentioned in the "disadvantages" of my answer? Check the revision history of your question ... Commented Apr 11, 2016 at 21:05
  • Pros and cons could be subjective when talking about something, but it doesn't seem subjective when talking of a module's features. Maybe the question can be rewritten to avoid using that term.
    – apaderno
    Commented Oct 5, 2016 at 11:25

2 Answers 2



The Group module allows for creating arbitrary collections of your content and users on your site, and grant access control permissions on those collections. It is available as of D7, and has a D8 version also. It is designed to be an alternative to Organic Groups.

Organic Groups allows content itself to be groups, which isn't always what people want. It relies on an entity reference field to keep track of the ties between a group (node, term, ...) and its content (node, term, user, ...)

Group instead creates groups as entities, making them fully fieldable, extensible and exportable. Every group can have users, roles and permissions attached to it (refer to "What are the various roles supported by the Group module?" for more details about that). Groups can also act as a parent of any type of entity. Group provides an extensive API to attach entities to groups.

Advantages of Group as compared to OG

  • Group started in D7 only, taking full advantage of entities introduced in D7.
  • Group doesn't 'abuse' nodes by adding custom fields to them in order to make the module work.
  • Group does not allow you to have per-group roles or permissions. These are instead defined on the group type. So group types, group roles and permissions are configuration instead of content. Because of this approach, group types and roles exportable (with or without Features).
  • Organic Groups is commonly perceived as a huge module, which carries a lot of "legacy" from pre-D7 releases and makes it tougher to ever get upgraded to D8.
  • A D8 version of Group is already available (not so for Organic Groups).

Disadvantages of Group as compared to OG

  • As of today, Group only has alfa / beta releases (not any official release).
  • Even though some say it is self documenting, I think it is not (maybe because I don't want to digest the source code to find out what this module can do ...).
  • Not a lot of documentation available.
  • As of today, there is no tag on drupal.SE, though there is an tag, and there are already quite a few Group specific questions. Anybody interested in creating it (again), feel free to reuse my previously approved tag wiki and/or tag excerpt (no need for credits ...).

Integration with various modules

The Group module integrates with various other (popular) modules, including:

The beauty, IMO, of these integrations are that they are more or less out-of-the box (not dozens of extra modules needed to make those integrations work).

Refer to Integrations with other modules and its "Related issues" about other modules for which integrations already exist, or are in the pipeline.


What people say about the Group module

Similar to what you see in the Group issue queue: most (if not all) people who know about Group just love it ...


There is an article that comes from being published named: GROUP FOR DRUPAL

The author says about group:

  • Simple

Groups should be like content types. I want different kinds of groups with different fields, roles and permissions. That’s exactly how Group handles it.

  • Group content

Basically anything you attach to the group can be fieldable. Another interesting thing about the relationship entity that sits between the group and the actual user/content is, that if you delete it from the Group interface, you are not deleting the content, but the linking entity instead, so the content (or user/entity/whatever) is left unchanged.

  • Powerful

Every group type has their own group content types and every one of them has configurable permissions and fields.

Out of the box, Group integrates with Views, Rules, i18n, Title and I’m sure much more is coming. Built on top of Entity, API Group provides all of its benefits to developers.

And as conclusion:

There is no doubt that Group is here to take the place of OG. It has everything that OG provides plus all the things that were missing. All brought in a neat UI, where you can configure so much without being a coder.

The only downside of Group I can think of currently is the state of the module. It’s currently marked as alpha, but seeing the growing number of contributors and downloads can only mean the development speed is increasing. It’s also hard to expect finding a lot of answers online, because Group is a very young module. Nevertheless, given very good response rates on the module’s issue queues I would say that writing a ticket is your best bet if you need any help.

EDIT: Another god article to read is: Building Community Sites in Drupal 8: A Guide To D8 Modules For Community Support Sites

  • Didn't know about this article! Commented Sep 23, 2016 at 17:05
  • 1
    "It has everything that OG provides plus all the things that were missing" For what I understood, permissions are defined site-wise, not group-wise. If you want each group admin to define the permissions for the content in its "own" group, you can't in group, but you can in OG.
    – Antonello
    Commented Jan 26, 2017 at 13:28

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.