Supposed
Why I doubt there's much use for customer facing SSO. Using SSO to login into the app is crucial. It's part of a security posture, and technically since 2fa is not enforcable on your platform, It could potentially hinder ISO27001 certifications if used by a company. Using SSO alleviates this as the 2fa flow can be configured by the IdP
I'd separate this into SSO for Contributors and SSO for participants. For us, latter is not important because we would use Tally for customer-facing surveys. Former is definitely crucial since it helps us with the account management and secures the data of filled forms.
Hi Omer +1 for this feature request. Without SSO it's not possible to use it in organizations
Hi Omer, +1 for this feature request. Because there was nothing like this, I figured out a way of "authenticating" a form response by doing an email verification of the respondent. I wrote a medium article about this : https://medium.com/inside-42/validate-a-respondents-email-ad… It may not be useful for you if your form is confidential (the link remains public). Hope this helps!
CC: Filip Minev
Thanks a ton for the detailed request and kind words, Dawud! 🙏 Google SSO with domain restriction would definitely be a powerful way to control form access — we’ve noted it down. Really appreciate you taking the time to share this!