HomeDev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunityDoc feedbackLog In
GitHubNuGetDev CommunityDoc feedback


649


## Requirements

  • No additional license fee.

  • An Optimizely Content Management System (CMS) or Optimizely Customized Commerce installation.

  • Accounts for the social channels to be used.

  • See [Add-ons platform compatibility](🔗) for package and version information. 

## Install Social Reach

These instructions apply to Social Reach for CMS version 7.5 and higher. To install Social Reach, you need a working site with CMS 7.5 or higher, with a valid license installed.

  • Versions 7.5 and higher are [installed through NuGet](🔗).

Social Reach contains the following:

  • **Files** – The installed files are located under **Modules/Social**.

  • **Virtual roles** – The virtual roles **SocialEditors** and **SocialAdmins** are included in the default configuration. You can change the access rights as described in [Changing Default Access Rights](🔗).

  • **Providers** – The social channels are created based on a provider model. Available example providers are **Twitter**, **LinkedIn** and **Facebook**. The shortening service is also based on a provider model. The available shortening service provider is **bit.ly**. Providers are registered in web.config with a default configuration to use Optimizely's accounts as follows:



## Change default access rights

You can change which roles that have access to the different views in Optimizely Social Reach by using the virtual roles **SocialEditors** and **SocialAdmins** through the **<location>** section in _episerverframework.config_ and _web.config_ for the following elements:

`<location path="/modules/EPiServer.Social">`

and

`<location path="/modules/EPiServer.Social/Settings">`

## How the Social Reach App gadget constructs the auto-input message

This section explains how the Social Reach App gadget constructs the auto-input message. The message is created when a Social Reach user is posting a message and selects a link. Social Reach then populates the message's **Name** and **Message** fields by extracting information from the link per the following logic. The user can accept the values or edit them before sending the message.

  1. The widget gets the `contentlink` from EditView and sends it to the OutReach panel.

  2. In the OutReach panel, the widget extracts `contentData` from the `contentLink`.

  3. Using the following components, the widget populates the OutReach UI components.

  • `message.Name = contentData.Name`

  • `message.MessageBody = contentData\["MetaDescription"\]` or `"MainBody"` or `"Info\_Description"` (in priority order).

**Additional explanation of MessageBody**

OutReach uses the `contentData` meta-description property if it exists.     If that property has no value, OutReach uses the `MainBody` property.          If that property has no value, OutReach uses the `Info\_Description` property.

See also: [Social Reach Add-on](🔗)