OGUR Settings Page

Only users with role ('administer og_user_roles') may configure this module.

Go to Administer >> Organic Groups >> Organic groups user roles:

(Note: Don't forget to click on "Save configuration" button to save your choices.)

  • Assignable roles

    Check the box next to each role you wish group admins to be able to manage. Make sure you have assigned the appropriate privileges to roles selected here. Note that because these will be assignable by non-site admins, you should be conservative in what permissions you give (maybe 'create' permissions on a special node type, etc.)

    Again, whatever roles you select here, when they are assigned to a user in a group, that user will only have the permissions of that role while he is within the context of the group in which he is assigned the role. When he is outside of that group's context,
    he will no longer have this role.

  • Permissions table for users with 'configure restricted member roles' permission. (6.x and higher)

    Users with the configure member roles permission may assign any group role to any user within the group in which the user has this permission. Users with the configure restricted member roles permission may only assign roles that they have permission to assign. You must define here for these users what permission allows a user to assign what role. If the user has a role which contains the permission, he can assign the applicable role. If not, then he cannot.

    Enter here a table consisting of each permission that allows a user with the 'configure restricted member roles' permission to assign a specific role to users in a group

    Users with the configure restricted member roles permission must have a role which contains the permissions required to assign specific roles. There should be a permission for each role that can be assigned by this user. You must define that relationship here. Every permission goes on a separate line. Each line consists of the permission itself and the role to which the permission grants the user the right to assign to another user. Each permission / role combination is separated by the | character.

    Structure your entries like this:


    permission|role

    For example:


    assign GroupMember role|GroupMember
    assign GroupAdmin role|GroupAdmin

    Each record is on a separate line. Each line contains the permission required to be able to assign a role, and the assignable role that permission allows. Each permission and role on a line is separated by a |.

    Please note that there are now 10 "permission templates" provided by OGUR (see: http://drupal.org/node/397954). These permissions can be used to configure the "permissions table" in order to grant role assignment rights. For example, if you configure the "permissions table" this way:


    ogur perm 01|GroupMember
    ogur perm 02|GroupAdmin

    Then, you can give the "ogur perm 01" permission to users who you wish to be able to assign the "GroupMember" role, and give the "ogur perm 02" permission to users who you wish to be able to assign the "GroupAdmin" role. This, of course, assumes that the user already has the configure restricted member roles permission.

  • Allow Group Admins to define Registration Codes for new group subscribers to moderated groups

    Allows you to allow Group Administrators to define Registration Codes to allow users to subscribe to moderated groups without administrator approval. Your Group Admins must have the "manage registration codes" permission to use this setting. See: http://drupal.org/node/217229

    Allow Group Admins to set Registration Codes for users to join their moderated groups without admin approval?

    Do you wish to allow Group Admins to define "Registration Codes" to allow users to subscribe to their groups without admin approval? The Group Admin will be able to define the Registration Codes on edit (not creation) of the group node. Group Admin must have the "manage registration codes" permission.

    Require users enter a Registration Code on site signup (user registration)?

    If you have checked the box above to allow Group Admins to define "Registration Codes", do you also wish to make entry of Registration Codes mandatory on the "User Register" screen? If you check this box, then no one will be able to sign up to your site unless they have entered a valid Registration Code. You should only check this box if you are sure that every user who signs up to your site will have access to the correct Registration Code to be able to automatically join the correct group. If you are unsure about any of this, do not check this box. See: http://drupal.org/node/394522

  • Set default basic group (group limited) role for users who join groups of this type: Group Type?

    Do you wish to automatically assign a specific "basic group role" to every new group subscriber at the time he subscribes to a group of this type: Group Type? The role is limited to the group that he is subscribed to, and only if the group is of the type: Group Type. If so, then place a check in this box.

    "Role to use as a group type Group role:"

    If you wish to assign a role based on the group type Group Type, then select the role to assign here.

  • Allow group admins to approve new signups

    If user registration to your site requires administrator approval
    and you allow users to subscribe to groups at registration, then
    you can optionally allow the administrator(s) of the group(s) to
    which the user is subscribing to approve the signup request.
    This will require that the administrator of each group that you
    wish to give this privilege have a role which includes the
    administer users permission.

    Allow group admins to approve new signups?

    If your site requires administrator approval for signups: When a
    user registers and elects to subscribe to a group (group is on
    registration form), then the admin of the group will receive an
    email notification of the pending signup and be allowed to
    approve it. Note that this requires that the group admin have
    a group role which includes the administer users permission.

    If:

    1. Your user settings require "administrator approval" for new signups.
    2. You have listed OG groups on your registration page for new users to subscribe to at signup.
    3. You want group admins to be able to approve new users who have elected to subscribe to their groups.
    4. The group admins that you wish to be able to do this have at least one role which gives them the "administer users" permission.

    Then, you should check this setting on.

    Please note that if a new user elects to subscribe to multiple
    groups at signup, any group admin (who was the "administer
    users" permission) from any of the selected groups will be
    able to approve his account. This also means that any group
    admin (with this permission) from any group a user belongs to
    will be able to delete the user's account.

    Usage notes:

    • Group admins with the "administer users" permission will receive emails for new signups to their groups. These emails will have a link to URL oguseredit to edit ("approve / deny") the user account.
    • When the group admin has the "administer users" permission in his group, a "Manage users" tab will appear on the OG "Members" screen (og/users/$your_group_id). Clicking on this tab will allow the group admin to list all users in his group and edit their accounts.
    • When the group admin has the "administer users" permission in his group, a "Users" link will appear in the Main Navigation Menu. If the user clicks on this link he will get an "access denied" message. This is because this link is for sitewide user administration, and group admins only have the "administer user" permission within their groups. They need to click on the "Manager users" tab on their group "Members" page.
    • URLs for group admins (with "administer users" permission) to view users in a group (where $gid = Group ID):
      • ogusermanage/$gid
      • /og/users/$gid/manage

      URL for group admins (with "administer users" permission) to view an individual user in a group (where $gid = Group ID and $uid = User ID):

      • oguseredit/$uid/edit?gids[]=$gid
    • Important: If you do NOT want a user or group of users to be edited using oguseredit, then you must give them the OGUR permission no oguseredit. User accounts which have either a site-wide or group role with the "no oguseredit" permission can NOT be edited using oguseredit.
    • Also, very very important: If a user has a group role with the "no oguseredit" permission in any group he belongs to, his account will NOT be accessible using oguseredit. That is, if a user belongs to two groups, Group A and Group B. If the user has a role with the "no oguseredit" permission in only Group B, his account can NOT be accessed by oguseredit in either Group A or Group B (or any other group he belongs to).
    • We have noticed that these URLs do not work unless the "Clear the cache" setting below is checked on. At this point, we don't know why.

    Requires the mimemail.module: http://www.drupal.org/project/mimemail

  • Default Non-Group Role for new users

    If you wish to assign a default site-wide role to every new user that
    signs up to your web-site, place a check in:

    "Set default global (site-wide) role for new signups?"

    and, select the role to which you want all new signups assigned from
    the pulldown menu:

    "Selectable roles:"

  • Default Basic Group Role for new group subscribers

    If you wish to assign a default group specific role to every new subscriber
    to groups on your your web-site, place a check in:

    "Set default basic group (group limited) role for users who join groups?"

    and, select the role to which you want all new group subscribers assigned from
    the pulldown menu:

    "Selectable roles:"

  • Allow Group Admins to define Default Basic Group Role for new group subscribers

    Allows you to allow Group Administrators to define a default group role to automatically assign to users who join their groups. The role is specific to the group to which the user is subscribing. That is, the user will only have the privileges of the role in the group he is subscribed to.

    Allow Group Admins to set default basic group (group limited) role for users who join their groups?

    Do you wish to allow Group Admins to define a specific "basic group role" for every new subscriber to their group at the time he subscribes to the group? The role is limited to the group that he is subscribed to. This role assignment can be be removed by the groups' admin(s). The Group Admin will be able to define the default group role on edit (not creation) of the group node. The Group Admin must have the "auto assign group roles" permission to be able to define default group roles for his group. See http://drupal.org/node/177414 for more information.

  • Default Founder Role for users who create groups

    If you wish to assign a default group specific role to a user who creates a group, then place a check in:

    "Set default group founder (group limited) role for users who create groups?"

    and, select the group role to which you want the group "founder" user
    assigned from the pulldown:

    "Role to use as founder role:"

  • Default Group Role for new group administrator

    Allows you to select a group role to automatically assign to users who are elevated to group administrator. The role is specific to the group(s) in which the user is a group administrator. That is, the user will only have the privileges of the role in the group he is the administrator for.

    If you wish to assign a default group specific role to every user who is newly elevated to group administrator status, then place a check in:

    Set default group (group limited) administrator role for users who are elevated to group administrator?

    and, select the group role to which you want the new group administrator user assigned from the pulldown:

    Role to use as group administrator role:

  • Default Group Admin Notification for new subscribers

    If you wish to automatically send an email notification to the group
    administrator when a new subscriber is added to a group, then place
    a check in:

    "Send email notification to group admin when new subscriber
    is added to group?"

    Note that this feature requires mimemail.

  • Nodes to automatically place into all available groups

    If you wish to have certain nodes automatically placed into all
    available groups each time they are modified, place the comma
    separated node id numbers into this box:

    "Nodes to automatically place into all available groups"

    Note: This is really a specialized customization for my own site.
    Use it only if you need it.

  • TAC / OG Access Control Integration

    This is a very specialized feature that you should leave unchecked
    by default. We have been working on an access control project
    which allows TAC and OG to work in unison. Basic details of this
    project are here: http://groups.drupal.org/node/3700

    Other related issues

    In order to use this feature, you will need a special patch
    installed: http://groups.drupal.org/node/4026.

    OG User Roles no longer (as of release 5.x-2.4) requires installation of the OG Forum module. However, TAC/OG Integration does require that the og_forum.module http://www.drupal.org/project/og_forum be installed.

    Also, the OG User Roles module will have to be weighted higher than the Node, Taxonomy Access Control and OG modules. The Module Weight module would be good for handling this: http://drupal.org/project/moduleweight.

    Again, unless you understand this project and know what you are doing, please leave this unchecked.

  • Create Subgroups

    Allows you to select a group type to use for displaying a
    "Create Subgroup" link on your group menus.

    Users will need to have the "create og_subgroups" and "create group content" permissions in order to access this link on their group menus. Note that this functionality requires the og_subgroups.module.

    To use this, you must first have og_subgroups.module installed.

    Next, you place a check in this checkbox:

    Create link to "Create Subgroup" in group menu?

    Finally, you select the group type to use for creating subgroups
    from this pulldown menu:

    Group type to use for subgroup creation:

    If a "Create subgroup" link does not appear on your group menu after verifying these settings, please see Create Subgroups notes here: http://drupal.org/node/334886.

  • Clear the Cache?

    We found that there are some modules which will return "Access denied" message even when OG User Roles returns permissions which allow the user access. This is due to cached permissions being used instead of the group permissions. This settiing allows you to reset these permissions for a user on an ongoing basis if you are having this problem.

    Clear the user_access() and cache_menu caches for user?

    Do you wish to automatically clear the cache_menu item and reset the user_access() cached permissions for this user? If you select this option, you will need to apply the og_user_roles.user.module.5.2.patch to the user.module. See http://drupal.org/node/177948 and OG User Roles and File Upload http://drupal.org/node/166566 for more information. Please note that this setting creates a heavy overload as permissions must be re-created on each page load. Use this setting only if absolutely necessary.

    Place a check in this checkbox if you wish to use this option. If you select this option, you will need to apply the og_user_roles.user.module.5.2.patch to the user.module for it to be effective.

  • Test/Debug

    This option allows you to output debug info to a table. You must first
    follow these instructions here to create the table:
    http://drupal.org/node/164038

    Once the table is created, place a check in this checkbox:

    Output debug data to og_user_test table?

    Every time user_access() is called, it will call og_user_all_roles()
    which adds group roles to $user->roles. This option allows you to
    see the output from this function. (Note that this feature is for
    testing/debug purposes, and could create a very large output file.
    This feature also requires that the table og_user_test already exist.)

  • Group Logo Attributes

    Group admins can now upload a logo for their group: http://drupal.org/node/256423. The logo path is entered into Location of group logo field in the group edit page.

    Here you enter the maximimum width and height attributes for Group Logos.

    Maximum width for display of group logo?:
    Enter the maximim pixel (px) width at which group logos will be displayed

    Maximimum height for display of group logo?:
    Enter the maximum pixel (px) height at which group logos will be displayed

  • Counter for og_users_roles table:

    This is the counter for the og_users_roles table. You do not need to set this. It will update itself. It should NOT be set lower than the number of records currently in the table.

Note: Don't forget to click on "Save configuration" button to save your choices.

See http://drupal.org/node/164038 for more details.

================================================
OG Group Edit Page

There are also new settings which will appear on the "Edit" page of your groups.

  • Display the "Create Content" link: http://drupal.org/node/262938
  • Remove the default "Create" links: http://drupal.org/node/262938
  • Disallow Public Posts: http://drupal.org/node/247488
  • Location of group logo: http://drupal.org/node/256423
  • Registration code for new subscribers to this group.: http://drupal.org/node/217229
  • Comments

    MXT’s picture

    I'm using og_user_roles-6.x-4.0 and drupal-6.15, but the only settings I can view in OGUR settings are "assignable roles" and "default role assignments".

    Where are all the others ones described in this page? Surely I'm missing something... I've forgotten to setup something?

    tobylechien’s picture

    I thought I looked everywhere but I have the same problem as MXT above. Did we miss something?

    koosdewit’s picture

    I'm using
    Drupal 6.20
    OG 6.x-2.1
    OGUR 6.x-4.1

    I'm looking for the settings for registration codes. Where can I find them?
    I'm only able to choose assignable roles and default roles assignments.