Skip to main content

I’d like to see the search in Control > Users search not just for the username and email address but also other custom profile fields.

Currently we run into situations where we are trying to locate a particular community member. We may not have their username or email but do have their name or other custom profile field data and can’t use that currently to locate them. While I can get this with a user export, it’s a hassle to have to resort to that each time.

Hi @Scott Baldwin! Thanks for submitting the idea. I can definitely see how that would be a small improvement with huge value. I’ll take this into the team, and will leave the idea open to gather some more votes/input.

Updated idea statusNew→Open

A lot of discussion around this idea in the replies to this topic: 

Here are my two cents: 

The ideal: If it’s a profile field (custom or not), then it’s searchable. Most of these are going to be text fields (whether a text input or text of selectable options), so if there’s a way to search all of the text tied to profile fields, I’d recommend that. It would keep the flexibility of custom fields and make each custom field searchable. 

The pragmatic: There are probably 3-5 fields that people would really search by (listed below). Perhaps an analysis of custom profile fields could validate or prioritize.

  • First name
  • Last name
  • Company
  • Job Title
  • City/State/Country

For these, I’d recommend building standard (non-custom) fields that are 1.) still optional, but 2.) standard, and then 3.) fields that are included in search for user management. 

That’s probably the best way to get close to what we expect of table stakes search functionality and cover most use cases. 

 

Great idea, Scott. I’m glad you go this conversation started!

Terms & ConditionsCookie settings