@sarajaynerowWe are facing exactly the same issue and we are using the manual workaround currently i.e. multiple publishing to change links. I had users complaining about not able to access a link and when I tried login as user, it works perfectly fine too. This is very strange and unexpected behavior which leads to confusions and unprofessional work practices. We have specific teams that only send out updates to customers and won't understand changing of these links completely. ... View more

@jamiemccardleSeconded. I would recommend the same. @CarolineS I think using roles or aliases with specific responsibilities is a good practice in any such scenario. Aliases work best to hide any internal changes (such as changed posts or employees). E.g. A helpdesk alias who does not have any front-end work in community but it is used by all helpdesk team who onboard employees and provide community access too. This can also be achieved by assigning a role which has this capabilities to the helpdesk users. Solution (until Khoros provides solution in roadmap): Create a user "Marketing Leader" with same posting credentials as the marketing leader's. Work with your IT and create an alias email ID (e.g. ml_community@org.com) that can skip SSO or has a backdoor entry. Share these credentials with anyone who you want to have the abilities. The CEO user is also a good idea. What I believe is SSO is a vast enough technology to accommodate your requirements. However, if this is handled by your IT, it is only possible if either an IT associate is your friend or the IT team is extremely co-operative 😉 ... View more

Thank you @karolinalinda for helping out. However, my concern is not about admins or moderators. We too have enabled this permission for looking up internally and that is a must feature for admins/mods as email IDs mere serve better associations with individuals.   @MarkAtTruthThank you, I agree with all that you mentioned. You have helped out with all possible scenarios. However, I do have a use case here: "x@abc.com is our external user in our community and so are y@abc.com and z@abc.com. All employees with abc.com can lookup each other's email IDs in their internal directory. There is a post in community where x wants to @ mention y and z but it is impossible without knowing their usernames." Here, I want to emphasize the fact that the user does not want to find people but he already knows who to tag. Only problem is he does not know the usernames. Here, allowing a user to see if there is an exact match to looked up email is reasonable option to provide. Please share your opinion. ... View more