Skip to main content

Currently profile fields are pretty binary: 

  • Required or not
  • Visible or not
  • Part of registration or not

It’d be great to have an option for role-based profile fields that could be configured for only certain user roles (similar to category permissions)

Use cases: 

  • Staff-specific profile fields that could be completed
  • Superuser specific profile fields
  • Gamifying the profile, incentivizing users to achieve a certain rank (and then get an automated role) in order to highlight specific things on their profile

My use case: 

We are highlighting some community members in a marketing campaign with power user profiles, etc. I’d love to feature the link to post on the users’ profiles. However, creating a field for this URL link would create a profile field for all users. 

Another use case I’d explore: 

Allowing users with certifications or ranks to specify their area(s) of expertise. Rather than allowing anyone to claim expertise despite being brand new or not yet certified. 

If you like this idea, check out this one (although it’s been parked)

 

@DannyPancratz I’m guessing there was some sort of abuse of the link use in previous communities. Otherwise I cannot imagine the reason why this would be rejected. Nothing tricky about it. 
I’m surprised it hasn’t been enabled with a warning in Control…

Thanks for your idea @DannyPancratz! As we require new users to fill in the required (custom) profile fields when they sign up, have you got any ideas on how we could then motivate users to post-fill it after they get a certain role or rank? In the meantime, I’ll keep this idea open.

@SmartlyGreg I’ll check on the closed idea you mentioned. 

Updated idea statusNew→Open

As we require new users to fill in the required (custom) profile fields when they sign up, have you got any ideas on how we could then motivate users to post-fill it after they get a certain role or rank?

Good question. For my use case, these wouldn’t be required fields or shown upon a registration. So the tactics to get them filled could be up to the community manager. My approach like would be: 

  • A call to action when they receive the role/rank (perhaps in the automated message with the rank)
  • User exports to show if that field is empty or not
  • Outreach to those who hadn’t completed it yet
  • Consider awarding points (manually) as an incentive for those who complete it

For my use case, just having the field that Community Managers could edit for them in control would be valuable. I could do it for them no problem; the issue is that the profile field would apply to all users. 

Terms & ConditionsCookie settings