Welcome, Guest Login
Higher Logic User Group Site Higher Logic User Group Site Higher Logic Support Center

Support and Documentation

Community Access Permissions

Last Updated: Feb 27, 2017 09:33AM EST

There are four primary "settings questions" for existing communities and their content.


1) Who can know the Community exists?

 

2) Who can join the Community?

 

3) Who can access Community content?

 

4) Who can create Community content?

 

Another question, "Who can create Communities of a given type?" is also relevant.

 

For any given Community the specific answers to all of these will be one or more Security Groups. A three-tiered permissions architecture for Communities and the products used by Communities establishes these permissions. These three tiers are


Community Type - Example: "Committees"

 

Community - Example: "Finance Committee"

 

Product - Example: "Finance Committee Discussion/eGroup"


The tiers of this architecture allow defaults to be established on the Community Type and Community levels.  These defaults can then be overridden as needed on the Community and product levels.  Admin pages have been established to allow the management of these three tiers.  It is on these pages – the Manage Community Types page, the Manage Community page, and Manage eGroup page – where the five settings questions are answered.

 

QUESTION 1: Who can know the Community exists?

Communities can be seen or hidden based on member flag, committee membership, or other factors.

Manage Community Types Page

The default is established in the Community Permissions area.  The selection area (a pulldown)  is labeled "Default View Permission".  There are five possible selections:

 

1) Invitation Only - Community Members and those invited to be Community Members

2) Members Only - those with a positive Member Flag (IsMembers) for the Organization. This does not refer to Community Member.

3) Authenticated - anyone logged in

4) Public - any user/visitor regardless of login status

*Note: “Invitation Only,” applies to both Member Created Communities and AMS-Integrated Communities. (Even though invitations are never allowable for AMS-based Communities).

Manage Community Page

The Manage Community Page will accept the "who can see" default set on the Manage Community Type page.  This can be overridden for a specific Community under "Who can View Your Community".  The five options are identical to those possible when setting the default. 


Important Notes:

  • The view permissions for the calendar and events are determined by the view permissions established here.  "Who can view your community" will determine who will see Community events. 
  • Not all View Permission and Join Permission pairs are logical.  Mutually-exclusive pairings may produce unintended results. For example, a Community with View Permission set to "Invitation Only" and join permission set to "My Contacts" will be seen and able to be joined by a contact.  

Manage eGroups Page

The Discussion and Library for the Community can be hidden from view based on security groups.  The top-most field of checkboxes on the Manage eGroups page is labeled "Security Groups: Allowed to View Name and Information".  Checking nothing will allow the permissions to defer to the defaults.  Checking one or more boxes will allow only those security groups checked to see the Discussion and the Library for this Community.

 

QUESTION 2: Who can join the Community?

Community membership ensures a user can see and post all content for that Community. 

Manage Community Types Page

The default is established in several inputs in the Community Permissions area.  These are determined on the Manage Community Types page and nowhere else. 

  1. Can join – allows members who qualify to join without invitation (yes/no)
  2. Can leave – allows members to leave of their own accord (yes/no)
  3. Can members invite others – allows members to invite their contacts to join (yes/no)
  4. Pulldown for "Default Join Permission" – establishes who can join.  "Members Only" refers to the member flag for organizational membership.  This is the primary "join" setting.


If Communities of this type are linked to the AMS the radio buttons for these settings will be grayed-out.  For AMS-based Communities "Who can join the Community" is always completely determined by the AMS.

 

QUESTION 3: Who can access Community content?

"Community Content" refers to Discussion/eGroup posts and Library Entries.   In most circumstances the "who can access" question could be rephrased as "who can read the Discussion/eGroup posts and Library Entries?"

Manage Community Types Page

The default as to whether Community Admins can download Community rosters is determined in the Community Features area.  Other content creation permissions are not addressed at the Community Type level. 

Manage Community Page

The Manage Community Page has no controls impacting the ability to create content, with two significant exceptions: 

  • The Discussion/eGroup, Library and Microsite for the Community can be deleted here.  Deleting the core products is never recommended, unless no content exists for them.  
  • The setting allowing Community members to create events is on the Manage Community page.

Edit Community Settings Page

"Community Content" refers to Discussion/eGroup posts and Library Entries.  All Community content is only available to members of the Community except when otherwise established on the Extended Attributes page.  Content posted to the Discussion and Library for a Community can be made accessible to non-community members based on security groups.  The middle field of checkboxes on the Extended Attributes page is labeled " Security Groups:  Allowed to View Content".  Checking nothing will maintain that only members of the Community can access Community content.  Checking one or more boxes will allow Community Members and those security groups checked to see the Discussion and the Library for this Community. 

 

QUESTION 4: Who can create Community content?

"Community Content" refers to Discussion/eGroup posts and Library Entries.   In most circumstances the "who can create" question can be reworded as "who can post new Discussion/eGroup messages and create new Library Entries?"

Manage Community Types Page

The default permission for Community event creation is determined at the Community Type level.  Who can create Community Events?  (Administrator/Administrator and community members).  This is the only Community content permission established on the Community Type level.

Manage Community Page

The Manage Community Page has no controls impacting the ability to create content. 

 

QUESTION 5: Who can create Communities of a given type?

Multiple Community Types with different "who can create" rules can be established. The creation of new Communities can be allowed for any logged-in user or reserved for Admins. 

Manage Community Types Page

The default is established in the Community Permissions area "Can Members Create" (yes/no).  This is determined on the Manage Community Types page and nowhere else.  If Communities of this type are linked to the AMS the radio buttons for this control will be grayed-out.  The products (Discussions, Resource Library, Calendar, Microsite) serving Communities of this type are determined in the Community Features area.

 

support@higherlogic.com
http://assets3.desk.com/
false
higherlogic
Loading
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
about
false
Invalid characters found
/customer/en/portal/articles/autocomplete