Survey Authentication

[Michael Todd]

Hi,

I have two separate, but related questions that I hope someone can assist with. Both relate to Surveys:

Background

• We plan to survey users in the customer_contacts table for general feedback on our organisation (i.e., not task related) 
• Only a small percentage of the contacts in our table are registered for access to our CSM portal i.e., they have set up their credentials.
• We have created a dynamic recipient list on the survey to target contacts and email the survey to them
• The survey has generated a unique survey instance for each contact with a bespoke URL

My questions are:

1. Is it possible to allow a non-authenticated contact to take a private survey when they have the URL for their own instance, or do they always need to authenticate? Aware I can make the survey public but this creates a new instance against the 'guest' user - we would like to track response back to the contact.
2. If I make the survey private, when the contact clicks the URL they are bounced out to our SSO provider which is only used for employees. How do I force it to request local authentication for snc_external users?

Any help appreciated.

[GodOfWar]

1) The user needs the authentication for the private survey it's being addressed to a specific user.

2) You really need to authorized every user of this private survey. It's always directed to a specific user.

Don't hesitate to click the Helpful button below if it helps.

[Michael Todd]

Re question 2, my issue is that the user is requested to authenticate via SSO, which we don't use for clients. It should take them to the CSM sign in page and ask for credentials but it's bouncing out to Azure AD.

[GodOfWar]

It's either you register your clients like an internal user or set the survey to public without knowing from who answered those surveys.

[deepakgarg]

@Michael Todd Did you try using the `createAssessments` API to create on-demand surveys for specific users? Using this, you can create specific survey instances assigned to specific users, which in turn can be used to trigger specific emails for each user for their specific instance.

For external users to have the access to the survey instances, you will need to make the survey public, but since you are sending specific instances already assigned to those users, you will still have the reference to who the survey is assigned, instead of `guest`.

Only catch is, since the survey is public & we are sending specific instance urls, if the user shares the survey taking link  with anyone else, then they will also be able to take that survey on behalf of them, which is obvious, as we are not asking them to login.