Bias towards user's Full names

One challenge of this: When your community is public, full names would be exposed. Many users may be uncomfortable with that. 

Here’s a suggestion I submitted recently related to it: 

• Expanded Permissions for the Profile Module or Showing/Hiding Profile Fields Open
• 17 Votes

I agree with @DannyPancratz. Not every type of community is a B2B community where a real name policy is considered standard, like on LinkedIn or professional collaboration platforms (Slack, Teams, etc.). A public B2C community, for example, couldn’t survive (in my opinion) with a forced real name approach.

Learning something new, and tbh @DannyPancratz, and @bjoern_schulze  “Full names exposed” dont sound alarming to me, rather encrypting Full names to usernames, does.

As you point out LinkedIn and other platforms we model on… here’s a couple of Huge, thriving SAAS b2b community examples

community.bmc.com

community.sap.com

ddpancratz wrote:

One challenge of this: When your community is public, full names would be exposed. Many users may be uncomfortable with that. 

Here’s a suggestion I submitted recently related to it: 

• Expanded Permissions for the Profile Module or Showing/Hiding Profile Fields Open
• 17 Votes

 

I like your idea @DannyPancratz and voted. It’s also my intent to drive towards a People’s directory so that your community is also your SME dB.

My contribution here is - whatever you do with identities, make it a positive action to select an option and never a default. Communities are so wildly different in their needs when it comes to identities. What helps one succeed would utterly destroy another. Mine, for example, thrives on anonymity.

Can't debate that @Onomatopoeia  … btw, did you upVote ddpancatraz’s idea? (woops sorry couldnt tell the full name )