ContributionsMost RecentMost LikesSolutionsRe: Permissions do not appear to be working properly Is there a way for the subscription button to work if they haven't verified their email? We want this to be easy and to reduce the barriers to leveraging this - are we able to tweak the way the subscription button works so that they can see it? Re: Permissions do not appear to be working properly I checked, at least one is verified, so that's not the issue. Re: Add link to case back to support emails Yes! It was the thing I always clicked, now I have to navigate in with many, many more clicks. Hoping it gets changed back. Re: Super basic - list of API calls It may be we have to be friends. Let me try that! Sbrown works as you are in the thread already, I'll try to @mention you somewhere else to see if that works, pre and post friending you. Re: Super basic - list of API calls Thanks Parshant! Angela, I tried to @mention you but I'm not finding @angelalau in the Lithosphere. I wanted to highlight these resources to you and Andrae so you can look at them. If you can see this site you have customer access, and you'll need to get Andrae to sign up and then request customer access from communityhelp@lithium.com Thanks! Super basic - list of API calls Hello all, We are new lithium customers, migrating from JX and working through our roll out of our new community on Lithium. We've seen some items that pull dynamic community data into our pages. Example: Welcome <username>! Or a customer component that pulls in a specific node name, # of posts per node, node description or Title text. We want flexibility to create these ourselves, but understand they are API calls. I am looking for a list of the things we could pull into our components. So what code do we use to pull "username" into a customer component. And what about node name, node title, node, # of posts, node # of solutions? I am sure this is a really basic question, but can anyone point me to a library of 'stuff you can pull in' that we can work with? FYI nicoleguzzo