The two fields that we've added can use some help, configuration-wise.

We'll start with the Groups Audience field:

  1. Click on the Groups Audience field's edit link
  2. Label field = Unit or Group
    1. Because Groups Audience makes no sense to our users
  3. Administrator widget type field = Select List
    1. This will provide a drop-down menu to site admins who may not be members of a given group, but who might still assign content to a group
    2. The auto-complete field that is there out-of-the-box is fine if the admin knows the names of all the groups - otherwise, a select list should really be used
  4. Number of Values field = 1
    1. For dynamic content that could possibly have several groups involved with it, you can change this to another number or "Unlimited"
  5. Render Views filters as select lists checkbox = check this
    1. This provides data to the Views module for this node type that Views then uses to create select list filters
  6. Click the Save Settings button

organic groups unit or group field settings

Now, let's get in and configure our next field:

  1. Click the Group content visibility field's edit link
  2. Group content visibility field = Public, accessible to all users
    1. This merely sets the default, it can be changed to private on individual nodes if the content needs to be visible to group members only
  3. Click the Save Settings button

organic groups group content visibility field settings

Also, to help our users out, we've moved both of these fields to the top of the node submission form, so they're not missed when our users create their content.

So the final result looks like what you see below.

organic groups group content field ordering

This process needs to be repeated on every single content type that a group is allowed to work with.

The next thing to do here is to adjust the display of the fields.