Group FAQs

  1. What is Group Discoverability?
  2. How do I make a visible group hidden? And vice-versa?
  3. What is Group Membership Access?
  4. How to Customize a Group?
  5. What are Group Plugin Access Levels?
  6. How are groups managed?
  7. How do I leave a group?
  8. How do I delete a group?
  9. How do we keep track of the invitations we've sent out?
  10. How do we cancel a group invitation?
  11. How do I accept a group invitation?

What is Group Discoverability?

All groups have an overall discoverability setting of either visible or hidden. This determines whether or not the group appears in searches or by browsing groups. Visible means the group can be found by anyone, hidden means the reverse. Hidden groups are not listed anywhere on the site.

The group mangers have the ability to update the group discoverability which can be found by editing the group.

Group managers can also set access restrictions on each group plugin (members, messages, wiki, etc) to limit access to that specific plugin's content. Information about group access levels can be found below.

How do I make a visible group hidden? And vice-versa?

If you are an administrator, go to your Groups page and select "Show Manager Controls" under your title (group manager) at the right. Select "Edit Group" from the drop down menu. Go to "Discoverability Settings" toward the bottom. Choose the "hidden" option and click save.

Instructions are the same for making a hidden group visible except choose "visible" instead.

What is Group Membership Access?

Group membership allows for groups to restrict access for new members. There are four settings for group membership: Anyone or Open, Restricted, Invite Only, and Closed.

  1. Anyone or Open means that if a registered hub member comes to you group they will be able to click a button to join the group without a group manager having to approve.
  2. Restricted means that the user will have to enter a reason for wanting to join the group and a group manager must approve their request before they will be granted access to the group.
  3. Invite Only means that the user will not be able to join the group unless they have been sent a group invite from one of the group managers.
  4. Closed simply means that membership cannot be modified.

The group managers have the ability to update the group membership access, which can be found by editing the group.

How to Customize a Group?

Groups allow for customization including adding a group logo, customizing the group home or main page (instead of using default group description and random selection of group members), setting group plugin access levels (discussed below), and the ability to add extra custom group pages.

All group managers can customize any of these items through the group customization interface.

What are Group Plugin Access Levels?

Group Plugin Access Levels allow for groups to set access levels for each plugin (members, messages, wiki, etc) individually. The different access levels are: Any HUB Visitor, Registered HUB Members, Group Members, and Disabled or Off.

  1. Any HUB Visitor means that if a guest (not logged in user) comes to the group plugin they will be granted access to view the plugin but not allowed to perform any actions (add, edit, delete, etc) within the plugin.
  2. Registered HUB Members means that if a HUB member (not a member of the group) comes to the group plugin they will be granted access to view the plugin but not allowed to perform any actions (add, edit, delete, etc) within the plugin. Guest users will not be granted access to view the plugin.
  3. Group Members means that is a group member comes to the group plugin they will granted access to view the plugin and perform any actions that group members are allowed to perform. Guest users and Registered HUB users will not be granted access to the plugin.
  4. Disabled or Off means that no one will be granted access to the plugin.

All group managers have the ability to update the group plugin access levels, which can be found through the group customization interface.

How are groups managed?

When you create a group, you are automatically made its first manager. As manager, you can also promote members to help you run the group.

A group manager can:

  1. Create group participation rules
  2. Promote/demote members and approve/deny membership requests.
  3. Modify information about the group
    • Create or change the group name
    • Create or change the group description
    • Associate the group with an external URL
    • Determine whether or not your group wiki pages, resources, and discussion topics can be viewed by non-members.
    • Moderate group discussions

There's no maximum limit on the number of managers a group can have, but a group must have at least one manager at all times.

You can read about keeping your group happy on the Tips for Running Your Group page.

How do I leave a group?

Go to your group page and click on "Show Member Controls" under "Group Member" on the right side. Click on "Cancel Membership". Select OK to confirm the cancellation. If you would like to rejoin the group at a later date, please request group membership again.

How do I delete a group?

The only way to delete a group is to leave the group as the last remaining member. A group can't be deleted if it has more than one member.

How do we keep track of the invitations we've sent out?

In the Invitees tab found under Members inside your group, you can keep track of whom you have sent an invitation to. You will find an symbol next to an invitees email address if he/she does not have an account on the hub yet. For those with hub accounts, you will see their profile picture next to their name.

How do we cancel a group invitation?

In the Invitees tab found under Members inside your group, you can keep track of whom you have sent an invitation to. Cancel the invitation by clicking the red (U) icon next to a persons name.

How do I accept a group invitation?

Click on accept in the "My Groups" section of your "My HUB" page or click on the accept link in the invitation message.

Back to Top Index

Last Modified: Wednesday, May 08, 2024 @ 5:41pm

Debug Console

Close4 MBRequestSessionTimelineDatabase16Events15
$_GET
Array( ) Array(

)
$_POST
Array( ) Array(

)
$_COOKIE
Array( ) Array(

)
$_SERVER
Array( TEMP => /var/www/tmp, TMPDIR => /var/www/tmp, TMP => /var/www/tmp, PATH => /usr/lo... Array(
TEMP => /var/www/tmp,
TMPDIR => /var/www/tmp,
TMP => /var/www/tmp,
PATH => /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin,
USER => apache,
HOME => /var/www,
FCGI_ROLE => RESPONDER,
REDIRECT_HTTP_AUTHORIZATION => ,
REDIRECT_UNIQUE_ID => Z0L3XzukL5EHpxcmVG3k7wAAAAg,
REDIRECT_SCRIPT_URL => /help/groups/faqs,
REDIRECT_SCRIPT_URI => https://shunko.aws.hubzero.org/help/groups/faqs,
REDIRECT_HTTPS => on,
REDIRECT_SSL_TLS_SNI => shunko.aws.hubzero.org,
REDIRECT_STATUS => 200,
HTTP_AUTHORIZATION => ,
UNIQUE_ID => Z0L3XzukL5EHpxcmVG3k7wAAAAg,
SCRIPT_URL => /help/groups/faqs,
SCRIPT_URI => https://shunko.aws.hubzero.org/help/groups/faqs,
HTTPS => on,
SSL_TLS_SNI => shunko.aws.hubzero.org,
HTTP_ACCEPT => */*,
HTTP_USER_AGENT => Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com),
HTTP_ACCEPT_ENCODING => gzip, br, zstd, deflate,
HTTP_HOST => shunko.aws.hubzero.org,
SERVER_SIGNATURE => ,
SERVER_SOFTWARE => Apache,
SERVER_NAME => shunko.aws.hubzero.org,
SERVER_ADDR => 10.68.128.8,
SERVER_PORT => 443,
REMOTE_ADDR => 3.145.66.104,
DOCUMENT_ROOT => /var/www/shunko,
REQUEST_SCHEME => https,
CONTEXT_PREFIX => ,
CONTEXT_DOCUMENT_ROOT => /var/www/shunko,
SERVER_ADMIN => root@localhost,
SCRIPT_FILENAME => /var/www/shunko/index.php,
REMOTE_PORT => 27751,
REDIRECT_URL => /help/groups/faqs,
GATEWAY_INTERFACE => CGI/1.1,
SERVER_PROTOCOL => HTTP/1.1,
REQUEST_METHOD => GET,
QUERY_STRING => ,
REQUEST_URI => /help/groups/faqs,
SCRIPT_NAME => /index.php,
PHP_SELF => /index.php,
REQUEST_TIME_FLOAT => 1732441951.9974,
REQUEST_TIME => 1732441951
)
separator ⇒ .
orderBy ⇒ id
orderDir ⇒ asc
1 ⇒ registerIP
2 ⇒ access
always ⇒
renew ⇒
tracker.sid ⇒ c440e7a258f19a4ddf930b1439cb291f
tracker.ssid ⇒ c440e7a258f19a4ddf930b1439cb291f
tracker.rsid ⇒ c440e7a258f19a4ddf930b1439cb291f
  • site 0.030 seconds (+0.030); 3.50 MB (+3.500) - afterInitialise
  • site 0.059 seconds (+0.029); 4.25 MB (+0.750) - afterRoute
  • site 0.065 seconds (+0.006); 4.50 MB (+0.250) - afterDispatch
  • site 0.069 seconds (+0.004); 4.50 MB (0.000) - onAfterRender
  • site 0.072 seconds (+0.003); 4.50 MB (0.000) - sessionStore
4 MB

16 Queries Logged: 0.0082895755767822 seconds

  1. SELECT data
      FROM `jos_session`
      WHERE `session_id` = '9f4a14e4482f79e002ffd9da27089ee3'
  2. DELETE
      FROM `jos_session`
      WHERE `session_id` = '9f4a14e4482f79e002ffd9da27089ee3'
  3. SELECT data
      FROM `jos_session`
      WHERE `session_id` = 'c440e7a258f19a4ddf930b1439cb291f'
  4. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_languages'
  5. SELECT session_id
      FROM `jos_session`
      WHERE `session_id` = 'c440e7a258f19a4ddf930b1439cb291f'
      LIMIT 1
  6. INSERT INTO `jos_session` (`session_id`,`client_id`,`time`,`ip`)
      VALUES ('c440e7a258f19a4ddf930b1439cb291f','0','1732441952','3.145.66.104')
  7. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_members'
  8. SELECT b.id, b.title
      FROM `jos_usergroups` AS `a`
      LEFT JOIN jos_usergroups AS b
      ON b.lft <= a.lft
      AND b.rgt >= a.rgt
      WHERE `a`.`id` = '1'
  9. SELECT *
      FROM `jos_viewlevels`
  10. SELECT folder AS type,element AS name,protected,params
      FROM `jos_extensions`
      WHERE `enabled` >= '1'
      AND `type` = 'plugin'
      AND `state` >= '0'
      AND `access` IN ('1','1','4')
      ORDER BY `ordering` ASC
  11. SELECT m.id,m.menutype,m.title,m.alias,m.note,m.path AS route,m.link,m.type,m.level,m.language,m.browserNav,m.access,m.params,m.home,m.img,m.template_style_id,m.component_id,m.parent_id,e.element AS component
      FROM `jos_menu` AS `m`
      LEFT JOIN jos_extensions AS e
      ON e.extension_id = m.component_id
      WHERE `m`.`published` = '1'
      AND `m`.`parent_id` > '0'
      AND `m`.`client_id` = '0'
      ORDER BY `m`.`lft` ASC
  12. SELECT con.`id`
      FROM `jos_content` AS con
      LEFT JOIN `jos_categories` AS cat
      ON con.catid = cat.id
      WHERE con.state=1
      AND con.`alias` = 'faqs'
      AND cat.`path` = 'help/groups'
  13. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_help'
  14. SELECT jos_template_styles.id,jos_template_styles.home,jos_template_styles.template,jos_template_styles.params,jos_extensions.protected
      FROM `jos_template_styles`
      INNER JOIN jos_extensions
      ON jos_extensions.element = jos_template_styles.template
      WHERE `jos_template_styles`.`client_id` = '0'
      AND `jos_extensions`.`enabled` = '1'
      AND `jos_extensions`.`type` = 'template'
      AND jos_extensions.`client_id` = `jos_template_styles`.`client_id`
      ORDER BY `home` DESC
  15. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_groups'
  16. UPDATE `jos_session`
      SET `data` = '__default|a:9:{s:15:\"session.counter\";i:1;s:19:\"session.timer.start\";i:1732441952;s:18:\"session.timer.last\";i:1732441952;s:17:\"session.timer.now\";i:1732441952;s:8:\"registry\";O:23:\"Hubzero\\Config\\Registry\":2:{s:7:\"\0*\0data\";O:8:\"stdClass\":1:{s:1:\"0\";s:7:\"session\";}s:9:\"separator\";s:1:\".\";}s:4:\"user\";C:17:\"Hubzero\\User\\User\":22:{a:1:{s:5:\"guest\";b:1;}}s:11:\"tracker.sid\";s:32:\"c440e7a258f19a4ddf930b1439cb291f\";s:12:\"tracker.ssid\";s:32:\"c440e7a258f19a4ddf930b1439cb291f\";s:12:\"tracker.rsid\";s:32:\"c440e7a258f19a4ddf930b1439cb291f\";}',`time` = '1732441952',`ip` = '3.145.66.104'
      WHERE `session_id` = 'c440e7a258f19a4ddf930b1439cb291f'
  • onAfterInitialise — Method — plgSystemP3p::onAfterInitialise → /core/plugins/system/p3p/p3p.php:21
  • onAfterInitialise — Method — plgSystemRemember::onAfterInitialise → /core/plugins/system/remember/remember.php:20
  • onAfterInitialise — Method — plgSystemHubzero::onAfterInitialise → /core/plugins/system/hubzero/hubzero.php:21
  • onAfterInitialise — Method — plgSystemXFeed::onAfterInitialise → /core/plugins/system/xfeed/xfeed.php:21
  • onAfterInitialise — Method — plgSystemSupergroup::onAfterInitialise → /core/plugins/system/supergroup/supergroup.php:113
  • onAfterRoute — Method — plgSystemJquery::onAfterRoute → /core/plugins/system/jquery/jquery.php:21
  • onAfterRoute — Method — plgSystemSpamjail::onAfterRoute → /core/plugins/system/spamjail/spamjail.php:21
  • onAfterRoute — Method — plgSystemIncomplete::onAfterRoute → /core/plugins/system/incomplete/incomplete.php:21
  • onAfterRoute — Method — plgSystemUnconfirmed::onAfterRoute → /core/plugins/system/unconfirmed/unconfirmed.php:21
  • onAfterRoute — Method — plgSystemUnapproved::onAfterRoute → /core/plugins/system/unapproved/unapproved.php:21
  • onAfterRoute — Method — plgSystemPassword::onAfterRoute → /core/plugins/system/password/password.php:21
  • onAfterDispatch — Method — plgSystemMobile::onAfterDispatch → /core/plugins/system/mobile/mobile.php:22
  • onAfterDispatch — Method — plgSystemDebug::onAfterDispatch → /core/plugins/system/debug/debug.php:60
  • onAfterDispatch — Method — PlgSystemHighlight::onAfterDispatch → /core/plugins/system/highlight/highlight.php:25
  • onAfterRender — Method — plgSystemSef::onAfterRender → /core/plugins/system/sef/sef.php:21