...
The Security Connector overrides the ASP.NET membership provider so user data is only stored in Salesforce but appears in Sitecore in the “Salesforce” domain. This is commonly called "a single source of truth". After installing the Security Connector it is possible to control the Sitecore user's membership information, rolesrole, and profiles profile from Salesforce. Note there are two ways The most common way to implement roles - choose only one:is called "Multi-role
...
" where fields in the Salesforce contact (or lead) record
...
specify the Sitecore role. One or more Sitecore roles have the same names as selections in a custom multi-pick list in the Salesforce contact (or lead)
...
.
...
Campaign Members as Sitecore Roles
Another option is to expose Salesforce Campaign Members as Sitecore users by setting up a separate domain for this provider. This functionality is provided for purposes such as reporting, emailing, etc and as such, these users are read only and are not used for authentication purposes.
Excluding Web Forms for Marketers
...