SuzieH
Khoros Alumni (Retired)
Joined 12 years ago
User Profile
User Widgets
Contributions
Farewell Dev Community. It's been a wonderful journey!
Tomorrow (March 31) will be my last day at Khoros as Principal Content Designer and Developer Experience Program Manager. I'll be just shy of my 9th anniversary at the company. I'm taking some time to recharge and relax. Before I go, I want to give a big thank you to the entire Developer Community. Hunting down answers to questions in the Dev Discussion Forum helped me learn about Khoros products at a deeper level and make lasting cross-functional team connections. Hearing about your use cases, and frankly, feeling your pain and frustration as you muddled through development issues informed how the dev docs evolved. When I came to Khoros (then Lithium) in 2013, Developer Documentation consisted of the Community API v1, FreeMarker guides, and a handful of knowledge base articles. I'm proud to have overseen the creation of developer.khoros.com and watch the developer documentation grow from Community API v1, FreeMarker, and a handful of knowledge base articles to include the Care, Automation Framework, Brand Messenger, Community v2, Marketing, and Flow APIs along with multiple SDKs and developer tools. RyanPijoined the team two years ago andJavidHjoined a year later. I'm leaving Dev Docs in good hands and I know that the Dev Experience will continue to mature. Thank you all. Suzie Hopkins (SuzieH)Re: How We Built It: Private Member Info component
Hialexislbrown. This is what I heard back from the engineer who wrote this customization. So for this, I would suggest creating a new role (<special_member>) and assign to all those 40 members. And we will keep a check that members with this role can only see each other's info. When a member (out of these 40) wants to see info of any other community member would not be able to see it. There could be a separate condition to check whether a community (staff) member can see info of these 40 members as well if you wanted to allow for certain employees of your company to see the private info for the 40 partner members.Re: How We Built It: Private Member Info component
alexislbrownThat is correct. As the code is presented here,the 40 Partner users would then be able to see not only each other's information but all users. I'm going to reach out to the Atlas engineer who built this to see whether he can suggest a tweak in the logic to make the component work as you'd like it to. It might take a few days to get a response back.Re: How We Built It: Private Member Info component
Hialexislbrown. I'm not sure I'm interpreting your question correctly. Here's how I would explain it -- let me know if this helps. Rather than saying that the component is "assigned to certain user roles," I would say that the component only renders for users with a certain role assigned (in this case, the Staff role). Regardless of the role(s) assigned to the user whose profile page is being viewed, any user with the Staff role will be able to see the personal information component. Does that answer your question?
