Using the System tab, the Community Administrator is able to configure and customize the system to best meet the needs of the community.
System settings include the following options or information requirements:
Site Name: Administrators can define and change the name of the community.
Base URL: Administrators can change the base URL for custom notification emails so that any links back to the community point to the masked URL instead of the default URL. This will also be the Base URL for any widgets developed for the community. It is important to note, however, that working as the Base URL for widgets developed on the site will only work if the URL has been appropriately mapped to the community site. If the Base URL has not been mapped appropriately, any email sent from the system will have empty placeholders for the header images within the email, and widgets will fail. More information on mapping is available here.
From Address: Administrators may specify the email address from which all email notifications will arrive. Both the name and the email address may be customized. Community administrators need to work with their domain provider to add an SPF record in their DNS. This basically tells the recipient systems of the email (spam filters) who are looking up this info that it is okay to accept mail from the client's domain.
Time zone: The time zone an Administrator defines will drive the time for meetings and also make it possible for meetings that are saved to Microsoft Outlook to be saved in the proper time zone.
Custom Default URL: Administrators may specify an alternative page to be displayed for users who are not logged in to the community.
Custom Login URL: Administrators may specify an external login page that is not hosted within the community. Note: When a URL has been defined in this field, the standard login box will no longer be displayed within the %%NAV%% when pages are displayed prior to login.
Session Timeout: Administrators may specify the number of minutes a member can be inactive before being logged out. If not defined, the default is 20 minutes.
The following options or information requirements are available for the home page:
Home Page: Administrators may define which page a community member sees when logging into their community by accessing this setting in the Community Administration Dashboard (navigate to Community Administration Dashboard > System > System Settings).
If a customized home page is selected, the administrator needs to enter the appropriate HTML and update their navigation options. The administrator also has the option of using the News Feed or any other page as the community home page.
When Other is selected, the URL of the desired page must be defined.
The following options or information requirements are available for the iPhone app:
Enable iPhone native application: This feature can be turned off if your members should not be able to access the community via the iPhone App.
Display the iPhone app download page when browsing via the iPhone: When enabled, anyone accessing your community via the Web browser on their iPhone will be offered a link to the iTunes store where they can download the iPhone App.
Require a signup code when members join the community via the iPhone: This feature ensures that only authorized individuals may join your community via the iPhone app. It is important to note that this feature requires the use of registration code invitations.
No signup code required - iPhone users can invite people to the community: This is the perfect option for public communities allowing anyone to join your community from the iPhone app while also providing members the opportunity to invite others to join.
The following additional options are available:
Enable RSS: This feature can be turned on or off. It is important to enable RSS feeds if widgets are used for the community.
Enable "Remember me": When enabled, and if the user chooses this option under the login box, the user’s login credentials will be remembered until the cookie is deleted or until the user logs out of the community.
Enable Secure Sockets (SSL): This can be enabled for communities that require additional security. Please note that this option cannot be used when the site URL has been mapped to hide the hosting domain. Since the URL being displayed is not actually where the site is hosted, visitors will be presented a certificate warning.
Display the login box on all public pages: The login box will be displayed on all public pages of the system when the user is not logged in, unless this option is disabled.
Display the login box on the logged-out front page: To hide the login box from the front page, the administrator can uncheck this option. A link to a separate login page will need to be provided if the login box is removed from the front page of a community so that members can log in.
Automatically subscribe members to email notifications when joining a group: Checked by default, administrators have the option to uncheck this box in order to allow members to join groups without being automatically subscribed to the email notifications.
Administrators may configure and customize the sign up steps that the user takes to register for the community.
Administrators will find the Client ID and Passcode required for setting up Web services with their community site.
Administrators may set how members log into the community via many Authentication options.
Web designers may customize the templates and CSS classes used for all pages within their community.
Designers my customize the mobile-based and Web-based user experience independently. Telligent Express supports mobile customization especially for the Apple iPhone.
Administrators may set the visibility level of each of the sections within their community.
Administrators may use IP filtering to restrict access to the community.
Telligent Systems, Inc. ©2013, All Rights Reserved