• All Files

Managing Communities

Managing Communities

AVAILABLE TO: Administrators only

A community is a collection of registered users that have access to a set of social features. When a Flare community is integrated with a Pulse system, users have access to the same type of community functions that one would find on a social media site.

You can manage communities using either the Pulse dashboard or the Flare interface (i.e., the Target Editor).

In the Pulse dashboard, the Administration > Settings menu command is available to members of the Administrators group. This gives you the ability to click Communities to view a list of the Flarecommunities that have been integrated with Pulse.

Managing a community means that you can add, delete, rename, or provide a published URL for that community. However, for best results, it is recommended that you always add, delete, or rename a Flare community using the Flare user interface, rather than using the Pulse dashboard (see Integrating Flare and Pulse).

ClosedHow to Manage Flare Communities From the Pulse Dashboard
  1. Log in to the Pulse dashboard using an account that is a member of the Administrators group.See Logging In to Pulse.
  2. Select Administration > Settings. The Settings page opens.

  1. Click Communities. The Communities page opens. This shows a list of all the communities that have been integrated with Pulse. A key is shown, along with the name of the community. This key is automatically created for you when you install the SQL Server Database.

  2. Make any necessary changes. If you want to provide a published URL for a community, in the Published Url field type the path to the folder containing your main landing page. Make sure you include http:// at the beginning of the URL.

    example

    Let's say you've generated a target called "FlareOutput" and you've uploaded the output so that users access it here: help.mycompany.com/FlareOutput/Default.htm. In that case, enter http://help.mycompany.com/FlareOutput in the Published Url field.

    Why is it a good idea to assign a URL path to a community? Because it allows topic feeds to open in context.

    example

    Let's say you have not provided a published URL for your community. You receive an email notification stating that a user has posted a comment in one of your topics. So you click the topic name link in the email notification to see the feed where the comment was posted. The feed opens in the dashboard view of Pulse, which shows only the feed and not the topic associated with it.

    On the other hand, let's say you provide a published URL to your community. In that case, when you click the topic link, the topic opens in the actual Flare output. You see both the topic and the Pulse feed below it, therefore giving context to the post.

  3. When you are finished, click Save Changes