Skip to main content

Issue / Feature Request: Exclude "Website" field from Profile Completion percentage

Hi team,

I noticed an issue with the Profile Completion calculation (the "Complete your profile (X%)" banner).

Currently, members can only reach 100% and dismiss the completion reminder if they fill in the Website field in their profile.

My community is an academic platform for students (high school and university) who simply do not have a personal website. Because of this, they are permanently stuck at 90% completion and are constantly prompted to complete their profile with a field that does not apply to them.

Could you please consider:

  1. Allowing community administrators to choose which profile fields count towards the completion percentage (or exclude optional default fields like "Website url").
  2. Automatically excluding non-mandatory default fields (like Website or Social Links) from the 100% completion requirement if custom required fields are already filled.
  3. Providing an option in settings to disable unused default fields entirely.

This would make the onboarding and profile completion experience much smoother for non-business/non-corporate communities.

Thank you!

victim account

sorry i added this mistakely

Claudy Scoufy

You beat me to it; I was planning to make this request soon. Not everyone has a website, and some provide all sorts of random information... Very good suggestion! I hope Shahjahan JewelΒ and Tawsif Ahmed RiyadΒ see this πŸ™

arjun arjun

Great observation and recommendation. As much as your title point is significant, the points below that you have raised in your body have similar weight:

  1. Allowing community administrators to choose which profile fields count towards the completion percentage (or exclude optional default fields like "Website url").
  2. Automatically excluding non-mandatory default fields (like Website or Social Links) from the 100% completion requirement if custom required fields are already filled.
  3. Providing an option in settings to disable unused default fields entirely.

AndrΓ© GΓ³isΒ  Thanks for your suggestion. I’ve added this to our feature request list and shared it with the team for consideration.