When you set up your Telligent community, you need to ensure that its structure matches the needs of the members and can provide you with the information you need to understand usage and performance. Before you walk through these steps to configure your community, you must first install Telligent Community in your environment using the Installation Guide.

Bear in mind that after performing the operating in this section, you need to create groups and assign them applications as in the Group Owner's Guide. You can use the Community Management Guide to create (or change) membership and roles in the community.

License

A valid license is required to use any application running on the Telligent Evolution platform.

Once you've received your license file:

  1. Save the license file locally or to a networked drive.

  2. Navigate to Control Panel Dashboard > Site Administration > Manage Licenses.

  3. Click Browse...

  4. Select the license file you saved in step 1. The path to the file is displayed in the text field.

  5. Click Install. For your reference, we list the basic information about your license (name, email, company, installation date), the products installed and the license attributes. If your license has an expiration date, you'll see the expiration date for each product and warnings to renew your license as your expiration date nears. Contact Telligent Support with any licensing questions.


    To delete your license, click Delete (located under your license information). With no license, you will only be able to run Telligent Community locally.

top

Authentication

Telligent Community can be configured to handle membership in one of two ways:

  1. Define your own membership rules within the community with users authenticated through the standard ASP.NET Forms authentication.

  2. Use the security that is already part of another application in your environment for login, logout, and registration. This enables members of your community to log in once and gain access to all related systems without being prompted to log in or register multiple times. We offer three options for single sign-on authentication:

    1. Forms Authentication - Shared authentication with other Microsoft ASP.NET applications

    2. Cookie Authentication - Shared authentication with applications that don't use Microsoft ASP.NET (e.g., PHP, ColdFusion)

    3. Windows Authentication - Shared authentication within an internal environment using Windows Active Directory

top

People

If your community does not share authentication with other applications in your environment, when you first log into the community, it is initially configured to:

  1. Allow login by anyone who has an approved, registered user account.

  2. Allow visitors to the community to register with:

    • Username between 3 and 64 characters that can include only letters, numbers, underscores, dashes, at signs, and periods
    • Password with no restrictions on characters. Registered users can be reminded of their password via a link in an email sent to their registered email address.
    • Visitors are tracked via the CSAnonymous cookie and cannot view members' profiles.

    • A registered user:

      • Is identified by his/her display names (first and last names captured during profile creation)
      • Can upload a photo as his/her profile avatar or select from ten different preinstalled avatars
      • Can enter status messages
      • Receives a welcome message from the administrative user
      • Must include a request message when trying to add someone as a friend

    Regardless of how your site is configured, you can:

    You can customize any of these settings for your community:

    top

    Organization

    Groups define the areas of interest for your community and allow you to control the type of content and the access to that content for community members. You can define a group hierarchy with any number of groups and levels of subgroups. Groups can be one of five different types:

    • Joinless - Membership is not tracked and permissions are managed using site-level roles.
    • Public open - Everyone can see the group and all content and can join without approval.
    • Public closed - Everyone can see the group and all content, but must apply to join and be approved to become members.
    • Private listed - Only members can see the group and all content. Everyone can see just the group name and description must apply to join and be approved to become members.
    • Private unlisted - Only members know that the group exists and can see group and all content. All others must be invited to join and approved to become members.

    We provide two groups by default:

    Name Type Parent Description
    Site Root Joinless None Required group for all community sites as it provides the overarching parent group to which all other groups belong. You cannot delete this group.
    Administrators Private unlisted Site Root Group that includes two forums:
    • Reporting Forums to which all forum posts that have been reported as abuse are moved.
    • Deleted Posts to which all forum posts that have been deleted are moved.
    By default, the administrative user is group owner so is the only one who can see and access this group and its content. As an administrator, you may want to add any other administrators and/or moderators as members of this group as well so that deleted and reported posts are managed effectively.

    Groups can include zero or more of each application type (blog, wiki, forum, file gallery), depending on the requirements for each group. Read more about applications and the configuration options available.

    As an administrator, you can:

    top

    Content

    Content within your community is structured by application. We support four application types:  

    Name Description Typical uses
    Blog Short name for weblog. Location for an author or more than one author to write commentary on a specific topic or area of expertise. Readers of the content can typically comment on the content. Personal commentary, description of events, or showcase of a set files (e.g., graphics and/or video).
    Wiki
    Collection of pages that allow community members to edit the content and/or comment on the content. Revision history is captured and comparisons can be made between revisions. Help documentation, specifications, and other less temporal or non-temporal content.
    Forums
    Discussion and/or question and answer area with threads that contain posts that are either replies, suggested answers, or verified answers. Discussions among group members, bug reporting.
    File galleries Collection of files available for download and commenting. Image gallery, video demos, presentations, reporting spreadsheets.

    Applications can only exist within a group. We recommend that you DO NOT create applications under the Site Root group to ensure that community members can navigate easily to all applications and the content within those application include the correct permissions. When you create a new group, we create one of each application type automatically. You can then can remove any of these applications or add additional applications as necessary through group management.

    top