Podcast Episode 152: Episode 125: Security

Description

This episode of Rock Cast is all about security. We start off with a discussion of future analytics features in development which could replace basic Google Analytics, answer community questions about the v13 profile protection feature, and cover the safest methods to update your instance to the latest version.

Transcribed Content

This episode of Rockcast is brought to you by Rock partner Triumph Tech, a full service specialist partner. Rock partners provide crucial support for Spark Development Network and important services for the Rock community. Connect with Triumph Tech today at rockrms.com/partners. Hello, Rock Community. I'm Emily Forman, your host for the Rockcast podcast, all things Rock and Spark Development Network. And I have here Jon Edmiston and Nick Airdo, and we are going to talk Rock today. Let's start with where we are, what's been released so far and what that means. At this point, we have released version 13.2, and it's quieted down quite a bit. So 13.3 has a few tiny changes in it, but we don't have an ETA on 13.3. We'll just have to wait and see, kind of we always do. As more churches come on board Rock, they might uncover something that we haven't seen, and then we'll release 13.3. Great. And we're still trucking on a different type of release pattern in general, right? a little bit faster on our major releases. That was our That's the goal. That's the goal. Yeah. That is the goal. I think we're making good progress on that. I thought I had heard that. Great. Yeah. Good. Well, what else are we working on? Well, we are working on new features for 14 and that's making some good progress. So digital signatures is now done for workflows and it's nearly done for event registration. Coding process is done. Now we're just going through the QA and and a little bit of UI cleanup. So that's pretty good, big news. That's a very hard feature. So we're just doing some last minute kind of polishing on that feature. Moving on to the person profile redesign, which again is gonna be a little harder than it probably looks. It's not just about rearranging some CSS styles. It's a complete refresh of the person profile page. And I think right now we're just trying to understand how is the best way to roll that change out in a way that, I mean, it's a pretty disruptive change in a good way, but we know a lot of people have also customized their person profile pages. So it's a little hard to move all the cheese around and not upset anybody. So we're trying to think through on a strategy of that. We have some ideas, but definitely I think we want to also help people try to clean up some of their badges through that process. I think over the years, people's badge markups are quite different and distinct and trying to create some standards around that, I think would be helpful. So we have some work to do around that. Just trying to create maybe some guidelines for markup that will help us in the future if we ever wanna do something this again. But if you've created a lot of badges, you might put that in the back of your mind that you might have some work to do when fourteen rolls out to get your badges kind of reworking, trying to shrink maybe the overall size of each badge so people can fit a little bit more on there. It's kind of cool to see how many people have made custom badges. But I've also seen a lot of people who have had too many badges in the badge bar and if you start to shrink it down a bit, it has some responsive issues in their environments. We're trying to take all that into account. Also looking at the personalization and we're doing a lot of work on that, a lot of prototyping. And I think the difficult thing is we can't just do the 14 o features personalization without looking further down the road because there's some other things we wanna do with personalization, a third stage of personalization. And we're actually working with some churches on that on their websites. So we wanna roll back some of those features in at least with the direction of where we're going with 14. So that personalization feature, if I had to explain it maybe better would be that, hey, we had some ideas and those ideas are good and are gonna stay, but now seeing some of the stuff that we want to go to in maybe fifteen, sixteen, it's having us reengineer some of the stuff in 14 to prepare for those things. But it's gonna be some really cool stuff. You're be able to do some really neat things with content, and it's gonna be very flexible in terms of search and filtering and personalization. And it's gonna be really fast. Oh, that's exciting. Yeah. We're not just We're not just going down the standard path of , okay, well, what can we do in SQL? SQL got booted out the door, a long time ago in terms of how we're gonna do that technology. And 've done some prototypes and it's really fast. And and so far, it looks really cool in terms of how you can make it really extensible about all that content. So, , I would encourage you guys just to keep looking at your content, trying to get as much of it into Rock as possible. And then there's gonna be some new features about how you can join different types of content together to create maybe a content library and then how you can provide personalization and search and filtering across that that library. Wow. That is going to scratch a lot of current itches out there, I think, when it comes to the desire to get more people engaged with more content that's very specific to what they need. Yeah. And and right now, that that feature set, if you didn't have a system Rock, you can do some of it, most of it Mhmm. But you can't do it in one system. And the hardest part is the the personalization because you have all your content filtering and search maybe in a different application, but you don't have any information about the person. And so being able to stitch that together is pretty cool and all in one place and then keep track of who's watching it and track the interactions. That's another whole feature we need to come back to you here soon is just some- Achievements, maybe? Yeah, you could put achievements on that, is to come back and create some analytics and some reporting around interactions. I mean, the data's all in there, you can do it Let's not say you can't do that, but how can we make that a little bit easier so you can see all that data and then do some reporting across it? Because I think, if you think a little bit into the future and maybe even now, almost everybody's putting Google Analytics on their sites. And I was thinking about it the other day, it's , should we? What value are we getting for Google Analytics? Yeah, we get some great reporting. There is value there, but is it worth trading in all that privacy and all of that data to Google to say, Hey, this is our site. This is Christian traffic. And is that a good thing? And is the trade worth it? The past, I think it was because it was , well, the privacy, they're only holding the data maybe five, ten years ago. They weren't really doing anything with the data. We were getting some value out of it. The tools weren't there. Well now, if you just wanna track interactions, you've had that in Rock from the beginning. It's been hard a little bit to report on that, but you could certainly make your own reports. So now it's , well, what is the real benefit? And there still are some, but I'm not sure if, I think I would say I'd have to convince myself to now use Google Analytics because of the privacy concerns and because of what's going on with that data. Mhmm. Some of it which we know and some of it which is not hard to infer. And I'm not sure I would wanna trade that data right now, but I'd wanna push to create some good reports. And another project actually, it hasn't hit the roadmap talk, but it is being developed right now is the ability to geocode those interactions by IP address. So we're writing in some extra properties onto the model to hold that data. And we're writing in some service accounts that you can get. Unfortunately, it's paid, but it's pretty cheap. Yeah. But you can go get an account that would will send over the data and it will geocode those IP addresses for you so you can start to see which regions those people are in. I mean, that's something you can do in Google Analytics, for example, right now, can't do in Rock. Mhmm. Today, that's interesting data, but I don't think anybody's that data's not adding another soul to heaven. Right. It's interesting to have though. I mean, are some ministry decisions being made perhaps, so that's why we wanna go out and get it. But that's kind of a challenging project too. We spend a lot time trying to figure out which service to go with, evaluating those. So that's kind of exciting, but I do think we should start proving to ourselves or validating to ourselves as data stewards of all these people who are in our database. Is it worth the the risk or the the outcomes of of Google Analytics? Yeah. That's a big topic of conversation. Yeah. It's really exciting to think about we're talking about reports and we're talking about content. But if you look at what we're really talking about, we're talking about stewarding and shepherding the spiritual journey of thousands of people. And it's just a really exciting thing to think about how these technology advances are going to make that so much easier for the individual and so much easier for the church to create and know the impact of what they're creating. Yeah. And so if you're a church of maybe let's just say you're a church of a thousand, on a weekend. So that's in our community, that's probably on the smaller side, but that's still a good sized church. So if you're a church of a thousand, that probably means you have probably three to 4,000 people who would call at home. So maybe three to 4,000 people hit your website. Is it really worth going to three to 4,000 people and saying, I'm going to go to Google, you're a Christian. Right. And that's going to affect your algorithm all for the little bit of reporting that you get. And I'm not saying we can just say, get rid of all that reporting. Maybe we need to work harder to get that inside of Rock. And maybe if people hear this and wanna help fund that, that helps move the needle for us. We're gonna do it, it's just a matter of how do we prioritize everything else that the community wants? It just, I don't know. I'm not a conspiracy theory necessarily, but in the past, I was , well, what's Google gonna do? But now you start reading what's going on in the news and the media and big tech firms. And it's kind of , well, why should I trust it? If it's just for these reports, do I really want to look three to 4,000 people in the eye and say, yeah, I just told them. Because for the most part, they're kind of naive to that. They don't think about that. And maybe if you ask them, if you had a little pop up on your website, Hey, do you mind if I share that you're a Christian at Google? they probably, most of them would probably say no, right? Prefer not. So that we can get some reports out. I mean, 99% of people have those reports, don't ever look at them again, know, if they do That's probably true. Once a year and how can we give you the basics? We can never replace Google Analytics for full package, but we could probably give you the things that you really need to know, traffic per week, by region Mhmm. Per certain parts of your page. Yeah. Top pages. We don't have that built in yet. Yeah. But it'll be fairly simple. And and the hard the data is there. , even , people wanna search by the uniform marketing codes. We have all that's being stored in Rock. Your traffic has those query string parameters, we're keeping all that. So all of that is available. I mean, I think we can get the majority, 80 of the stuff you want in Google Analytics, I think the data is already in there on So basically what you're saying is if there are churches out there that really hadn't thought about this yet, but now hearing this, they're , wow, yeah, I don't want my information on Google, but I want this, this and this to let us know. Yeah, and if you have some funding that would help prioritize it too. I think the one thing we could never do though, is we couldn't tie that into the advertising. If you're using Google and you wanna tie the effectiveness of the ad to, that's gonna be difficult because we don't have that data, but you can pass that stuff in through your ads. you can pass the marketing keys over and then you can track that. We've actually done that on some stuff. We've put up some ads for employment and we've passed that in and we've caught it on the other side and did some specific reports just on that. So there is some stuff you can do, but I would question , is again, is it worth it? that's kind of good stuff. That's , makes us feel cool because we're doing all the cool SEO stuff that our secular friends are doing, but is it worth the privacy concerns? And are we really making that big of a decision on it? I know in our case, we didn't use it. We used the terms that came through and it was more than enough. we knew on this page, this much traffic came from the Google ad. That was pretty easy to see. Wow, that is some exciting stuff coming up and some big questions to consider. So thanks for sharing enough of that for people to start kind of prethinking. And as you mentioned, preload your content in Rock. , we do have a lot of requests from the churches that we work with about certain things they'd to have done in their, especially their external pages of Rock. If the content's not there, that's just one more hurdle to jump over before it's ready to go. Yeah. And with Thirteen coming out, a big piece of that is getting their media set up. media is a new feature within Thirteen. And so it's been fun and rewarding to help churches get their media. From Vimeo or HiVision or YouTube, wherever they had it before, getting that converted into media within Rock so that we can get all that analytics. It's really cool to to see that in play. It's not too super hard to do. And then once you're there once you're there, you have all these this data that you can, , exchange people's experiences and see how people are interacting with that that media. And if you're listening and you don't know any more about media analytics than that, check out our blog. It was not too long ago that we posted a video that had a summary of all the v 13 features that were added. So there's more details there about media analytics, and we strongly suggest that you check that out. Yeah. Definitely. Speaking of v 13, we also had some new profile protection features that came out and that have really good reasons for the for that being the case in v 13, but might be a little bit confusing for some people running into them for the first time. So we've been kind of paying attention to the community chatter and picking up on some of the questions so we could bring those here to the podcast and provide some additional answers. Yeah, and that's another area where really the stewardship is so important to consider as you work through this as a Rock administrator. It's not just, should I flip this on and off because I want to? You have to think about, , what is the ramifications for that? So as Rock has gotten more powerful and had more things that it could do, and as the world's become more and more of a, , security minded, which is good, we've realized that we need to put some more options into the hands of the administrator. And there's some things that we shouldn't really do. It might've been okay in the past because it wasn't such a powerful tool and security just gets more and more important. So it wasn't a decision we thought was a binary one, allow it or don't allow it. It became , let's not allow it by default, but let people adjust it. And that's where we created these security profiles. So basically, it's just going through a database and saying not everybody's equal in terms of their x access to Rock or the or their capabilities in Rock. So let's let's classify each record person's record as what is the security profile of this record? Is it high? Is it extreme? Are they a staff person? a staff person, holy cow, be careful. if someone hijacks that account Oh, all the things they'd have access to. Yeah. Yeah. An administrator is basically gonna have everything, right? So we need to protect those accounts really well. Now, someone who's just has a name in database, I mean, that's kind of important still. We don't wanna get that to get out, but it's not the same access level. And so you might be willing to add a little bit more power to that ability. So when I say power, allow the church to send them a tokenized link that they can click on that automatically knows who they are. If they were to forward that to a friend and their friend were to click on it, well, okay, they have their name. That's not good, but they don't have complete carte blanche access to the database. that would be horrific. Yep. So we're just putting these levels in. And so you'll see those levels on the person profile page. Now you have to see it on the person profile page. We kind of purposely didn't make it And there has been some pushback about that. And I get that. it is a little startling, I would say, maybe is a good word when staff sees that, but that's intentional. People need to understand that. And I think there has been some thought, well, my staff don't understand it, and they're never gonna understand that, and then they just don't care. It's , okay, I get that, we understand that, but they need to care, because the biggest security hole in any organization- The staff. Is the staff. Yep. Yep. I mean, go to any security expert, they'll tell you that. There's whole services that will send out phishing schemes to your staff, just to see how many of them will click on a link that would have downloaded a virus, and then they'll tell you that. Right. It's not because of malicious intent. It's because of accidental stuff that a staff member inadvertently exposes their account somehow. Yeah, and it's kind of ignorance of this new stuff and we have to train them as professionals. It doesn't just grow in their heads, it has to be communicated and educated. And this is another thing. So I would strongly encourage you not to hide it. I have seen maybe a few people talking about perhaps putting CSS in the hide it. I think that's a very bad idea. That's the kind of idea I think in the future, could come along and see that and not be too happy that that was done. And remember the first time you see something this, yeah, it's shocking and it's different. And that makes sense, but think it through, it's a new thing, so let it digest a little bit. And I think it's super important to have that conversation. And I would get in front of your staff at a staff meeting and say, Hey, I'd to do a presentation on security. Not only talk about these account profiles, but talk about phishing schemes and say, Hey, , you're gonna get these things. Throw up some example emails. I mean, some of them are pretty good. I've almost clicked on a few of them. And some of them are legit and they're real, and I'm still doubting it because I'm , Well, I'm not sure about this. I don't know if I wanna click on this. Yeah. So staff meeting, a lunch and learn, and then take those items and put them into your onboarding process so they catch the new staff members as they come in. Yeah. And it really should be a yearly thing that you get in from your staff and go through it. And then maybe that there are some services. I know Justin at IT OneSource has done that. We've partaken in that too. We have very, for the most part, technical staff, but it's always going to be a reminder for us because of the types of work we do and the types of the data that we have access to. We want to make sure that we're on the cutting edge of that of that training. So back to the account profile. So it it allows you to grade each account in in terms of accessibility fear, and then it can allow or disallow certain kind of capabilities. So you can say for someone in this category, I don't want to to allow tokenized links that allows them to log in automatically. , you probably don't want your Rock administrator having those links because those links can get out. And there's lots of options even with those links. You can make one time links, you can make links that expire. Yeah, do that. But at a certain point, maybe you shouldn't do it at all. And so again, it's a new feature, so there has been some talk back and forth. Well, I'm just going to enable all of it back to where it was. Because of merges. Some people were , Well, I don't want to disable the ability to create duplicates, or I don't want to create duplicates. Don't want to create duplicates, right. But you don't want a duplicate of a staff member, really. Yeah, and the duplicates in the merging capability, that's another thing we put a lot of time into. So there's big, huge, strong warnings , Hey, this is a staff person. You don't merge this data unless you're absolutely certain of it. And again, that's good. What I would say on the merge thing, and I know Nick, you're on the same page too, is , duplicates happen. , it's life. Yeah, it's a convenience thing. It's , you can have good convenience for yourself and have no duplicates, so you can have good convenience for the person and have duplicates. Personally, my take is train people to merge your duplicates for you, get volunteers. Are, trust me, I've done it. There are volunteers who actually love doing that. They're not necessarily the most common volunteer, but there are people who are high Cs, high detail, maybe who can only can work from home, which you don't maybe trust at first, but bring them in, train them, get the trust, get them to sign a document. And once they've built that trust, I mean, we had one of those at CCV, she was so good. I would sometimes intentionally try to create duplicates so I could do some testing. And before I could get to my testing, she'd already have it merged. I'd have to call her and say, Hey, just hold off on these because I'm actually intentionally doing it. And she just felt that that was her one piece of ministry that she could do that she was really good at and she loved it, and she's not the only one out there. But understand, and I think before clicking all the buttons and putting it back to default, take the stewardship mindset and say, Hey, it's not my preference, it's not my call, what is the right thing to If I really wanna protect this data, maybe have a conversation and try to explain it to your next level up and try to get some input, because we're never gonna be able to go to the next step in digital ministry if we don't start taking a stewardship mindset and start talking about things and the ramifications of things and not just thinking about, let's say, what's best for me and my merges and my duplicates, but what's best for these people's data. at certain point, no one wants to have to go talk to people and say, yeah, sorry, all your contact information and you're giving history was downloaded. Yeah, seen by someone else. So again, those features where we put a lot of time into them. We'd have ratcheted them to the tight level. Mhmm. Because it's easier for you guys to go in there and release them than it is for us to put it in as weak and have to have you strengthen them. Right. as a software author, we really need to come out on the firm side. But that said, I would leave them the way they were. I just think security is that important. And at the very least, I can always go back to, well, we kept it at the highest level. I'd wanna report up to my leadership. I kept it at the highest level. But if I weakened it down, that's not a message I'd to tell them. Well, I lowered the security and maybe that was it and maybe it wasn't, but I still don't wanna say that. I want them to think, well, I did the best I could. Yeah, that's a great point. And just to put a spotlight again on the word that you use there, you use stewardship in reference to data. A lot of times in the church world, we use stewardship associated with financial resources. But we are in many of our positions here in the Rock community, stewarding people's data, and it is critical. And we do need to approach it from that conservative, thoughtful perspective. Yeah. So even today, we got talked about from the account profile perspective, but also for the privacy in terms of who are we sharing this data with. Right. And again, why share data with anyone if you don't have to? That's a great question. And as you mentioned, probably not one we'd want to have to go in front of a person whose data had been accidentally compromised and tell them, well, we didn't put a lot of thought into it. Sorry, we forgot about it. Or it just was easier for our team to deal with that way and we didn't want to change it. That's just not something you'd really wanna have to tell someone. Yeah. Back when I was doing communications at CCV, I would do this this kind of mental test in my head. I'd try to write it as a newspaper article, a headline, and then feel , I wanna defend that? Right. Now that can go to the extreme in weird ways, and it's not that you always use that as your measure, but it it's another way of kinda thinking at another way, church lowers security profile and, , weekend security profile settings and, , breach happens. , oh, yeah. I wouldn't wanna read that in the paper. Church shares data with Google and blah blah blah blah. It's , oh, yeah. I mean, it's it's a trade off. And so I would say, well, is the is the value I'm getting back worth it? Mhmm. It's a risk reward scenario. Yeah. And I can say what we were doing at that time, it was not worth it. we've got a few pretty charts and maybe some slightly better linkage and graphs for some ads that we probably would have done anyways if we didn't have those. Mhmm. Well, we hope that answers some of the questions that have come up inside the community. And do realize we love to answer questions in the podcast. So if you have any additional questions, send those over to our email address, infosparkdevnetwork dot org, and we'll take a look and try to weave some answers in and some topics that help answer your questions and meet your needs. Additionally, there have been some questions that come up about the best way to update your system. So what is the best version update plan, one that won't create issues for you? Do you have a sandbox? How do you approach the the idea of updating to a new version? Some churches look at that and say, , I really only wanna update, every so often. , I'm gonna have an update plan. We do it once a year. Other churches say, well, it it looks it's in production. It's ready to launch on my, production server. Ready. Go. What are some of the best practices around updating that you could share with the community, John and Nick? I think the first one is always know what's the latest secured update. And there's always going be one for the latest release and there's always going be one for at least one release behind that, major release behind that. So you have to, have to, have to be on that release or better. If you're not, you're hurting yourself greatly and you're putting yourself at risk. After that, it becomes a little bit more optional of what you need. I would first say that every person should know what's in the latest releases. Not to know that you're basically making a decision that we have no data, you're not making a decision, you're just not acting. So always read because there might be something in there that's gonna click with something one of your colleagues is talking about. It's , oh, you want that. Well, there's a new feature. It does exactly that. Let's expedite this a little bit. At that point, I think it's just trying to determine how new do you wanna be. I do think that there's two ways that come about that. There's an honest reflection of where can you be and how many resources can you put into that. And then there's on the other side of that is , well, how much effort do you wanna put in? And I think when it comes to effort, you gotta put that off the table. We should always be giving highest effort because these are tools that help your ministry and you shouldn't be a hindrance to that, so from an effort perspective. Now there's a fair evaluation of resourcing. if you're one person, in a church of 10,000 and you have 200 staff, Okay, well, you may not be able to always keep up, but make sure that you're making that decision based on what can I put effort into to make sure that my ministry has the best newest tools and features versus what feels good to me? And I would add in that situation, it's super easy to at least get some of your staff leads, ministry leads, to go look at the pre alpha site. , hey, this is what we could have. Go look at that new feature in the finance, under the finance tab on a person profile. Exploring the features on the pre alpha site is almost free. It just takes a little time. Yeah, you've got the documentation, you got the pre alpha, show them to it. But know that if they it, you're going to be doing some work. And that's okay. That's what we get paid for. We're here to serve Jesus. And we serve Jesus by helping them get the best features and support the staff and make them incredibly productive and powerful. It's , why wouldn't you If you could sharpen their sword and that's your job as the armorer, why wouldn't you sharpen their sword? Yeah, it's real pain, right? And who wants to sharpen something? But it makes them much more effective in battle. So, yeah, that and that's a great point. the pre alpha is there. Just do know that people do some unholy things to pre alpha. So it's not always it's not always exact what you're going see. True, and we have also moved the demo site up to closer to the latest version, so I think it's running the version 13. And you could upgrade it if you want, you want to upgrade to version 13 too, go on to the demo site and hit the update button. Yeah. Yeah. I spend most of my time in pre alpha, you said, but sometimes it is someone's done something to it, so I'll head over back over to the demo So just know that, don't show it to your staff. The day of you're gonna show it to them, go check it right before the meeting. Yes. It'd be kind of embarrassing to get in there and say, oh, it doesn't work. Or make some recordings and screenshots. Because we wipe the demo site daily. Right? But the pre alpha site is on a different schedule. Every other week. Okay. And it also is pre alpha. So legitimately, there are some bugs in there that we're working And things that you won't see until version 14, the next major version. Yeah. So definitely know what's out there, I think, is the next one. And then as it comes to keeping on the bleeding edge, that's another thing that you just kind of need to look at. If you're lucky enough to have resources a sandbox, I think it's much easier. You can just upgrade your sandbox. I would have a star team of staff who kind of help you look at the new features, go find the top administrator in every single team and have them be a part of your little superstar team and get them looking at that and engaging in that and making sure that they're signing off on , yeah, I've tested these types of things and everything looks good. That gives you more peace of mind. If you can't do that, then I would say, well, still know what's in there, still try to stay up to date, but I would probably let a few months go by. So when 13 came out, I'd probably, okay, well, I'm going to keep my eye on the chat and I'm going to kind of take some temperature readings off of that, and I'll probably wait a few months. And when 13.2 is out, it's probably safe for me to step in there without a sandbox and kind of take that risk. Now, are some ways that you can go immediately back to where you were, if your Azure tools. But if you wait a few months, get a few dot releases under your belt, you're gonna be okay. Yep. And of course, don't push that button on a Friday. Oh boy. No. No. That would be Monday, Tuesday are the best days. Wednesday, maybe. Yeah. Depending on what you have going on Wednesday night. Right. Now some people have asked too, , jumps can you take? And I'd say, don't worry about that. Know where you wanna go. if I'm on 127 and I wanna go to 133, okay, well I know where I wanna go. And the update block will take you there. Sometimes you have to make intermediate stops and there's some technical reasons why we put those stops in, but that's okay. Just update to that one. It'll reset, update again, and you'll get to 13.3 in the quickest way possible that we can technically get you there. Yeah, and maybe also wait a minute after you've updated. Give it a second to catch up and fully restart, fully run jobs that might be running after the update because we've moved some things into the post update process. So don't feel you have to rush, click, click, click, click. It's always just safe. I'm paranoid. So that's how I operate. Yeah, but the update block will lead you on that path, just keep hitting update until you're at the place you want to be. But definitely you have to know what the latest security, secured version is. We don't have security releases very often, but you need to know when they come out. And it is right there on the release notes page, right on the side, upper corner tells you which is the secure version. And of course, that's just rockrms.com/releasenotes. So it's easy to get to, easy to find. And then what we've been doing for the last couple of versions, two or three, I think, is that video that I mentioned earlier where we summarize the features that are coming out with a little bit more dialogue behind them rather than just align. So when a major version is released, look for that video on our blog as well so you can get a little bit more insight and and some visuals behind that if you wanna if you wanna have that additional information. Yeah. And I would really that video should really be a exciting thing. It should be. It's basically here are all the new powerful tools for you to do ministry and for you to communicate and get that out to your staff and colleagues so that they can go to battle. It's the latest version unboxing video, really. It shows you, it walks you through it, it shows you what you're looking at and it is very exciting. I think it's a lot of time that gets put into that. Mean, I think it's well over an hour. I know we do that before it's a video, we do it on our staff to train them and to get feedback so that we can make the video even better. Yep. Great. Well, that answers a lot of really good questions in the community. And also, if you want questions about Rock itself answered, we have a lot of classes coming up that are tailored to you right where you are. So if this spring you're looking for additional Rock instruction, you can find it at, our 100 class. So our basic entry class is Rock one zero one, one zero two. It is a a survey class that kinda gives you some some guided videos to watch on certain days. Those are videos currently available on the site, but how it is. It's much easier to have someone telling you what to watch that when to get through them. And then the great part about this is you have a Rock instance you can play around with while you're learning and a Rock instructor on a daily basis for two weeks, for a scheduled time where you can ask questions related to the content you've consumed that morning. So that survey class is fantastic if you're looking at Rock. If you have new staff that will interact with Rock in some ways and you want them to really have a an understanding of what it all all is, it's not just a group's tool or just a check-in tool. There's a a quite a bit more there, and the investment is a little bit lower than, say, the masterclass, but we do have a masterclass coming up as well. That's May 10. And, so make sure that you're you're looking for that. If you're ready, you have a new person coming on that's a Rock admin, you're new, or you just haven't gotten around to that class and you wanna fill in some gaps, that's a great class to go to. And then finally, the next level from that, if you want to, is a SQL for Rock class that takes you down into the data structure of Rock. This is for people who know Rock and don't really know much about SQL. We'll help get you up and running. That's coming this summer, or I'm sorry, this, spring, April 19. So it's coming up. Make sure you get registered. And we have, just really begun seeing registration start coming in for Rx. So we know a lot of people started budgeting around December. We're seeing our registration start moving now, and we've had to adjust our room block already. So if you're planning to come to Rx, don't put off your ticket purchase. Ahead and get that in and do your room reservation at the same time. We are for sure going to be spilling over into other hotels for this event. So if it's important to you to be right on-site, and we did that last year, it was really convenient and really fun. Just make sure to get those rooms booked soon. Yeah. It's so nice to have it right on-site. It really is. Go upstairs and you're there. Convenient, fun. Plus the lobby was just full of people. All night. All hours. Just a lot of fun. We're really looking forward to the event this year. Yeah. So, , the podcast is really important to us and we wanna make sure that we can celebrate that and honor those who listen to it and try to get a few more people. So we have a little special promotion for this podcast and we have a special chip sticker for you guys who listen to the podcast. It's a Mr. T chip sticker. And really the theme of it is I pity the fool who doesn't subscribe to the Rockcast podcast. So because you're listening to this, you now have the secret information of how to get this sticker for free, and you just need to go to the Rock website, rockrms.com/pitythefool,alllowercase,nospaces,pitythefool. And you can put your name and information in there to and we'll send you the sticker for free. So here's the deal though. You can't tell other people Mm-mm. About this link. You can tell people about this podcast, and they can listen to the podcast, get to this segment of the podcast, and they'll realize that they need to go do this, but you can't this this is community honor system right Don't break Chip's heart. So when they see that sticker in their office. Yes. They just have to say, yeah, it's a special thing I got. Yeah, at least for now. In the early part, it's an exclusive sticker. Who knows where it goes? Now there's a limited time frame for this, so you wanna go do this as you hear this. But if you're listening to this six months from now, sorry. But so please do spread this to other people. Just tell them, hey, there's something in the podcast you're gonna wanna listen to. It might be interesting. Don't tell them it's at the very end. No. Don't tell them that. Skip to the end. Yep. But this is a way for us to to celebrate those who do listen to the podcast and also help you guys have a tool to encourage others to listen to the podcast. That is super fun. And I know people are gonna be scrambling right now to see what that looks . I hope so. That's right. Well, thank you so much for being our faithful listening audience, for tuning in, and for allowing us to share some things with you. Please do feel free at any time to send us additional questions or insights about the podcast to our info email address. We will keep an eye out for that, add that content to future podcasts, and we look forward so much to hearing from you. So thanks for tuning in, and we will come back next time with more information. Do a church that loves the idea of using Rock but hasn't taken that leap yet? With managed hosting, churches of any size can get access to Rock's amazing technology, hassle free. With just one click, Rock's managed hosting removes the roadblocks that might stop a church from switching to Rock by making the process simple. Churches get the ease of a SaaS church management system without losing any of Rock's powerful features. Are you ready to take the next step or share with another local church? Visit rockrms.com/hosting today.