In Sitecore, a user must be associated with one or more Sitecore roles. S4S has a way to map a Salesforce Contact (or Lead) to Sitecore so the individual has one or more roles (Multi-Roles). The primary way to do this is called Multi-Role: Sitecore role(s) are selected from within the Contact or Lead record. The role selections can be made using a Salesforce Picklist, Multi-Select Picklist or checkboxes.
About Single-Role and Other Role Mapping Options
S4S provides an alternative to Multi-Role called Single-Role. This approach maps Sitecore roles to Salesforce Account names so any contacts that belong to an Account will appear in Sitecore as belonging to a Sitecore role with the Account name. If neither Single-Role or Multi-Role works for your business requirement, you can dispense with overriding the role provider and use a Sitecore role but still have the membership and profile data in Salesforce. More options that involve some development effort are also possible with S4S.
Configuring Multi-Role
This section covers the additional steps to set up Multi-Role role support for all Salesforce editions. The Multi-Role package requires a custom field to be added which will map a Contact and/or a Lead (representing users in Sitecore) to Sitecore role/roles. This can be done via a checkbox, picklist or multi-select picklist.
...
Figure 18: Multi-Role using checkboxes
Password Encryption
The password encryption checkbox is a way for Sitecore authentication to determine if the supplied password is encrypted or not. In Salesforce Enterprise and above editions the password will be encrypted when saving the Contact or Lead automatically. In all other Salesforce editions, the Contact or Lead Password will be encrypted after the first successful login into Sitecore.
Next Step
Changing the Sitecore Username (Optional) (Pre-Sitecore 9)
Steps
| Child pages (Children Display) | ||||||
|---|---|---|---|---|---|---|
|