Community Session: Protect your applications from your own users

Hi everyone. Wow, so nice to see so many of you here already. Welcome to another Versel community session. Very excited to have you all here. Um, we're actually

on fire this week. This would be our third community session of the week. Um you um may have seen um everyone in my team do a session this week and now we're going to end it with just me. Um so if this is your first time in one of our sessions, hi, I'm Pauline. Um you may have seen me around floating around the community space answering questions. And so this is always a great

opportunity to connect with our community, our customers, and our users live. Um, if you are in our community space and want to um chat and engage with with us uh throughout the session, drop a message in the in the chat and let us know where you're uh tuning in from. If you can't see the chat, uh join our community space over at community.versal.com. Um and on the top you should see a banner uh that links back to this um to

this stream. And then you just click on going using your Versal account. Um, amazing. So excited to see so many of you here already. Um, so just a reminder if you are going to engage with us in the community chat. Um, make sure to adhere to our code of conduct to make sure that we continue to run these um, sessions. Amazing. With all of that out of the way, um I'm so excited for

today's community session. We have James from uh UNI who will be talking about um how to protect your applications from your own users. I'm very very excited about this session. Um welcome James. Hi. Hello. Hello. Thanks for having me. I'm glad we finally got this organized and I know we kept moving it for a while, right? Yep. Yep. Yep. And I apologize if my

voice is a bit uh horseo. I've been at conference for two days. So this is the second day after the conference. So we'll see how it goes. But we should be I mean I saw the pictures on X and it looked good. So I hope you had a good time. I had a really really good time. It was one of my it's my favorite conference to go to pretty much every year that isn't like run by like big bigger companies. It's like all community based open source. So, it's always fun to go to. Yeah. Which one was that one again?

It's All Things Open. Nice. If you attended All Things Open and saw James, drop it in the chat and let us know. Um, awesome. With that, James, I will leave you to um chat about your talk. Cool. Yeah. So, we're going to talk about protecting your applications from your own users today. Um, basically, it's always the theory of users are great until they aren't. Um, and most of that time comes down to them

accidentally doing something that you didn't want them to or potentially they could be doing, you know, something that is caused by your own UI or your UX. So, first thing we want to talk about, rage clicks. Now, if you don't know what rage click is, it's usually what happens when users end up clicking on a form, a button, or something on the screen because it doesn't work the way they expected to. Maybe there's not a loader, maybe there's no confirmation that you've actually filled out a form, things like that. And that usually ends