<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~files/feed-premium.xsl"?>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:feedpress="https://feed.press/xmlns" xmlns:media="http://search.yahoo.com/mrss/" xmlns:podcast="https://podcastindex.org/namespace/1.0" version="2.0">
  <channel>
    <feedpress:locale>en</feedpress:locale>
    <atom:link rel="self" href="https://feedpress.me/rock"/>
    <image>
      <link>https://community.rockrms.com/connect</link>
      <title><![CDATA[Rock RMS Blog]]></title>
      <url>https://static.feedpress.com/logo/rock.jpg</url>
    </image>
    <title>Rock RMS Blog</title>
    <link>https://community.rockrms.com/connect</link>
    <description/>
    <language>en-us</language>
    <ttl>120</ttl>
    <lastBuildDate>Thu, 19 Nov 2026 04:07:00 -0700</lastBuildDate>
    <item>
      <title>RX26's Secret Sauce Wasn't on the Schedule | Ep 226</title>
      <guid>a7919588-e591-4944-a715-38fe1767d8e8</guid>
      <link>https://feedpress.me/link/5849/17528808/470</link>
      <pubDate>Wed, 18 Nov 2026 15:20:00 -0700</pubDate>
      <description><![CDATA[
            <img src="https://www.rockrms.com/GetImage.ashx?guid=d4551e9c-ef86-4a75-b4b9-d45ab0871a7b" />
            <br />
            <div style="position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden; margin-bottom: 24px;">
  <iframe
    src="https://www.youtube.com/embed/2U_xJLL_6I0?si=aAFdRnsYMlCIWJrz"
    style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"
    frameborder="0"
    allowfullscreen>
  </iframe>
</div>
<p>RX26 is in the books, and it was our biggest year yet, with 855 registrations worldwide. Emily and Nicole revisit the defining moments  from Ted Decker's opening rap to the future of check-in, nine Gold Circle Awards and a Hall of Fame induction.&nbsp;</p>
<p>They also dive into the sessions attendees are still talking about. Horst Schulze delivered an inspiring call to build systems of excellence, and Ministry by Design proved so valuable that churches from overseas and outside the Rock Community came just to hear it.&nbsp;Paired with Staffing for Scale, it gives you a way to design your ministries and your team intentionally.</p>
<p>Emily walks through a few of the exciting features coming in v20: Helix in Rock Mobile, the Code and Workflow Composer, and a new Group Finder. They share community feedback from the event and answer questions raised in the survey.</p>
<p>The best part of RX26 was the Community, the connections, the hallway conversations, the secret sauce no session can replicate. For so many of you, RX was the reset button you didn't know you needed. Listen now to catch the vision and relive the Community's favorite moments.</p>
<h2><a href="https://www.rockrms.com/partners">Rock Partners</a></h2>
<p>We are thankful for our Rock Partners and their support of the Rock Community. Visit their websites through the link above to learn how they can help your ministry and confirm that those you work with are as invested in the success of Rock as you are!</p>
<h2>Quick Links</h2>
<ul>
<li>Catch all of the sessions we talked about: AI in Rock, Ministry by Design, Staffing for Scale, in the <a href="https://rx.rockrms.com/subscription">Content Subscription</a>. One purchase provides your entire organization with year-long access to all non-vendor speaking sessions.</li>
<li>We've made Jon's <a href="https://rx.rockrms.com/#keynotes">The Algorithm &amp; the Altar Keynote</a> and the <a href="https://rx.rockrms.com/#keynotes">Rock Forward Keynote</a> available to watch online. These are 2 great resources to share with your team and leadership to inspire, encourage and equip.</li>
<li>Registration for RX27 is available now with the Early Bird sale. <a href="https://rx.rockrms.com/">Purchase your tickets today</a> for the most affordable pricing.</li>
<li>Check out the <a href="https://www.rockrms.com/releasenotes#v20.0">v20 roadmap</a> and Jon's <a href="https://community.rockrms.com/subscriptions/rx26/ai-in-rock-whats-here-whats-coming">AI in Rock Vision Day Breakout Session</a> to learn where Rock is heading next.</li>
<li>Learn how to bring back the RX26 immersive walkthrough <a href="https://rx.rockrms.com/rx26-check-in-experience">Check-In Experience</a> to your ministry today.</li>
</ul>

        <img src="https://feedpress.me/link/5849/17528808.gif" height="1" width="1"/>]]></description>
      <summary>
            RX26 is in the books and it was our biggest year yet. Emily and Nicole revisit the can't-miss moments, Ministry by Design and the v20 roadmap, answer your survey feedback and celebrate the Community.
        </summary>
    </item>
    <item>
      <title>The Can't Miss Moments of RX26</title>
      <guid>17335ef4-ef19-4cd9-af94-3f4380bf373a</guid>
      <link>https://feedpress.me/link/5849/17521881/470</link>
      <pubDate>Tue, 10 Nov 2026 16:45:00 -0700</pubDate>
      <description><![CDATA[
            <img src="https://www.rockrms.com/GetImage.ashx?guid=263e57b9-f4fa-466c-8fa1-f1d20d5ffe0a" />
            <br />
            <p>This past week, the Rock Community took over downtown Phoenix for Rock's annual conference, <a href="https://rx.rockrms.com/">RX26</a>. The event started with Ted Decker on the big screen rapping about all the ways he's been Rockmaxxing, and it had the Community excited for everything to come next.</p>
<div style="position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden; margin-bottom: 24px;">
  <iframe
    src="https://www.youtube.com/embed/Ksa9n2fM3rs?si=_jaQDptNE2k59EtL"
    style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"
    frameborder="0"
    allowfullscreen>
  </iframe>
</div>
<p>It was our biggest RX yet with 855 registered attendees who came from across the globe for three days of keynotes, hands-on sessions and the kind of hallway conversations that only happen when this many Rock churches are in one place. Here are some of the best memories we're taking with us and the golden nuggets we hid throughout the event.</p>
<h2>An Immersive Look at the Future of Check-In</h2>
<p><img src="https://www.rockrms.com/GetImage.ashx?guid=7ba37032-8f96-49ff-a405-f0545268becb" alt="" class="img-responsive"></p>
<p>Attendees first walked into the Future of Check-In experience, an immersive, Disney-like walkthrough we built to help churches picture check-in technologies in their own lobbies. You can see it unfold,&nbsp;learn how we set it up and <a href="https://rx.rockrms.com/rx26-check-in-experience">apply it to your ministry</a> today.</p>
<p><img src="https://www.rockrms.com/GetImage.ashx?guid=31eb8134-62ad-42ba-b8cd-b8bc698bc5df" alt="" class="img-responsive"></p>
<p>Attendees tapped for NFC check-in and watched the Bluetooth Beacon work in real time, sensing each person as they walked near and generating an AI-created baby photo that was equally hilarious and surprisingly convincing. It was a fun reminder that the technology shaping check-in today is far more approachable than you might think.</p>
<h2>Building a Culture of Excellence</h2>
<p><img src="https://www.rockrms.com/GetImage.ashx?guid=d0cb0e9b-3548-43c6-8b61-4407d8ced807" alt="" class="img-responsive"></p>
<p>Our guest keynote speaker, Horst Schulze, challenged the room to stop leaving excellence to chance. Drawing on a career built on world-class hospitality, he made the case that excellence is not something you stumble into on a good day. It's the product of systems you design on purpose.</p>
<p>For the ministry leaders and church staff in the room, the message landed. Schulze encouraged everyone to build intentional systems that engrain excellence into how their teams operate, so that deeply caring for people becomes the standard rather than the exception.</p>
<h2>Rock Forward: What's Coming in v20 and Beyond</h2>
<div style="display: flex; justify-content: center; width: 100%;">
<blockquote class="instagram-media" data-instgrm-permalink="https://www.instagram.com/reel/DfSuG2uyltc/?utm_source=ig_embed&amp;utm_campaign=loading" data-instgrm-version="14" style=" background:#FFF; border:0; border-radius:3px; box-shadow:0 0 1px 0 rgba(0,0,0,0.5),0 1px 10px 0 rgba(0,0,0,0.15); margin: 1px auto; max-width:540px; min-width:326px; padding:0; width:99.375%; width:-webkit-calc(100% - 2px); width:calc(100% - 2px);"><div style="padding:16px;"> <a href="https://www.instagram.com/reel/DfSuG2uyltc/?utm_source=ig_embed&amp;utm_campaign=loading" style=" background:#FFFFFF; line-height:0; padding:0 0; text-align:center; text-decoration:none; width:100%;" target="_blank"> <div style=" display: flex; flex-direction: row; align-items: center;"> <div style="background-color: #F4F4F4; border-radius: 50%; flex-grow: 0; height: 40px; margin-right: 14px; width: 40px;"></div> <div style="display: flex; flex-direction: column; flex-grow: 1; justify-content: center;"> <div style=" background-color: #F4F4F4; border-radius: 4px; flex-grow: 0; height: 14px; margin-bottom: 6px; width: 100px;"></div> <div style=" background-color: #F4F4F4; border-radius: 4px; flex-grow: 0; height: 14px; width: 60px;"></div></div></div><div style="padding: 19% 0;"></div> <div style="display:block; height:50px; margin:0 auto 12px; width:50px;"><svg width="50px" height="50px" viewBox="0 0 60 60" version="1.1" xmlns="https://www.w3.org/2000/svg" xmlns:xlink="https://www.w3.org/1999/xlink"><g stroke="none" stroke-width="1" fill="none" fill-rule="evenodd"><g transform="translate(-511.000000, -20.000000)" fill="#000000"><g><path d="M556.869,30.41 C554.814,30.41 553.148,32.076 553.148,34.131 C553.148,36.186 554.814,37.852 556.869,37.852 C558.924,37.852 560.59,36.186 560.59,34.131 C560.59,32.076 558.924,30.41 556.869,30.41 M541,60.657 C535.114,60.657 530.342,55.887 530.342,50 C530.342,44.114 535.114,39.342 541,39.342 C546.887,39.342 551.658,44.114 551.658,50 C551.658,55.887 546.887,60.657 541,60.657 M541,33.886 C532.1,33.886 524.886,41.1 524.886,50 C524.886,58.899 532.1,66.113 541,66.113 C549.9,66.113 557.115,58.899 557.115,50 C557.115,41.1 549.9,33.886 541,33.886 M565.378,62.101 C565.244,65.022 564.756,66.606 564.346,67.663 C563.803,69.06 563.154,70.057 562.106,71.106 C561.058,72.155 560.06,72.803 558.662,73.347 C557.607,73.757 556.021,74.244 553.102,74.378 C549.944,74.521 548.997,74.552 541,74.552 C533.003,74.552 532.056,74.521 528.898,74.378 C525.979,74.244 524.393,73.757 523.338,73.347 C521.94,72.803 520.942,72.155 519.894,71.106 C518.846,70.057 518.197,69.06 517.654,67.663 C517.244,66.606 516.755,65.022 516.623,62.101 C516.479,58.943 516.448,57.996 516.448,50 C516.448,42.003 516.479,41.056 516.623,37.899 C516.755,34.978 517.244,33.391 517.654,32.338 C518.197,30.938 518.846,29.942 519.894,28.894 C520.942,27.846 521.94,27.196 523.338,26.654 C524.393,26.244 525.979,25.756 528.898,25.623 C532.057,25.479 533.004,25.448 541,25.448 C548.997,25.448 549.943,25.479 553.102,25.623 C556.021,25.756 557.607,26.244 558.662,26.654 C560.06,27.196 561.058,27.846 562.106,28.894 C563.154,29.942 563.803,30.938 564.346,32.338 C564.756,33.391 565.244,34.978 565.378,37.899 C565.522,41.056 565.552,42.003 565.552,50 C565.552,57.996 565.522,58.943 565.378,62.101 M570.82,37.631 C570.674,34.438 570.167,32.258 569.425,30.349 C568.659,28.377 567.633,26.702 565.965,25.035 C564.297,23.368 562.623,22.342 560.652,21.575 C558.743,20.834 556.562,20.326 553.369,20.18 C550.169,20.033 549.148,20 541,20 C532.853,20 531.831,20.033 528.631,20.18 C525.438,20.326 523.257,20.834 521.349,21.575 C519.376,22.342 517.703,23.368 516.035,25.035 C514.368,26.702 513.342,28.377 512.574,30.349 C511.834,32.258 511.326,34.438 511.181,37.631 C511.035,40.831 511,41.851 511,50 C511,58.147 511.035,59.17 511.181,62.369 C511.326,65.562 511.834,67.743 512.574,69.651 C513.342,71.625 514.368,73.296 516.035,74.965 C517.703,76.634 519.376,77.658 521.349,78.425 C523.257,79.167 525.438,79.673 528.631,79.82 C531.831,79.965 532.853,80.001 541,80.001 C549.148,80.001 550.169,79.965 553.369,79.82 C556.562,79.673 558.743,79.167 560.652,78.425 C562.623,77.658 564.297,76.634 565.965,74.965 C567.633,73.296 568.659,71.625 569.425,69.651 C570.167,67.743 570.674,65.562 570.82,62.369 C570.966,59.17 571,58.147 571,50 C571,41.851 570.966,40.831 570.82,37.631"></path></g></g></g></svg></div><div style="padding-top: 8px;"> <div style=" color:#3897f0; font-family:Arial,sans-serif; font-size:14px; font-style:normal; font-weight:550; line-height:18px;">View this post on Instagram</div></div><div style="padding: 12.5% 0;"></div> <div style="display: flex; flex-direction: row; margin-bottom: 14px; align-items: center;"><div> <div style="background-color: #F4F4F4; border-radius: 50%; height: 12.5px; width: 12.5px; transform: translateX(0px) translateY(7px);"></div> <div style="background-color: #F4F4F4; height: 12.5px; transform: rotate(-45deg) translateX(3px) translateY(1px); width: 12.5px; flex-grow: 0; margin-right: 14px; margin-left: 2px;"></div> <div style="background-color: #F4F4F4; border-radius: 50%; height: 12.5px; width: 12.5px; transform: translateX(9px) translateY(-18px);"></div></div><div style="margin-left: 8px;"> <div style=" background-color: #F4F4F4; border-radius: 50%; flex-grow: 0; height: 20px; width: 20px;"></div> <div style=" width: 0; height: 0; border-top: 2px solid transparent; border-left: 6px solid #f4f4f4; border-bottom: 2px solid transparent; transform: translateX(16px) translateY(-4px) rotate(30deg)"></div></div><div style="margin-left: auto;"> <div style=" width: 0px; border-top: 8px solid #F4F4F4; border-right: 8px solid transparent; transform: translateY(16px);"></div> <div style=" background-color: #F4F4F4; flex-grow: 0; height: 12px; width: 16px; transform: translateY(-4px);"></div> <div style=" width: 0; height: 0; border-top: 8px solid #F4F4F4; border-left: 8px solid transparent; transform: translateY(-4px) translateX(8px);"></div></div></div> <div style="display: flex; flex-direction: column; flex-grow: 1; justify-content: center; margin-bottom: 24px;"> <div style=" background-color: #F4F4F4; border-radius: 4px; flex-grow: 0; height: 14px; margin-bottom: 6px; width: 224px;"></div> <div style=" background-color: #F4F4F4; border-radius: 4px; flex-grow: 0; height: 14px; width: 144px;"></div></div></a><p style=" color:#c9c8cd; font-family:Arial,sans-serif; font-size:14px; line-height:17px; margin-bottom:0; margin-top:8px; overflow:hidden; padding:8px 0 7px; text-align:center; text-overflow:ellipsis; white-space:nowrap;"><a href="https://www.instagram.com/reel/DfSuG2uyltc/?utm_source=ig_embed&amp;utm_campaign=loading" style=" color:#c9c8cd; font-family:Arial,sans-serif; font-size:14px; font-style:normal; font-weight:normal; line-height:17px; text-decoration:none;" target="_blank">A post shared by Rock RMS (@rockrms)</a></p></div></blockquote>
</div>
<script async src="https://www.instagram.com/embed.js"></script>
<p>In the <a href="https://community.rockrms.com/subscriptions/rx26/rock-forward">Rock Forward Keynote</a>, Jon pulled back the curtain on what's coming next, and the roadmap left attendees cheering and clapping.&nbsp;Here are a few of the highlights from <a href="https://www.rockrms.com/releasenotes#v20.0">v20</a>:</p>
<ul>
<li><b>Rock Mobile Chat</b> brings conversations directly into Rock Mobile, so Community members can connect without leaving the app.</li>
<li><b>Helix in Rock Mobile</b> carries the Lava Applications model into mobile. Get fresh data nearly instantly without needing a page refresh.</li>
<li><b>Code and Workflow Composer</b> makes building logic and automations faster and more approachable for teams of every skill level.</li>
<li>An <b>improved Group Finder</b> makes it easier for people to discover and connect with the right groups at your church.</li>
</ul>
<p>Taken together, the roadmap points to more capability and more accessibility, whether you're a seasoned developer or building your very first workflow.</p>
<h2>Celebrating Gold Circle Awards &amp; New Hall of Fame Inductee</h2>
<p><img src="https://www.rockrms.com/GetImage.ashx?guid=35f358c3-3050-4c3b-990d-fe589f24dc6c" alt="" class="img-responsive"></p>
<p>RX is as much about the Community as it is about the software. We handed out nine Gold Circle Awards, recognizing the churches who use Rock's powerful toolkit for impactful ministry projects. Learn more about these <a href="https://rx.rockrms.com/rx26-gold-circle-winners">award-winning projects</a> and be inspired.</p>
<p><img src="https://www.rockrms.com/GetImage.ashx?guid=444e4caa-fef7-420b-b682-5baf127b0999" alt="" class="img-responsive"></p>
<p>We also welcomed a new inductee into the Hall of Fame, Adam Hann. Adam's ongoing contributions and leadership in the Community have left a lasting mark, and his induction was a well-deserved moment of recognition!</p>
<h2>Catch Every Session with the Content Subscription</h2>
<p>If you couldn't make it to every session, the <a href="https://rx.rockrms.com/subscription">RX26 Content Subscription</a> is now live, giving you on-demand access to the full lineup. It's the perfect way to go deeper on the sessions you loved and catch the ones you missed.</p>
<p>It also provides excellent training for your team back home. Instead of one person bringing back a page of notes, your whole staff can learn directly from the sessions, at their own pace, long after the conference ends.</p>
<p>And a few of the biggest moments are free and open to everyone. Jon's <a href="https://rx.rockrms.com/">Vision Day Keynotes</a> and the <a href="https://community.rockrms.com/subscriptions/rx26/community-keynote-1">Community Keynote</a> are public, so you can share them with your leadership to get your whole team aligned.</p>
<h2>RX27 Is Already Here</h2>
<p>If RX26 is any indication, you won't want to miss what comes next. <a href="https://rx.rockrms.com/rxregister/rx27">RX27</a> registration is open, and tickets are the most affordable right now.</p>
<p>We're not the only ones excited. In less than 24 hours after RX26 wrapped, a dozen people had already signed up to come back for another year. We'd love to have you in the room with them.</p>
<p>Thank you to everyone who joined us for RX26, to our speakers, Rock Stars, award winners and to the incredible Rock Community. See you at RX27!</p>

        <img src="https://feedpress.me/link/5849/17521881.gif" height="1" width="1"/>]]></description>
      <summary>
            RX26 was our biggest year yet, with 855 registered attendees. Here are some of the best memories we're taking with us and the golden nuggets we hid throughout the event.
        </summary>
    </item>
    <item>
      <title>Your RX26 Bucket List Just Became a Bingo Card</title>
      <guid>e8e73a7b-17c9-49f6-ac02-63c9a08a95d8</guid>
      <link>https://feedpress.me/link/5849/17513913/470</link>
      <pubDate>Mon, 02 Nov 2026 09:23:00 -0700</pubDate>
      <description><![CDATA[
            <img src="https://www.rockrms.com/GetImage.ashx?guid=1645cba9-8a14-4faa-8b2f-0befc1de2394" />
            <br />
            <p>With hundreds of Community members from across the world flooding the Phoenix Convention Center this week for RX26, there's going to be three back-to-back days of keynotes, breakout sessions, and a few local experiences you won't want to skip.</p>
<p>So, we made a bingo card filled with all the fun key conference experiences to fill your weeklong trip!</p>
<p>Half the squares are pulled straight from the conference: things like scanning sponsor QR codes, joining the surprise community activity, and chatting with a Rock Star between sessions. The other half sends you out into Phoenix, whether that's riding a Waymo, dining at an award-winning restaurant, or tracking down a saguaro cactus taller than Chip.</p>
<p>The idea is simple. Stop by the info center on your way in to pick up a bingo card and start filling out the squares. Get 5 in a row, and you've had a great RX. Fill the whole card, and you've lived the RX experience to the fullest.</p>
<h2>Here's How to Play</h2>
<p><b>Solo -&nbsp;</b>Work your way through the card at your own pace and see how many squares you can check off by the closing session.</p>
<p><b>With your team -</b>&nbsp;If you're bringing a group from your church, split up the card and compare notes at the end of each day.</p>
<p><b>For the win</b> - Post your completed card on social media and tag @rockrms. We'll be sharing the wins throughout the week.</p>
<p>Whether you're a first-time attendee or you've been to every RX since the beginning, this is a fun way to make sure you don't just attend the conference; you experience all of it. See you in Phoenix.</p>
<div class="structuredcontent-attachment"><div class="structuredcontent-attachment-fileicon"><div class="structuredcontent-attachment-fileicon-background"></div><div class="structuredcontent-attachment-fileicon-label" title="png">png</div></div><div class="structuredcontent-attachment-fileinfo"><div class="structuredcontent-attachment-fileinfo-title">RX26_Bingo.png</div><div class="structuredcontent-attachment-fileinfo-size" data-size="KiB">231.7</div></div><a class="structuredcontent-attachment-download" href="https://www.rockrms.com/GetFile.ashx?guid=ac2aab5c-f611-414b-8111-1fd8798cb341" target="_blank" rel="nofollow noindex noreferer"><svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="icon icon-tabler icons-tabler-outline icon-tabler-download"><path d="M4 17v2a2 2 0 0 0 2 2h12a2 2 0 0 0 2 -2v-2"></path><path d="M7 11l5 5l5 -5"></path><path d="M12 4l0 12"></path></svg></a></div>
        <img src="https://feedpress.me/link/5849/17513913.gif" height="1" width="1"/>]]></description>
      <summary>
            Don't just attend conference, experience it to the fullest by playing our official bingo card! You'll find plenty of fun activities to do at RX, ways to connect with Community members and Arizona-exclusive adventures.
        </summary>
    </item>
    <item>
      <title>The Security Wake-Up Call and Your RX26 Playbook | Ep 225</title>
      <guid>079c1468-db5d-4f12-bc35-639ad18cd693</guid>
      <link>https://feedpress.me/link/5849/17513914/470</link>
      <pubDate>Fri, 23 Oct 2026 16:24:00 -0700</pubDate>
      <description><![CDATA[
            <img src="https://www.rockrms.com/GetImage.ashx?guid=4b98031c-f818-44a4-ab2d-f1b02e5eff29" />
            <br />
            <div style="position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden; margin-bottom: 24px;">
  <iframe
    src="https://www.youtube.com/embed/MtXvlC7oZT4?si=Y04yuLCZaI4rq1dd"
    style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"
    frameborder="0"
    allowfullscreen>
  </iframe>
</div>
<p>This week a major PHP exploit went public. While admins worked hard to roll out the patch, AI was already reverse-engineering it within minutes. Jon, Emily, and Nicole unpack what that means for your church.</p>
<p>Jon covers the latest security wave (19.7, 18.7, and 17.11) and why we won't be patching three major versions anymore. It's another critical reason to stay current on the latest secure version. With Early Access and the grant program, there's no reason to be behind.</p>
<p>Emily shares how to get the most out of RX26: set your out-of-office reminder, build your schedule, plan sessions as a team, join a community dinner, stay out late in the Renaissance lobby, and look for someone who needs a friend.</p>
<p>Listen now and share it with your team before heading to Phoenix.</p>
<h2><a href="https://www.rockrms.com/partners">Rock Partners</a></h2>
<p>We are thankful for our Rock Partners and their support of the Rock Community. Visit their websites through the link above to learn how they can help your ministry and confirm that those you work with are as invested in the success of Rock as you are!</p>
<h2>Quick Links</h2>
<ul>
<li><a href="https://rx.rockrms.com/rx-app">Download the Rock Community App</a> to start building your personal RX26 schedule, sign up for Rock Star Consults, see the floor plans and so much more.</li>
<li>It's not too late to sign up for <a href="https://rx.rockrms.com/rock_blog26">RX26</a>! Invite your leadership and local churches to experience Rock and the Community.</li>
<li>Visit the<a href="https://community.rockrms.com/feature-retirement"> Feature Retirement page</a> to plan your updates in advance.</li>
<li>Read the <a href="https://www.rockrms.com/releasenotes">release notes</a> to learn more about the latest versions.</li>
</ul>

        <img src="https://feedpress.me/link/5849/17513914.gif" height="1" width="1"/>]]></description>
      <summary>
            A major PHP exploit went public this week. Jon explains why staying current on Rock matters more than ever, and Emily shares how to get the most out of RX26 in Phoenix.
        </summary>
    </item>
    <item>
      <title>We Spent a Church’s Yearly AI Budget in One Weekend. Here’s What We Found | Ep 224</title>
      <guid>b25d2fff-3905-4ad5-a584-d17b6fbd34d9</guid>
      <link>https://feedpress.me/link/5849/17513915/470</link>
      <pubDate>Mon, 12 Oct 2026 15:00:00 -0700</pubDate>
      <description><![CDATA[
            <img src="https://www.rockrms.com/GetImage.ashx?guid=fc931b72-9fbd-4afa-af32-48d77b3f61d5" />
            <br />
            <div style="position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden; margin-bottom: 24px;">
  <iframe
    src="https://www.youtube.com/embed/TTQofWpJ6Ic?si=C838tuvBFhRa4ERi"
    style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"
    frameborder="0"
    allowfullscreen>
  </iframe>
</div>
<p>AI got very good at surfacing security vulnerabilities fast. In this episode of Rock Cast, Jon, Emily, and Nicole share the story behind Rock's recent security releases.</p>
<p>Jon explains how the team built a series of agents to scan Rock's code and why Rock's flexibility makes every fix a balancing act.</p>
<p>The main takeaway here is that security is a two-way street. The core team is working its hardest to roll out fixes, but they only protect your church once you install them. As a Rock admin, here's your 5 step action plan to make sure your church stays protected and secured:</p>
<ol>
<li>Install security releases when they land.</li>
<li>Watch for the red banner on your homepage.</li>
<li>Work through the field types guide and move your Lava over.</li>
<li>Keep cleaning up predictable IDs.</li>
<li>Report security issues through Talos.</li>
</ol>
<h2>Rock Partners</h2>
<p>We are thankful for our Rock Partners and their support of the Rock Community. Visit their websites through the link above to learn how they can help your ministry and confirm that those you work with are as invested in the success of Rock as you are!</p>
<h2>Quick Links

</h2>
<ul>
<li>Read the field types guide, <a href="https://community.rockrms.com/connect/safely-turn-on-field-validation">Safely Turn On Field Validation</a>, and block time on your calendar to test.</li>
<li>Learn how the Community and the Rock team share the work of <a href="https://community.rockrms.com/connect/keeping-rock-secure-together">Keeping Rock Secure</a>.</li>
<li>Visit the <a href="https://www.rockrms.com/releasenotes">release notes</a> to catch up on the latest security updates.</li>
<li>Check out <a href="https://security.rockrms.com">Talos</a>, our new tool for reporting security issues to the core team.</li>
</ul>

        <img src="https://feedpress.me/link/5849/17513915.gif" height="1" width="1"/>]]></description>
      <summary>
            One weekend of AI security scanning cost us more than most churches spend on AI in a year, but this episode explains why every token was worth the investment.
        </summary>
    </item>
    <item>
      <title>Keeping Rock Secure Together</title>
      <guid>a4257476-1eb8-4ca7-8345-9e0cd3321c5b</guid>
      <link>https://feedpress.me/link/5849/17513916/470</link>
      <pubDate>Fri, 02 Oct 2026 13:00:00 -0700</pubDate>
      <description><![CDATA[
            <img src="https://www.rockrms.com/GetImage.ashx?guid=9d2156c6-9e28-4d95-827e-11f1d0670c31" />
            <br />
            <p>For months on Rock Cast, we've been talking about how AI would change security for all software. That shift is here. AI tools are making it easier than ever to find security issues in any platform, and because Rock is open source, anyone can read its code. That openness is one of Rock's greatest strengths, and it also means security is something we build together as a community.</p>
<p>Here's how that partnership works.</p>
<h2>What we do</h2>
<p><b>We make reporting easy and personal.
</b></p>
<p>Our new security reporting tool, <a href="https://security.rockrms.com/">Talos</a>, gives anyone who finds an issue a private, two-way conversation with our team. You'll see your report move from investigation to fix to release, and you'll get updates along the way.</p>
<p><b>We turn around fixes quickly and carefully.
</b></p>
<p>Every report is triaged fast, and many fixes ship within days. Some take longer, because every church hosts its own Rock server, with different versions and customizations. We take the time to build fixes that protect churches without breaking the systems they depend on every week. Security fixes are applied to the latest two versions of Rock so churches on recent major versions can get protected right away.</p>
<p><b>We communicate with you.</b></p>
<p>We alert you to new security patches so you can update quickly. And with our our new Talos reporting system, we'll communicate with you throughout the process from report to release.</p>
<p><b>We keep details quiet.
</b></p>
<p>We don't publicly share the details of security issues. Despite the risk, many churches update on their own schedule, often with small teams or volunteers, and keeping specifics private protects them while they catch up.</p>
<h2>What you do</h2>
<p><b>Update all the way, and keep updating.
</b></p>
<p>This is the single most important thing your church can do. Get to the latest version of Rock, then stay in cadence with each release. Every release carries the most current security fixes.</p>
<p><b>Report anything you find through Talos.
</b></p>
<p>If you come across something that looks like a security issue, send it through Talos instead of posting it publicly, in Rocket Chat or on social media. That keeps other churches safe while we work on a fix, and it keeps you in the loop from start to finish.</p>
<p><b>Stay up to Date with Best Practices</b></p>
<p>Be sure to keep up with our blog, Rock Cast, and information from our other platforms so you are always knowledgeable about best practices. Start by reading our <a href="https://community.rockrms.com/connect/safely-turn-on-field-validation">blog on Rock's Field Validation</a>.</p>
<p><b>Ask for help if you need it.</b></p>
<p>
Updating can feel like a big lift, especially for a small team. Several Rock Partners offer update services, and you can find them at <a href="https://www.rockrms.com/partners">https://www.rockrms.com/partners</a>.&nbsp;&nbsp;</p>
<p><b>Consider your whole environment.</b></p>
<p>In addition to keeping Rock updated, be sure to keep up to date with server, network and hosting security, manage user permissions and account access and follow best practices for configuring Rock.</p>
<h2>Stronger together</h2>
<p>Rock was built by the church, for the church, and keeping it secure works the same way. When our team moves quickly and every church stays current, the whole community is safer. Thank you for being part of it.</p>

        <img src="https://feedpress.me/link/5849/17513916.gif" height="1" width="1"/>]]></description>
      <summary>
            As AI makes security issues easier to find in open source software, Rock is teaming up with churches to stay secure through fast fixes, private reporting with the new Talos tool, and regular updates to the latest version.
        </summary>
    </item>
    <item>
      <title>How to Safely Turn On Rock's Field Validation</title>
      <guid>97163aff-1cb2-47d8-9dc9-6d478c61459c</guid>
      <link>https://feedpress.me/link/5849/17513917/470</link>
      <pubDate>Thu, 01 Oct 2026 09:00:00 -0700</pubDate>
      <description><![CDATA[
            <img src="https://www.rockrms.com/GetImage.ashx?guid=c196ef39-7fe9-4b76-82f7-03387c1739ba" />
            <br />
            <p>Server model validation keeps Lava and HTML out of fields that were never meant to hold them. Before you turn it on, Rock shows you what it would likely block, so you can fix each issue first and flip the switch with confidence.</p>
<p>It's a strong layer of protection, but turning it on without preparation could stop a staff member's save in the middle of a busy week. That's why Rock logs first and blocks later. Saves that validation would reject land in your Exception Log, so you can fix the cause long before anyone runs into it.</p>
<p>This post walks through that review: where to find the exceptions, how to read them and how to resolve each one. Most fixes come down to checking&nbsp;<b>Allow Lava</b>&nbsp;or&nbsp;<b>Allow HTML</b>&nbsp;on an attribute. The rest point to a workflow, import or habit that's saving content where it doesn't belong.</p>
<h2>Check Your Version</h2>
<p>Validation logging will be available in Rock 17.9, 18.5, 19.5 and 20.0, plus any later release in each of those version lines. Earlier versions don't log these exceptions.</p>
<h2>Plan on About a Month</h2>
<p>Check the Exception Log once a week for roughly four weeks. That gives your weekly and monthly processes time to run and log anything they would trip over. Here's the full path from first look to fully enabled:</p>
<ol>
<li><b>Review the Exception Log</b> for the two exception types covered in this post.</li>
<li><b>Fix attribute exceptions </b>by adjusting attribute settings or cleaning up the source of the content.</li>
<li><b>Fix property exceptions </b>by updating the workflows, imports, integrations or staff habits that produce them.</li>
<li><b>Confirm the log is quiet. </b>By your last weekly check, aim for zero new validation exceptions, or only ones you've reviewed and are comfortable having blocked.</li>
<li><b>Turn it on. </b>Go to&nbsp;<code>Admin Tools &gt; Settings &gt; Security &gt; Security Settings</code>, check&nbsp;<b>Enable Server Model Validation</b>&nbsp;and save.
</li>
<li><b>Restart Rock. </b>The setting is only read when Rock starts, so it doesn't take effect until the application restarts.</li>
<li><b>Monitor. </b>For the first few weeks, watch the Exception Log and listen for staff reports of saves that fail. Failures are usually logged and point to the exact attribute or field involved.</li>
</ol>
<p>

When you're ready, the setting lives on the Security Settings page.</p>
<p><img src="https://www.rockrms.com/GetImage.ashx?guid=f5c4951d-28e6-4890-90f7-0e79d4fd3716" alt="The Enable Server Model Validation setting checked on the Security Settings page" class="img-responsive"></p>
<h2>Know the Two Exception Types</h2>
<p>Rock logs two kinds of validation exceptions, and each one gets a different fix.</p>
<ul>
<li><b>Attribute Value Validation </b>(<code>Rock.Security.AttributeValueValidationException</code>) means a value saved into an attribute contained something that attribute isn't configured to allow. The most common case by far is Lava or HTML in a Text or Memo attribute.
</li>
<li><b>Property Validation </b>(<code>Rock.Security.PropertyValidationException</code>) means a value saved into one of Rock's built-in fields, such as a person's name, a group's name or a page title, contained something that field never allows.
</li>
</ul>
<p>Validation only runs when something is saved. Records that are never edited won't generate errors, even if they already hold content that isn't allowed, so the log reflects what's actually happening day to day. When a record is saved, the checks work like this:</p>
<ul>
<li><b>Attribute values </b>are checked only when the value is new or has changed. Workflow form fields are the exception: every editable field is checked each time the form is submitted.</li>
<li><b>Built-in fields </b>are all checked whenever the record is saved, not only the ones that changed. If a person's last name already contains HTML, editing only their email address will still log (or, once enabled, block) the save.</li>
</ul>
<h2>Find the Exceptions</h2>
<ol>
<li>Go to&nbsp;<code>Admin Tools &gt; Settings &gt; System &gt; Exception List</code>.
</li>
<li>Enter&nbsp;<code>validationexception</code>&nbsp;in the search box. Look for&nbsp;<code>AttributeValueValidationException</code>&nbsp;and&nbsp;<code>PropertyValidationException</code>&nbsp;in the&nbsp;<b>Type</b>&nbsp;column. Other types that match the search aren't covered here.
</li>
<li>Use the&nbsp;<b>Description</b>&nbsp;column to see which attribute or property is affected.
</li>
</ol>
<p><img src="https://www.rockrms.com/GetImage.ashx?guid=1f9ccc44-77b6-4d87-8a6c-d711e523c5ff" alt="The Exception List filtered to validation exceptions, showing one attribute exception and one property exception" class="img-responsive"></p>
<p>

Select any exception to see each occurrence, including the page URL and stack trace, when you need to know where it came from.</p>
<h2>Read the Message</h2>
<h3>Attribute Exceptions</h3>
<pre class=""><code class="language">The value of the &#39;&lt;Attribute Name&gt;&#39; attribute (id: &lt;AttributeId&gt;) on &lt;Entity Type&gt; id &lt;EntityId&gt; &lt;reason&gt;.
</code></pre>
<p>For example:</p>
<blockquote>
<p>The value of the 'Breaking Changes' attribute (id: 15610) on Rock.Model.DefinedValue id 8110 may not contain HTML tags.</p>
</blockquote>
<ul>
<li><b>Attribute name and id </b>tell you exactly which attribute to fix.</li>
<li><b>Entity type </b>tells you what kind of record the attribute belongs to, which helps you find it.</li>
<li><b>Entity id </b>is the specific record that was being saved, useful for looking at the actual value.</li>
<li><b>Reason</b> tells you what kind of content was rejected.</li>
</ul>
<p>

Global attributes use a slightly different format:&nbsp;<code>The value of the '&lt;Name&gt;' global attribute (id: &lt;Id&gt;) on entity id 0 &lt;reason&gt;.</code></p>
<h3>Property Exceptions</h3>
<pre class=""><code class="language">The value of the &#39;&lt;Property Name&gt;&#39; property on &lt;Entity Type&gt; &lt;reason&gt;.
</code></pre>
<p>For example:</p>
<blockquote>
<p>The value of the 'Name' property on LearningActivity may not contain Lava commands.</p>
</blockquote>
<p>These refer to a built-in field on the entity, not an attribute, and they're fixed at the source. See&nbsp;<b>Fix Property Exceptions</b>&nbsp;later in this post.</p>
<h2>Fix Attribute Exceptions</h2>
<h3>Decide Whether the Content Belongs There</h3>
<p>Before changing anything, look at the value that was saved if you can, and ask one question: is this attribute meant to hold Lava or HTML?</p>
<ul>
<li><b>Yes, it's expected. </b>A group type attribute that holds a Lava template for a welcome email, or a content channel attribute that holds formatted text. Turn on the matching option.</li>
<li><b>No, it arrived by accident. </b>Someone pasted formatted text into a plain text field, or a workflow wrote output that still contained unresolved Lava. Fix the source and leave the attribute locked down.</li>
</ul>
<p>Turning on Allow Lava or Allow HTML loosens protection on that attribute. Only turn them on where the content is genuinely expected, and take extra care with attributes the public can edit, such as registration forms, workflow entry forms on your external site and public profile editing.</p>
<h3>Choose the Fix</h3>
<p>Turn on only the option that matches the reason in the message:&nbsp;<b>Allow Lava</b>&nbsp;for Lava,&nbsp;<b>Allow HTML</b>&nbsp;for HTML tags. Which options you'll see depends on the field type.</p>
<ul>
<li><b>Text </b>offers Allow Lava and Allow HTML. These options have no effect when the attribute is marked as a first name field.</li>
<li><b>Value List </b>offers Allow Lava and Allow HTML.</li>
<li><b>Memo </b>offers Allow HTML. Memo attributes always allow Lava.</li>
<li><b>Other field types </b>don't have these options. Fix the source instead.</li>
</ul>
<p>If the reason in the message is anything other than Lava or HTML tags, treat it as a source problem. That content isn't allowed in these field types even with both options on.</p>
<p>A few field types are unrestricted and never generate these exceptions: HTML, Code Editor, Lava and Structured Content Editor. Markdown allows Lava and basic HTML.</p>
<p>Keep in mind that Lava detection is a simple text check. Any value containing&nbsp;<code>{{</code>,&nbsp;<code>{%</code>&nbsp;or&nbsp;<code>{[</code>&nbsp;counts as Lava, even if it wasn't meant as Lava, such as JSON or text copied from a template. The fix is the same: turn on Allow Lava if that content is expected.</p>
<h3>Find and Edit the Attribute</h3>
<p>If you already know where the attribute is managed, such as on a defined type or a workflow type, edit it there. Otherwise, the Entity Attributes page lists every attribute in Rock and is the quickest way to track one down.</p>
<ol>
<li>Go to&nbsp;<code>Admin Tools &gt; Settings &gt; System &gt; Entity Attributes</code>.
</li>
<li>Set&nbsp;<b>Entity Type</b>&nbsp;to the entity type from the exception message. For example,&nbsp;<code>Rock.Model.DefinedValue</code>&nbsp;is&nbsp;<b>Defined Value</b>. For global attributes, choose&nbsp;<b>Global Attributes</b>.
</li>
<li>Enter part of the attribute name in the search box.</li>
<li>If more than one attribute matches, use the&nbsp;<b>Id</b>&nbsp;column to pick the one whose id matches the exception message.
</li>
</ol>
<p>In the following example, two Defined Value attributes are named "Breaking Changes." The exception message said&nbsp;<code>(id: 15610)</code>, so the first row is the one to edit.</p>
<p><img src="https://www.rockrms.com/GetImage.ashx?guid=dba36d94-1769-49f4-8e2a-0f9af066b062" alt="The Entity Attributes page filtered to two Defined Value attributes named Breaking Changes, with Ids 15610 and 25096" class="img-responsive"></p>
<p>If the entity type is&nbsp;<code>Rock.Model.Block</code>,&nbsp;<code>Rock.Model.WorkflowActionType</code>&nbsp;or another component whose attributes are defined in code, don't edit the attribute. See&nbsp;<b>Attributes Defined in Code</b>&nbsp;later in this section.</p>
<p>To make the change:</p>
<ol>
<li>Select the edit (pencil) icon on the attribute row.</li>
<li>In the field type configuration area under the Field Type selection, check&nbsp;<b>Allow Lava</b>, <b>Allow HTML</b> or both, based on the reason in the message.
</li>
<li>Save the attribute.</li>
</ol>
<p>The following example is a Memo attribute, so only&nbsp;<b>Allow HTML</b>&nbsp;appears. Text and Value List attributes show&nbsp;<b>Allow Lava</b>&nbsp;in the same area.</p>
<p><img src="https://www.rockrms.com/GetImage.ashx?guid=ae8cbc62-a079-41ba-b061-383bd60e469d" alt="Editing the Breaking Changes Memo attribute with Allow HTML checked" class="img-responsive"></p>
<p>The change takes effect immediately. No restart is required.</p>
<h3>Confirm the Fix</h3>
<p>Re-save one of the affected records, or re-run the process that produced the value, and confirm no new exception is logged for that attribute. Existing log entries don't clear on their own, so note the time you made the fix and only look at entries logged after it.</p>
<h3>Attributes Defined in Code</h3>
<p>Attributes on blocks, workflow actions, jobs and other components are declared in code. If one of these shows up in the log with reasonable content, such as a block setting meant to hold a Lava template, the attribute definition likely needs to be updated to allow that content. This is usually a simple oversight.</p>
<ul>
<li>If it comes from core Rock, report it on the&nbsp;<a href="https://github.com/SparkDevNetwork/Rock/issues">Rock issue tracker</a> with your Rock version and the full exception message.</li>
<li>If it comes from a plugin, report it to the plugin's author.</li>
</ul>
<h2>Fix Property Exceptions</h2>
<p>Built-in properties have fixed rules that can't be changed through settings. A person's name, for example, will never allow HTML. To resolve these, find and change whatever is putting the content there.</p>
<h3>Change the Process</h3>
<ul>
<li><b>Workflows:</b> make sure Lava used to set names, titles or other simple fields outputs plain text. Use filters such as&nbsp;<code>StripHtml</code>&nbsp;where formatted content might sneak in.
</li>
<li><b>Imports and integrations:</b> clean or strip formatting from the source data before it's sent to Rock.
</li>
<li><b>Lava templates: </b>check that entity commands set only plain values on simple properties.
</li>
<li><b>Staff habits:</b> train staff to paste as plain text (Ctrl+Shift+V in most browsers) when entering names and titles, and to avoid copying from word processors or emails into simple fields.</li>
<li><b>Plugins:</b> contact the plugin's author.</li>
</ul>
<h3>Clean Up Existing Data</h3>
<p>Changing the process stops new invalid content, but records that already contain it will keep reporting the same error every time they're saved, even when the invalid field wasn't touched. Once validation is enabled, those saves will fail. Clean up the existing data, or expect these errors to keep appearing until you do.</p>
<h3>Confirm the Fix</h3>
<p>Note the time of the fix and confirm no new entries appear for that property afterward, other than from records you haven't cleaned up yet.</p>
<h2>Turn It On</h2>
<p>Once no new validation exceptions are being logged, or only ones you've reviewed and are comfortable having blocked, go to&nbsp;<code>Admin Tools &gt; Settings &gt; Security &gt; Security Settings</code>, check&nbsp;<b>Enable Server Model Validation</b>, save and restart Rock. Keep an eye on the Exception Log for the next few weeks, and you'll catch anything that didn't come up during your review.</p>
<h2>For Plugin Developers</h2>
<p>This section is for plugin developers. If you don't write plugins, you can skip it.</p>
<p>Validation covers string properties on entity models and attribute values, in plugins as well as core Rock. Test your plugin on a development server with&nbsp;<b>Enable Server Model Validation</b>&nbsp;turned on so problems surface as failed saves rather than log entries.</p>
<h3>Model Properties</h3>
<p>Declare what each string property is meant to hold with the&nbsp;<code>[StringValidation]</code>&nbsp;attribute (<code>Rock.Security</code>) and a&nbsp;<code>StringValidationProfile</code>&nbsp;(<code>Rock.Enums.Security</code>).</p>
<table class="table table-bordered table-striped">
<thead>
<tr><th>Profile</th><th>Intended for</th></tr>
</thead>
<tbody>
<tr><td><code class="inline-code">PlainText</code></td><td>Ordinary text with no formatting.</td></tr>
<tr><td><code class="inline-code">Name</code></td><td>Names of people, groups and similar values. Stricter than&nbsp;<code>PlainText</code>.&nbsp;&nbsp;</td></tr>
<tr><td><code class="inline-code">BasicHtml</code></td><td>Short formatted text that should not contain Lava.</td></tr>
<tr><td><code class="inline-code">LavaAndBasicHtml</code></td><td>Formatted text or templates that may contain Lava.</td></tr>
<tr><td><code class="inline-code">Unrestricted</code></td><td>Content edited only by trusted administrators, such as raw templates or code.</td></tr>
</tbody>
</table>
<p>For example, a <code>Name</code> property that holds a person's name and a <code>Description</code> property that holds formatted text look like this:</p>
<pre class=""><code class="language">[DataMember]
[StringValidation( StringValidationProfile.Name )]
public string Name { get; set; }

[DataMember]
[StringValidation( StringValidationProfile.LavaAndBasicHtml )]
public string Description { get; set; }</code></pre>
<ul>
<li><b>Only decorated properties are checked, for now. </b>A string property without <code>[StringValidation]</code> isn't validated today, so existing plugins keep working. In a future version, undecorated properties will be treated as <code>PlainText</code>. Decorate every string property on your models now, especially any that need to hold HTML or Lava, so your plugin keeps working when that change arrives.
</li>
<li>The property must also have <code>[DataMember]</code>, must not have <code>[NotMapped]</code> and must have a public setter.
</li>
<li>Choose the most restrictive profile that fits the data. Use&nbsp;<code>Unrestricted</code> sparingly.
</li>
<li> ExcludedRules and <code>AdditionalRules</code> fine-tune a profile for a single property when none of the profiles fit exactly. Use these sparingly as well.</li>
</ul>
<h3>

Attributes Declared in Code</h3>
<p>Block settings, workflow action settings, jobs and other components are validated with the same Allow HTML and Allow Lava options covered earlier. If an attribute is meant to hold HTML or Lava, say so in its declaration:</p>
<pre class=""><code class="language">[TextField( &quot;Welcome Message&quot;,
    Key = AttributeKey.WelcomeMessage,
    AllowHtml = true,
    AllowLava = true )]

[MemoField( &quot;Summary Template&quot;,
    Key = AttributeKey.SummaryTemplate,
    AllowHtml = true )]</code></pre>
<p><code>TextFieldAttribute</code>&nbsp;and&nbsp;<code>ValueListFieldAttribute</code>&nbsp;support both&nbsp;<code>AllowHtml</code>&nbsp;and&nbsp;<code>AllowLava</code>.&nbsp;<code>MemoFieldAttribute</code>&nbsp;supports&nbsp;<code>AllowHtml</code>&nbsp;and always allows Lava. For settings that hold full templates or code, use a field type built for it, such as&nbsp;<code>CodeEditorField</code>&nbsp;or&nbsp;<code>LavaField</code>.</p>

        <img src="https://feedpress.me/link/5849/17513917.gif" height="1" width="1"/>]]></description>
      <summary>
            Safely turn on Rock's field validation with confidence! This keeps Lava and HTML out of fields that shouldn't hold them. Learn how to find and fix what it would block before you flip the switch in our new guide.
        </summary>
    </item>
    <item>
      <title>Daydreams of Multiplayer Agents and (Maybe) the End of Duplicate Records | Ep 223</title>
      <guid>ec5277b5-a800-4866-88ac-c3a98a09bdc3</guid>
      <link>https://feedpress.me/link/5849/17513918/470</link>
      <pubDate>Tue, 22 Sep 2026 10:50:00 -0700</pubDate>
      <description><![CDATA[
            <img src="https://www.rockrms.com/GetImage.ashx?guid=b836b80e-6cdc-4b38-952c-64c18f13c3a1" />
            <br />
            <div style="position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden; margin-bottom: 24px;">
  <iframe
    src="https://www.youtube.com/embed/0cIpEpUzQN0?si=Od1fmw4xt9hnWkie"
    style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"
    frameborder="0"
    allowfullscreen>
  </iframe>
</div>
<p>In this episode of Rock Cast, the team talks about the next unlock for AI Agents, especially after a long 3-month period of limited progress in the industry around harnesses. Instead of working with personal agents in a private chat, imagine collaborating with your team by sharing a live agent workspace. This is the transition from single-player agents to multiplayer agents, and it will dramatically change the way your team works.</p>
<p>Then, they&nbsp;pull back the curtain on a problem every Rock church experiences: duplicate records. They invite listeners to brainstorm early product thinking and daydream about a unique solution: requiring verification for phone numbers and emails when adding a record. Jon and Emily are careful not to promise any guarantees, but allow listeners a peek into the crucible process, that is, the refinement and testing of all ideas.</p>
<p>Give this episode a listen, then head to the <a href="https://chat.rockrms.com/channel/rock-cast">Rock Cast channel</a> to see what other churches are saying about this possible solution.</p>
<h2><a href="https://www.rockrms.com/partners">Rock Partners</a></h2>
<p>We are thankful for our Rock Partners and their support of the Rock Community. Visit their websites through the link above to learn how they can help your ministry and confirm that those you work with are as invested in the success of Rock as you are!</p>
<h2>Quicklinks</h2>
<ul>
<li>Read the complete article on Sergey Karayev's <a href="https://x.com/jonedmiston/status/2101347637295513758?s=20">Multiplayer AI Manifesto</a>.</li>
<li>Invite your leadership to <a href="https://rx.rockrms.com/rock_blog26">RX26 Vision Day</a>, and grab your hotel room before they all fill up.</li>
</ul>

        <img src="https://feedpress.me/link/5849/17513918.gif" height="1" width="1"/>]]></description>
      <summary>
            This week the team dreams up a future with multiplayer agents and the solution for eliminating duplicate records in Rock.
        </summary>
    </item>
    <item>
      <title>Why Your Pitches Aren't Making it to the Elevator | Ep 222</title>
      <guid>cf516338-efb2-4c52-ad3e-6b1c2b98a33a</guid>
      <link>https://feedpress.me/link/5849/17513919/470</link>
      <pubDate>Fri, 11 Sep 2026 10:37:00 -0700</pubDate>
      <description><![CDATA[
            <img src="https://www.rockrms.com/GetImage.ashx?guid=bc6fafad-d566-4a7d-93f6-944ffabd5290" />
            <br />
            <div style="position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden; margin-bottom: 24px;">
  <iframe
    src="https://www.youtube.com/embed/4hJ0g7lDhAI?si=nOVQxpwVTnETqYcF"
    style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"
    frameborder="0"
    allowfullscreen>
  </iframe>
</div>
<p>You have a good idea and you've thought it through. You're ready to pitch it, but it gets shut down. In this episode, we cover the gap between having an idea and selling one.</p>
<p> Spoiler: they're not the same skill.</p>
<p>Speaking from lessons learned in their careers, Jon and Emily walk through 12 reasons why some ideas never get a seat at the table. They share tried-and-true strategies for what does work and what happens after the pitch actually lands.</p>
<p>Emily and Nicole add real examples from church and organizational work, and Jon closes with a line that sums it all up: a good idea poorly communicated is a missed opportunity. A bad idea communicated well is a landmine.</p>
<p>This isn't a talent you're born with. It's a skill you train for. Watch the latest episode to learn how to master the art of selling your ideas.</p>
<h2><a href="https://www.rockrms.com/partners">Rock Partners</a></h2>
<p>We are thankful for our Rock Partners and their support of the Rock Community. Visit their websites through the link above to learn how they can help your ministry and confirm that those you work with are as invested in the success of Rock as you are!</p>
<h2>Quick Links</h2>
<ul>
<li>See an example of how Wes Kao uses the <a href="https://x.com/wes_kao/status/1597610726700765184?s=20">Action Method framework</a> for communicating ideas.</li>
<li>There are only <a href="https://rx.rockrms.com/rock_blog26">3 days left to register</a> for General Ticket pricing before September 15. Don't forget to book your stay at our final hotel, <a href="https://www.hyatt.com/events/en-US/group-booking/PHXZD/G-SPK6">The Hyatt Place</a>, which is already a third full.</li>
<li>Submissions for <a href="https://rx.rockrms.com/rxawards">Gold Circle Awards</a> end on September 18. Submit your inspiring Rock-powered digital ministry project before then for consideration.</li>
</ul>

        <img src="https://feedpress.me/link/5849/17513919.gif" height="1" width="1"/>]]></description>
      <summary>
            Having an idea and selling the idea are two completely different skills most people don't actually train for. Speaking from lessons learned in their careers, Jon and Emily walk through 12 reasons why some ideas never get a seat at the table.
        </summary>
    </item>
    <item>
      <title>Stop the Slop: How We're Keeping AI Out of Our Blind Spots | Ep 221</title>
      <guid>fd5827c7-0c64-4a79-ab1a-c5c412c1df34</guid>
      <link>https://feedpress.me/link/5849/17513920/470</link>
      <pubDate>Fri, 21 Aug 2026 15:20:00 -0700</pubDate>
      <description><![CDATA[
            <img src="https://www.rockrms.com/GetImage.ashx?guid=8ceea024-cf27-480e-8e1a-db3030ffa9a5" />
            <br />
            <div style="position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden; margin-bottom: 24px;">
  <iframe
    src="https://www.youtube.com/embed/F8HUXDXSW4A?si=XKNt0If_Je2WJ8kQ"
    style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"
    frameborder="0"
    allowfullscreen>
  </iframe>
</div>
<p>AI slop isn't a writing problem; it's an effort problem that shows up when we outsource our thinking to the model.</p>
<p>On this episode, the team walks through what AI slop actually is, how we're keeping it out of own channels, and practical tools like a viral AI Writing Policy and skills our team uses internally to help you stop the slop.</p>
<p>Jon kicks off with version updates including v19.4 in beta with AI agents coming very soon, Rock IQ, and v20 development. He shares his hot take on AI slop framing it as a human problem rather than a technology problem.</p>
<p>Nicole walks through the Write-Like-Me skill, which is an internal tool used to speed up drafting communications in your real voice while stripping generic AI output. It's refinable over time and we're giving it away for free. Find it in the shownotes.</p>
<p>Emily brings in Extreme Ownership, applying Jocko Willink's stewardship principle to Rock admins. There are no bad teams, only bad leaders, and there is no AI slop problem, only a review process nobody is enforcing. Download the resources and listen to this episode to learn how you can apply them.</p>
<h2><a href="https://www.rockrms.com/partners">Rock Partners</a></h2>
<p>We are thankful for our Rock Partners and their support of the Rock Community. Visit their websites through the link above to learn how they can help your ministry and confirm that those you work with are as invested in the success of Rock as you are!</p>
<h2>Quick Links</h2>
<ul>
<li>Read <a href="https://a.co/d/07xFwY50">Extreme Ownership</a> by Jocko Willink, retired Navy SEAL commander, on the leadership principle we applied in this episode.</li>
<li>Adapt <a href="https://www.linkedin.com/feed/update/urn:li:activity:7492584311087542272/">Clay's AI Writing Policy</a> for your team to guide their writing output.</li>
<li>View the RX26 schedule, submit your Gold Circle Awards by Sept 18, and join the Content Subscription waitlist.
</li>
<li>Download the Build My Style Guide skill and the Write Like Me skill to help your team stop the slop.</li>
</ul>
<div class="structuredcontent-attachment"><div class="structuredcontent-attachment-fileicon"><div class="structuredcontent-attachment-fileicon-background"></div><div class="structuredcontent-attachment-fileicon-label" title="zip">zip</div></div><div class="structuredcontent-attachment-fileinfo"><div class="structuredcontent-attachment-fileinfo-title">Stop_The_Slop_Skills.zip</div><div class="structuredcontent-attachment-fileinfo-size" data-size="KiB">206.3</div></div><a class="structuredcontent-attachment-download" href="https://www.rockrms.com/GetFile.ashx?guid=347d00c3-365e-4d4a-b62d-3df892ebfb0f" target="_blank" rel="nofollow noindex noreferer"><svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="icon icon-tabler icons-tabler-outline icon-tabler-download"><path d="M4 17v2a2 2 0 0 0 2 2h12a2 2 0 0 0 2 -2v-2"></path><path d="M7 11l5 5l5 -5"></path><path d="M12 4l0 12"></path></svg></a></div>
        <img src="https://feedpress.me/link/5849/17513920.gif" height="1" width="1"/>]]></description>
      <summary>
            This episode is packed with practical tools to help your team stop the slop. You'll find an AI Writing Policy template that went viral for good reason, and skills our team uses internally to keep the generic AI output away from our channels.
        </summary>
    </item>
  </channel>
</rss>
