Skip to main content
davetee
Helper ⭐️
Mar 14, 2022 8:46 PM UTC
Open

Support for passing custom fields in through SSO

Related products:CC Customization

We could simplify our new user registration page if Insided supported custom fields via SSO - specifically SAML.

 

On the new community user registration form, we currently ask for the first name, last name, title, and company. We have all that data in the SSO identity provider and that’s the system of record where the data will most likely be accurate.

 

Fields we would like to populate in the Insided user profile via SSO include:

  • first name
  • last name
  • job title
  • company name
  • CSM ID assigned to the user
  • unique customer ID

I would expect the same visibility controls applied to regular user profile fields.

7 replies

Sebastian
Helper ⭐️⭐️⭐️
Mar 28, 2022 3:42 PM UTC
Updated idea statusNew→Open
Translate
Sebastian
Helper ⭐️⭐️⭐️
Mar 28, 2022 3:43 PM UTC

Thanks for your idea @davetee! I’d love to hear more about your use cases for setting it up this way. What problem would this help you solve, and which opportunities would this open up for you?

Translate
davetee
daveteeAuthor
Helper ⭐️
Mar 28, 2022 8:56 PM UTC

Hi @Sebastian -

Passing custom fields in via SSO allows us to augment user profile information so we can streamline the user registration process by pre-populating the registration page with known fields. It also provides metadata for us to trigger events outside the community. We use our SaaS product to authenticate new users in the community. We need to have a single source of user account truth and that should be coming from our SaaS product platform.

 

Problem - We ask our community users for the same profile information they provided when registering for our product platform. This burden could deter new community member registration. It could also lead to incorrect profile data when the user updates their profile in our product, but not in the community.

 

What it opens up -

  • Easier user registration process (Fewer hurdles the better).
  • Correct user data across platforms for reporting.
  • User metadata that can help us route customer inquiries with Zapier (customer ID and CSM ID).

 

 

 

Translate
dandre
Contributor ⭐️⭐️⭐️⭐️⭐️
Apr 6, 2022 1:03 AM UTC

Love this idea

Translate
When things get tough, we ask, what is best for the customer?
Maayan K
Contributor ⭐️⭐️⭐️⭐️
Jul 14, 2022 2:16 PM UTC

yes please will improve flow immensely. 

 

Translate
In the sweet spot between Tech & Biz I ride
Contributor ⭐️
Oct 13, 2022 8:31 PM UTC

Agree with what has been said above. It would be very helpful for us to get customer data via SSO from our app. Not having that data is a problem, and forces us to use janky workarounds and additional API integrations to sync the data. 

Translate
Contributor ⭐️⭐️⭐️
Aug 22, 2023 10:12 PM UTC

YES PLEASE!! Most interested in first name, last name, company name -- will be so valuable to build a credible and easy to interact with community. A total game changer!!!

Translate