Yes, the SSO setup involves additional service costs (enablement cost).

Yes, it works the same for Advocacy and all the other modules. However, it does cost extra to set up and configure the necessary services to extend the solution to Advocacy.

Yes, you can use both SSO or Social Sign at the same time.

No, this is currently not possible.

Depending on what information is sent to Sprinklr in the SAML attributes, we can capture the information sent to us and map it to screener questions.

Yes, we have the ability to capture the information from SSO and the remaining can be completed by the user manually.

Yes, we can send a welcome email once the user is approved.

No, Sprinklr only supports SP (Service Provider Initiated) SSO. 

Yes, the awards and points are lost in the switching process, but the profiles of the user are stitched once they log in with SSO and connect a social account associated with their social sign-on profile. The Advocacy Admin can also manually award points to the user.

Once the user has left the company, their SSO credentials will stop working so they won’t be able to access the site. If required, the admin can set up a rule that will revoke users’ access if they haven’t logged in for a set period of time.

Yes, the posts will be published unless the user has manually removed his/her social channels. if the admin changes the user’s status to Rejected, then a rule will stop the scheduled posts from being sent. Admin will have to manually change their status though. It can’t be done automatically.

Yes, SSO can lead to auto-approval of Advocacy members if the Auto Approval community rule is switched on.

Ask the slack channel #spr-advocacy, someone will help you out shortly.