How to make Display Name Permission controlled?

Support

Support
A public community space for Developers, IT Professionals, Architects, and System Administrators to engage and help each other, share knowledge and best practices, find product documentation and Q&A, and discuss technology oriented topics.

How to make Display Name Permission controlled?

This question is answered

Seeing real names on posts greatly improves the quality of discourse in a community.

But members are very reluctant to see their real names exposed to search engines etc.

There is only a global site setting for Display Name to be real name or username. It needs to be Permission controlled so signed-in users can see real names while acting in the security that their identity is not open on the internet. How can this be achieved?

Verified Answer
  • There is not currently platform support around changing what a given User (A)'s DisplayName property would return to another User (B) based on permission.

    The closest workaround might be to modify widgets that refer to a user's DisplayName to instead implement their own logic for what value to render. For example, a widget could check to see if the accessing user is anonymous (or perhaps not friends with the user), and if so, render a Username instead of DisplayName. This would not truly change what information is private though, since User A's DisplayName value would still be available to User B via REST.

All Replies
  • We don't actually collect "Real" names Out of the box.  There is a display name option that is completely user defined and does not have to a real name.  If you allow display names they are shown in place of a user name if one is set.  If a user doesn't want to use a display name then they should remove it from their profile.

    But again, this can be anything, not necessarily a real name

  • Yes, sorry, I mean you have a global site selection to control whether to show DisplayName or UserName.

    But that DisplayName is the same to all users. We would like to have Permission-control of who gets to see the DisplayName. That way they can show a more personal face to trusted users.

  • Right, but that DisplayName is the same to all users. We would like to have Permission-control of who gets to see the DisplayName. That way they can show a more personal face to trusted users.

    On Dec 16, 2013, at 10:48 AM, Patrick Mason <bounce-pmason@communities.telligent.com> wrote:

    We don't actually collect "Real" names Out of the box.  There is a display name option that is completely user defined and does not have to a real name.  If you allow display names they are shown in place of a user name if one is set.  If a user doesn't want to use a display name then they should remove it from their profile.

    But again, this can be anything, not necessarily a real name

  • There is not currently platform support around changing what a given User (A)'s DisplayName property would return to another User (B) based on permission.

    The closest workaround might be to modify widgets that refer to a user's DisplayName to instead implement their own logic for what value to render. For example, a widget could check to see if the accessing user is anonymous (or perhaps not friends with the user), and if so, render a Username instead of DisplayName. This would not truly change what information is private though, since User A's DisplayName value would still be available to User B via REST.

  • Michael Monteleone

    There is not currently platform support around changing what a given User (A)'s DisplayName property would return to another User (B) based on permission.

    OK, consider this a feature request to make the 'show username or show DisplayName' selection permission based rather than site-wide.

  • Thanks! We've captured this request.

  • Hi Guys,

    Strangely we had this request from a client also last week. Pretty much the same thing but an added level of complexity to have different 'Display Names' show against posts in different groups as well as to different users/roles.

    So I guess what we need is some kind of event like Pre_Render_Displayname() that we can hook into and carry out logic on in a plugin that will effect all widgets that show a users display name.

    We can then put in any logic we wish there. This would be good for connecting to 3rd party systems to get a users 'Real Name' or things here instead too if  that was needed.

    Also using this we could make users posts anonymous with logic too if required. This is something we have been asked to do before: make it anonymous on the front-end but track the real user in the back-end.

    is this not possible with event plugins in 7.6 or the up-coming 8.0 at all?

    thanks

    Adam

  • We'd also be interested in something along those lines, but would like it applied to all profile fields as well.

  • Great feedback. Capturing this as well.

    Thanks

  • It occurs to me that even without a platform event, you could still currently write your own Velocity extension plugin that could perform the same custom logic, though requiring a slight change in widgets...

    $myCustomExtension.EffectiveDisplayNameFor($user.Id)

  • Luke D

    We'd also be interested in something along those lines, but would like it applied to all profile fields as well.

    We already have that through a Couto Solutions plug-in (I think it is Directory Connect) that lets us apply view permissions individually to User Profile fields (as well as create custom Member Search widgets based on global Role of the searcher). However, without rewriting all the widgets that display usernames, we cannot use those permissions to selectively display either the Username or the user's true name.