Video: Troubleshooting Blackbaud ID from the Blackbaud K-12 Solutions School Office | Duration: 2556s | Summary: Troubleshooting Blackbaud ID from the Blackbaud K-12 Solutions School Office | Chapters: Introduction and Housekeeping (5.6s), Speaker Introductions (108.54s), Blackbaud ID Basics (186.98499s), Blackbaud ID Username (343.095s), Account Inactivation Logic (426.93832s), Blackbaud ID Updates (898.175s), Authentication Troubleshooting Guide (1043.375s), Troubleshooting Login Issues (1497.03s), MFA and SSO (1595.92s), Sign-In System Reminders (1670.115s), Support Case Guidelines (1768.02s), Parent Email Management (2154.6301s), Blackbaud ID Update (2215.17s), SSO Login Considerations (2274.63s), Email and Account Considerations (2336.435s), Mobile Authentication Issues (2395.5251s), Webinar Conclusion (2503.075s)
Transcript for "Troubleshooting Blackbaud ID from the Blackbaud K-12 Solutions School Office":
Hey, everyone. Thank you so much for joining us today to talk about Blackbaud ID and education man and Jesse Walters, and I'm joined by Natasha Paiva. And we are gonna kick this off by talking about some housekeeping items first, and then we are gonna go real fast through this content today because we have a lot to share. So first up for webinar housekeeping, audio for this webinar is being broadcast through your computer speakers. Hopefully, you can hear me or sad day if you can't. But as we are going along, if you have any issues with the slides progressing or with your audio, if you will refresh your browser tab, that should take care of any issues that you have there. The most common question we receive with any webinar is, is this being recorded? Will I be able to watch this later? The answer is absolutely. You will receive a follow-up email about an hour. I think after the the webinar ends, you will receive a link to that recorded session. You can always go back and, go through the registration page to get to it again that way as well. But, yes, you will receive a recording of the webinar. You can download the slides over on the docs tab. If you click on docs, which is between chat and q and a, you'll see the slides for today's webinar along with a couple of other resources that we put out there for you. And if you want us to answer questions that you have, please submit those under q and a and not under the chat. The chat is not being supervised by anyone at Blackbaud, so we will not see your questions there in the chat. So if you were wanting us to answer any questions, please put those under the q and a, which is where you see that red arrow. And then if you have any, settings that you would like to adjust, you can do that from the settings cogwheel down there at the bottom. Let's go. As I said, my name is Jessie Walters, and I am the product manager for Core in education management. I come from a Blackbaud customer. I implemented the solutions, fell in love with Blackbaud, which is ultimately why I'm here today. And, Natasha, do you want to introduce yourself? Yeah. Sure. Hi, everyone. My name is Natasha Paiva. I am the senior principal for customer support for Blackbaud ID. I'm also a former educator. I used to teach English as a second language, in a high school setting, and I fell in love with technology and turned into a techno technology wizard, which is why I'm here today and working for Blackbaud. Excited to work with you all today. When I have questions about VV ID, I'm pinging Natasha going. So remind me, and she can always answer that question. So I'm thrilled to have you with me today. Yeah. So in our, in our webinar today, we're gonna talk about what we've heard from you, with your feedback and what we're doing in response to that. We are going to talk about some of the new authentication types that were just recently, released as supported through Blackbaud ID. We'll talk about some branding updates that were recently recently released as well. And then Natasha is gonna take you through a troubleshooting wheel, of tips and tricks that you can use to help folks resolve their BBID problem. But things came up at BBCon. I hope you were there with us last week, but I got a lot of feedback about BBID. So we're gonna start with Blackbaud ID one zero one first before we get into the rest of our actual plan agenda. Good thing I could do this up until 10:30 last night. So to start, let's talk about the core account for your users and how that is not the same as your BDID account. They work together hand in hand, but they are not the same. So the screenshot that you see right here is actually from app.blackbaud.com. So if someone were to go in through Blackbaud.com and sign in because they remember the Blackbaud ID was a thing, but they don't remember exactly what it was, they would land here. Their profile that they see here with their, name and their email address is really all that BBID stores about that person. It's just that that account is linked to permissions and to organizations where they have a relationship. If I were to click on profile, that's gonna bring up another page that has my personal information, which is just my name, and it also has my sign in email and my authentication type. So whenever we'll talk about this more later. We are going to talk about redaction. But when someone is redacted, it's the BBID account, name, and email. It doesn't touch the core account anymore. But, again, we're gonna talk about inactivations and redactions more in a minute. But the BBID account, again, is out there under app.blackbaud.com. It doesn't do much. It doesn't do much of anything with core, except that it's so foundational to the way that core works. So when you go into core, if you're looking at a core account, core has all the things from education management. So all of your your user records and all of the information that you have about a user or a student in education management is going to be tied to that core account. Core talks to BBID using the Blackbaud ID username that's down there on the right hand corner. And if you need to know what someone's authentication status is or how they're logging in using Blackbaud ID, If you are a solution admin, most platform managers or many platform managers are, you can click on that tiny little question mark that's right next to authentication status, and it will open a window, that will tell you what the authentication type is and whether or not that user has multifactor authentication either enforced, enabled, or not on at all. But the the email is what's used to connect someone to Blackbaud ID, and it will propagate through the Blackbaud ID username and also into the username field. This next slide is really just included for your reference. I know that it is a bit of an eye chart, but the Blackbaud ID username accepts the email from the user's contact card into the Blackbaud ID username. History lesson, this used to be, separate from the username because we used to have legacy username and password control, but now it's all using Blackbaud ID, and so we've also continued to clean up our processes. So if someone is connected to Blackbaud, that Blackbaud username and the actual username field will be the same value. Legacy username is used to hold the what the username used to be. So if you've been with us since longer than twenty twenty thirty, many of your users will have a legacy username. Users moving forward will probably not have a legacy username. And, again, legacy username and username are relics of the past, and they're also used for many integrations. I put this slide together for your reference. You can go to the docs tab between chat and q and a and grab today's slides and download them, and you'll have this to take away from home. Also, ask from you, if you see somewhere that username, single single word, is is being used interchangeably and incorrectly with user space name, meaning the name of the user, send me an email and let me know because that drives me nuts. They are not the same. Okay. So recently, we made a change to our inactivation logic to help make sure that only the accounts which should have active access to education management would remain active with the ability to log in to your to your school and access information. The inactivation logic and core was already applied years ago. The recent change is that we no longer excluded accounts that were logging in through Blackbaud. And so when we talk about inactivated, let's talk about what that means. When an account is inactivated, it means that all we've done is taken that little disabled account bubble that normally says no when people can log in, and we've toggled it over to yes. So that account has been disabled, but we are logging that separately from when a user takes action to disable the account and when that user is inactivated by the system. So if you're looking at at someone and their account is disabled, pay attention to whether it says disabled by the name of a person or inactivated by the Blackbaud system. Inactivation only happens as a result of inactivity in a span of more than thirteen months. If it's been more than thirteen months and they haven't logged in, they're they're not really considered a current active user. So inactivation is done by the system, whereas disabled is the action that's taken by an admin. The result is the same. If they log in through Blackbaud ID and they land at your school's, instance or your, your myschoolapp.com, they won't be able to get in. When an account is inactivated or disabled, in both cases, that link from the BBID profile that we saw at the beginning to the school is removed. So that if they happen to land at blackbaud.com and they're logged in, they're not gonna see a link that they click on and then they come over and they get disabled. That would just be confusing and frustrating. Inactivate only happens in core. It doesn't do anything to the BBID account. It doesn't do anything to their account in tuition management. If they're using the same BBID to log in to your financial agent next to your financial agent next to it doesn't do anything to those accounts either. Our inactivation logic in core is really just meant to core, and the only thing that we do externally is remove that link from BBID to education. To Blackbaud ID, they have a couple of things that are happening. After six months with no login activity, Blackbaud ID is gonna go ahead and require a password reset on those accounts that are using a username and password, and that's to ensure that the account hasn't been hijacked by some kind of a threat actor and to make sure that that account remains secure. So they're gonna have to go back through the process to establish a new password and confirm that they still have access to that email address. If they get up to two years later and Blackbaud ID has no logins from any solution at all, there's no Blackbaud ID login, that account is going to be redacted, and this has a lot to do with, US privacy laws for Blackbaud ID. But the Blackbaud ID will only be redacted if it's been two years with no logins anywhere to any Blackbaud solution, and there's no link of that Blackbaud ID to, to any school or any organization using RE or FE or tuition management or education management. So what we saw is when we updated our inactivation logic to, inactivate accounts and core, The Blackbaud ID to school link was removed, which means that users who had been previously linked and had been logging in for three or four years were suddenly redacted because Blackbaud ID didn't have a link. It's like, okay. There's no school. There's no association. This person isn't logging in. They're redacted. The good news is that it doesn't impact the user moving forward because they can still use their email address. The unfortunate thing that that did is made it really difficult for school admins to to manage those accounts and make sure that all of the right people that they need to have access to their solutions are able to do so. So I am going to skip ahead a little bit and which is for Natasha's reference. Skipping ahead. We'll go back in a second. But let's talk about that. So one of the things that we heard out of out of that situation is, dude, give me a heads up. I need more than a day after the release notes, to react to this information whenever it goes out. I hear you, and I've asked, like, five people to help me remember and to be especially mindful whenever things like this are going out so we can be sure that that doesn't happen again. One of the other common themes I heard is that you need to know when somebody is approaching inactivation. So if you need to touch or pull one of the levers to help make sure that the inactivation timer is reset so somebody remains able to log in because they should remain able to log in, you need to be able to see that. So as of today, the last login date is now available on the Blackbaud ID authentication page so that you are able to see of all of your users who are logging in how long has it been since their last login. You also need to be able to bulk re enable accounts that have been inactivated by the system. That's especially important as you approach contract season and have enrollment contracts that'll be going out to families, especially those folks who only log in once a year when they have to sign that enrollment contract. So also released today, we've made it possible not only to enable accounts in bulk, but also to disable those accounts too. So if you see that there are some accounts that have been inactivated and you see, yeah, this person is a is a past parent or the they're a parent of a past candidate, they're not logging in anymore, you could go ahead and and fully disable them so that you know that you've reviewed them, they no longer need to be able to log in to education management. Also, one of the common cases we hear is that schools often want to shut down access to the portal whenever you're trying to manage access to schedules for the summer. Schedules are fun. Schedules are sensitive. Everyone has feelings about schedules, and so you might want to just be able to shut off logins for a little bit, but not remove the Blackbaud ID. The good news is that disabling an account doesn't touch the Blackbaud ID connection. And so you can disable an account. You can enable an account. It doesn't do anything different to the Blackbaud ID than what was already there. So this also means that in addition to being able to activate accounts as needed ahead of contract season, you can also disable and then re enable accounts as you're trying to manage access to schedules in, over the summer when you're building those schedules. Fourth thing that we heard, which is kind of annoying, make the list sticky. Keep my filters if I have to navigate away from the Blackbaud ID authentication list and then come back. You got it. We're working on it right now. And stop redacting my users. Done. As of a few weeks ago, we are no longer accepting that redacted value in the username field. We are just we will soon be disconnecting them from Blackbaud ID, leaving the username in place, and giving you a reason that explains where that came from. Were they redacted? Did they request it? Did they ask to be forgotten by Blackbaud, which is a whole other can of worms. But you'll have some context about why that happened and why the system had to kick that off. So there is a lot more to know about that. In the docs that we've shared, we have a link to a community blog post that has a ton of detail. In that blog post, we have a table there that shows a lot of different scenarios of when someone would or would not be inactivated in BIM, when they would or would not be redacted, in Blackbaud ID, and how that would go across on different timelines. So check out that community blog. There's a lot of good information in there, including additional updates planned for the Blackbaud ID authentication area. Okay. I made it through that section faster than I thought it would. You did it. I'm proud of you. Thanks. Alright. So now to your regularly scheduled, agenda, let's talk about what we've heard from you. I'm gonna pass it over to Natasha to talk about this from the Blackbaud ID team. Thanks, Jesse. So what we previously heard up before in inactive and redacted were issues with Apple sign ins, that the details for users and what type of authentication they're using is very varied and that you also just wanna give people the ability to just start completely fresh. So for Apple sign ins, we've already taken some action here, and, Jesse, you can move into the next slide. I will, talk about this. So for Apple sign ins, we have actually blocked the use of hide my email for any Blackbaud related, domains. So if they're coming from the my school app, if they're coming from anywhere else across Blackbaud, they cannot create a BBID with a hidden Apple ID account any longer. They receive an error saying that the account cannot be created and referring them to go back into the into the page. The second option about the details being buried is actually something that we are in the process of working on together to try to find a solution where a constituent user list can show those authentication details and make it exportable report that your team can use so that you know who to communicate to and let them know that there's an issue happening with that particular sign in method or anything else. And then the final item that you guys asked about was the ability to allow people to start fresh. We have actually developed as a part of the right to be forgotten, GDPR, and COPPA, the ability for users to delete their BBID directly from their BBID profile. However, if you also have a parent or user who can't sign in to their account and needs to delete their account so that they can start fresh, all of the support team has been enabled on the process to request for an account to be deleted from the BBID team. We actually go through this process of verification with the user to make sure that they're okay with us to delete that BBID account so that they can start fresh all over again from the start. So no more I'm stuck in an Apple loop. We can actually remove that account, and they can start all over again. The future work that I've already mentioned is the constituent user list. It's something that we're currently in the process of discovery, trying to identify what's going to be the core information that your team needs surfaced to you so that you can work on it. So please stay tuned for more information there. Our next topic is gonna be oh, go go ahead. Sorry. Last I checked that idea in the IDEO Bank had 78 votes. If you agree and have not yet voted on that idea for having a list or a report of all users by authentication type, go let us know how you feel about it. Please. Please do. And our next item on the agenda is gonna be talking about authentication types, and I'll let Jesse go from here. Sounds great. Thanks, Natasha. So there are a we're gonna talk about new types, some visibility for those types in education, and how you can do a really quick check to see how somebody is authenticating. So, very recently, it was the September, early October, Blackbaud ID made it possible for users to authenticate using sign in with Microsoft or sign in with Facebook or continue with Microsoft, continue with Facebook, where they can use either their Microsoft account or their Facebook account to be able to log in where that is the source of their identity. Their, name and email address is passed over to Blackbaud ID, but it works similarly to sign in with Google, sign in with Apple where, the, it can be any email address, but the password reset is going to belong over in that identity provider. And the good news is that, multifactor or two factor authentication is not going to be enforced with those two options. But a handy thing that Natasha showed me is that you can actually check someone's sign in method. It looks like it's not showing it here. So what you can actually do is open an incognito window in your browser and go all the way out to app.Blackbaud.com. If you don't know how to do incognito, choose a different browser. Like, I'm in Chrome, so I would open up Safari instead since I'm on a Mac. In that separate space from where you're already logged in, go to app.Blackbaud.com and click continue with email. On that page, enter their email and click continue, and what's gonna happen is that it's automatically going to redirect you to wherever they are gonna be authenticating, whether it's Google for signing with Google or Apple for signing with Apple or Microsoft for signing with Microsoft or your identity provider if they're part of your SSO. So you can kind of cheat the system by using that continue with email path to see where they land to identify where should they actually be going to reset their password if they're having trouble with that. We call that smart redirect. And then we also have some recent branding changes that give you control over which authentication types you want to use at your school. So let's talk about some branding updates and where you can configure this, and I'm gonna move really fast so you can get to the troubleshooting portion because Natasha is so good at that. So under, with some of these new branding updates, of course, we have the new, continue with Microsoft, continue with Facebook options, but you can actually sort the order that those sign in options appear on your, Blackbaud ID sign in page if it's a new user. And you can also hide some of those sign in options. So one of the common things we heard is we please, we wanna be able to hide, like, sign in with Apple because that one was was challenging for some folks, and you can do that now. So if you go to, in your solution, if you're in core, if you look up at the omnibar at the top, click admin, go to settings and branding. There are lots of branding options where you can upload logos and change your color and things like that. But if you click on manage brand and sign in, then you're going to see a page that looks like this where it gives you the ability to customize the the summary text at the top of that page. You can include a link to additional documentation that your IT team may have painstakingly created to make it look exactly like your school. You can sort those branding options for the buttons, and you can even hide ones that you don't want to appear. But that might make you go, but wait. What if I hide sign in with Apple and we have people who are using sign in with Apple? The good news is with smart redirect, it's automatically gonna kick them over to sign in with Apple anyway. It just kind of prevents more users from trying to use that sign in with Apple option at your school. There's also some custom text and some custom settings in education management that you can use to customize the label above the, the username box. The more information and docs links that I have on this page are also configurable as well. Plus, if someone were to go to their profile and try to look at their login settings or their account settings, there are, custom text boxes for those areas as well. So make sure you download today's slides from the docs area so that you have these instructions moving forward. And now we will get into troubleshooting. And, Josh, no pressure. No pressure, though. Right? I have seventy to six minutes to go through it. We got it. So, this is a troubleshooting wheel. I've used this for training and teaching all of our, staff across support as well as my staff at previous work and and employment. The top of the wheel is going to always start with environment. The reason why is that there are many environmental factors that can actually impact somebody's capability of signing in. And so your troubleshooting steps should always start with the environment first. Asking questions about their device hardware or network connectivity, their browser that they're using is typically the best place to start. So device hardware questions, things like, are they working on a device that's owned by them or potentially managed by their IT at work? Is it a user working on a shared family device where there's about 40 other people who also sign in on that device? Is the device on the most recent operating, service or system? And then when we're talking about network questions, it's really important to find out if the Internet connection the parent's using is on a Wi Fi in their office or if it's a public location. I always recommend for people to switch over into their cellular data because that is the simplest method for testing network functionality. If you can switch into cellular data and test and it operates differently, that means that something in the network could potentially be impacting you. We do also have in our KB about network functionality. We have a network test that you can provide folks where they can see if they're actually blocking any of our URLs, preventing them from signing in as well. We also have as a part of network connectivity, you may also need to ask if other devices in the home are working as designed or if they are also having issues because that would also indicate a potential environment impact. We talk about browser and cache a lot. I'm sure you guys hate to hear us say, have they tried clearing their cache and cookies? But the reason we're asking that is that the tiny micro bits of information that is stored in that cache can impede somebody's ability to sign in. So always have them test in an incognito or private browsing window. Try entirely different browsers if they're available or entirely different devices that they've never used to sign in before just to make sure that there's no other environmental factors. Once you get past those environmental factors, your next step is probably gonna be to take a look at your system. Checking in core using all the steps that Jesse and I have already referred to in this presentation, checking to make sure that everybody's information is, available and accurate according to the education management system. Something to really make sure to to know is that if parents are using one email for communication and one email for their BBID, that they are using their BBID email to try to sign in to the school. That is a very common problem we run into all the time. I would also recommend that you remove the school part from the issue, which I know sounds counterintuitive. But if a parent has no issue signing in on app.Blackbaud.com, that indicates that they're not having an issue with the account, but maybe there's something in core that's preventing them from signing in. The final step is always going to be testing. A part of that testing process should always be, asking every question you can think of. No question is a bad question or a dumb question. I say this as the person who gets the phone call from my parents to fix their printer. I am 2,600 miles away. I am still asked to do that. I ask questions including, is the printer plugged in? Is your Internet router actually plugged in? Do you have Internet access? Is that why you're running into issues? It could potentially be a cause and something to worth asking. Something that we also ask for you to do is always get the exact steps as they are happening. You can check with them, like, cross site sorry. Ma'am, you're yeah. You're good. You can you can be on this one. I was about to get to, what they see after. Yeah. You're totally good. You, so they also should be, you should be confident in putting the parent and user information in the school sign in as you saw, in our demo. And it's very important to get those screenshots and screen recordings from the parents. Most devices have that standard built in. But I would always make sure that you ask questions about what they typed into the box, whether if they've forgotten their password, if they've tried the process of resetting it, and checking for anything else. And you can move into the next slide, Jesse. So for our email password and MFA problems, I do want to say real quick, parents who are solely parents and nothing else are not enforced to use MFA. They are not required to use MFA. If they are choosing to use MFA, their best option for enrolling in MFA is going to be a mobile application that will allow them to additionally enroll in the self recovery system where they can reset MFA on their own. If you ever have a device that or a user who's reporting that the remember me function functionality isn't working, more than likely, it's because they are on a brand new device or they are on a brand new network that we don't recognize. So please make sure to remind people that the remember me option for sign in, which allows them to skip over their MFA process, requires them to be on the same IP address and the same device. In the instance of folks not receiving their code, they may need to enable their notifications on their device, and they may also need to check to make sure that they didn't block our system from sending them text messages to tell them that they're ready. We do highly recommend for everybody to have SSO for their faculty and staff. Let the parents use email password and keep that separated. And, Jesse, go ahead and move to the next one. I wanna do a quick reminder that sign in with Google is a social networking system. Google originally had a system called Google Plus. They also still have YouTube, which allows for people to create Google accounts with non Google emails. And as a reminder, you may also see folks say, I didn't mean to click on sign in with Google, but it just signed me in like that, and I'm stuck. That more than likely is can be caused by the fact that they're signed in to the Google Chrome browser with a Google account. So it has actually taken up the Google sign in process because they're signed in to that environment already. So keep in mind that all of the Google password reset process is going to be entirely done by Google and the Google support, side of things. If you do have any questions about signing with Google, please make sure you put them in the chat because I know that we're running short on time. Jesse, go ahead and move in to sign in with Apple. As we mentioned, last year at the 2024, we did introduce a blocker preventing hidden emails. So you'll no longer see people with private relay accounts populate. We no longer allow that to happen. We also have given folks the ability to delete their accounts. So if you have anybody who's stuck in a loop with sign with Apple, an option for them is to delete their account so that we can move forward and allow them to start fresh. The final two things here, this is about fast laning yourself through support. I know everybody loves the fast lane, so go ahead and move to the next slide. Make sure that you've tested by using incognito window. Make sure that you've gathered information about their network locations and devices, and please make sure that you've also tested their login attempts at app.blackbaud.com. And then, Jesse, go to the very last slide. The final thing that we have here is what is provide what is to provide support in your support cases. Please, please, please always include the impacted user's email address. I know that seems silly to have to provide that, but it is really helpful for us to know exactly what email the parent is using. We would also benefit from knowing the user type, what troubleshooting steps you've already taken so that we don't make you repeat additional steps, and tell us what the user status is. Can they sign in at all or are they completely blocked? If it's something that you need them to do an MFA reset or a deletion request, please put that in your notes when you send, in your support cases. I think I did everything, Jesse. I think I covered it all. I think you did. So here are our email addresses if you do have a follow-up question. I'll warn you though if you email us director directly, it may be a while before we are able to get to those questions, but we are available for you to contact. I am going to stay for a few extra minutes. Natasha, are you able to stay for a few extra minutes for some q and a live? Okay. Awesome. Stay if you would like to. Feel free if you need to hop. It doesn't hurt my feelings. We have one who asks, for users who are already signed in to Google and who are being authentic automatically, can the workflow still display the Google account selection screen? So once they've signed in, are they they should see if they're signed in to multiple accounts at once. It should give them a picker before they select which account, but it does depend on how they're currently signing in. So that one might need a support case to know. And yep. And that's another good one where if you if they're signed in and they're like, I have the wrong account, they can go to app.blackby. Or just blackby.com. Click sign in or not already signed in. Go to their profile. They can see what's actually being used and then sign out and sign in again or use a different window. But, yeah, that one may need some follow-up from support. You might consider reaching out there. I've I'm seeing a request to have a support line staffed for parents to contact because today, parents have to go through the school for support rather than being able to contact Blackbaud directly. I hear you. For the delete BV ID request, Natasha, can you talk to us a little bit more about that? Does the user need to contact Blackbaud support, or does the school admin contact Blackbaud support, or how does that delete user work? Sure. So we actually would prefer for the school to contact us to let us know that the parent needs their account deleted. The reason for that is so that you as the school can make sure that all of the back end system settings, whether if that is education, whether if that's tuition management, financial aid management, all of those things are lined up appropriately. Do have an article specifically for school admins, that tells you kind of what to do to prepare for somebody to have their account deleted. And I'll make sure that that goes in the chat so that you guys have that. Thank you, ma'am. Mhmm. Let's see. We have a request to articulate the account reset process, especially if they're using, like, signing with Google. Oh, somebody asked for us to repeat the app.blackbaud.com suggestion. So whenever somebody is logged in and they're like, wait. Why can't I get into my solution? I'm I'm sure that I I entered the right email address. They may have. And then in the redirect to Blackbaud ID and back into education, if they're already signed in with Google, it might pick up like, oh, we recognize you. We see you signed in with Google, and then they dump them back in as the wrong person. So if they go if they you can leave education management open, open a new browser tab, and go to app.blackbaud.com. And what that what that does is you can open the profile and see which email was actually picked up in the browser as being authenticated, and you can see who we think you are because that's who your browser told us you are. So going to app.Blackbaud.com to view the profile whenever somebody is logged in is always a helpful tool to make sure that they are actually logged in as who they think they are. Because that can be confusing, especially when you have a shared device. Let's see. Just as a reminder, an hour after the session, this will be sent to you as a recording. So you will have a copy of this as well as don't forget to go to the docs page, which is in between chat and q and a, and download the slides so that you have them for reference. A lot of the really, really informative slides at the beginning that Jesse went through, I know she went through as quickly as she could, but, they have a lot of info on there and, can answer some of the questions we're also seeing here as well. Yep. For users, that you've re enabled after they've been inactivated, somebody asked how long until they are inactivated again. If you reconnect them, that's gonna reset their inactivity timer. If they sign in to the system, that will re reset their inactivity timer. If you disable them and re enable them, that'll reset the timer. If you disconnect them and connect them or just reconnect them from the awaiting response tab. Any of those actions will reset that inactivity timer. The inactivity period is three hundred ninety five days, and then someone will be inactivated. Three hundred and ninety five days is approximately thirteen months. So that goes to say, like, with with a little bit of wiggle room, somebody hasn't logged in to sign their enrollment contract, within the last year ish. Three hundred ninety five days. And I'm so sorry, team. I said earlier, that it would be an hour for the recording to be made available. It's actually next day. So apologies. The recording is being made available to you next day. There is a a system time that we have to allow for it to to clean everything up for audio and quality. So apologies. Hi, Pat. Okay. Cool. Oh, this is a good question. Somebody said if both parents have the same email, is that that okay? Once you have connected them to Blackbaud ID and they have a Blackbaud ID username, their Blackbaud ID username has to be unique between the two like, each person has to have their own Blackbaud ID username. We won't allow you to have multiple users with the same Blackbaud ID. Once they're connected, you can make their email address whatever you want. So if they have, like, a shared family email and you want them to receive, like, push page emails or notifications or whatever at the at the same email, that's fine. It's just that they can't share the Blackbaud ID username. So at the point when you are connecting them to BBID, that email is gonna have to be unique. But after that, we don't check it unless you're trying to reconnect them. Two of my, friends in Hawaii are reaching out, and I'm gonna follow-up with both of you. Uh-oh. The links in the docs are to the same URL. Let me see. Hoping selfishly, it's to the one I want you to have. Oh, it is not. Okay. Let me see. Okay. So let's go back. The doc that I want you to see or the link that I want you to have is the one in the community. This is the link that I would like for you to have to look at the, Blackbaud ID blog post that we put out in education that talks about all the things we've heard related to account inactivations and redactions and the things that we are doing in response to make that easier to manage. Thank you to the person who pointed that out. Okay. Hop back in q and a. Pick one more. Maybe I'll pick two r. If our SSO is Google, should we remove the SSO for login? You can. You don't have to regardless of which authentication button they push. Somebody who's on SSO is gonna go through SSO to log in because we are gonna recognize that that email domain once they try to continue. Yeah. Ultimately, it's up to you. It depends on what value you see for each of those buttons and the order that you place them on. Good point. Having the same email address will break your ability to bulk connect BBID for those shared people. So proceed with caution if you're gonna share email addresses among multiple records because you won't be able to to connect easily without touching both records in the future. The recording is emailed to each person who signed up, so you will receive that within a day. And just a note on parent accounts as well. If you have parents who are wanting to use their work emails or their work business emails, whatever it could be, just take into consideration that, Blackbaud is a global company. We have many products and many solutions. It is also possible for their work email to be a Blackbaud customer, in which they could have SSO configured for their organization using Blackbaud products, and that also adds to that. So where you can, please make sure to stress to parents that they're using a personal email address that they have access to, and that they'll maintain access to if they leave that organization or business just makes things a little bit easier for them. K. Last one we'll answer today. Natasha, somebody asked if there are any known issues with mobile apps for authentication. One thing I remember is if your phone goes swimming in the ocean and you don't have your 24 digit recovery key, you are out of luck and it's nearly impossible to recover that account. Correct. So if you do not have your 24 digit recovery key and you have not configured a recovery phone number for your mobile app, which you can configure a recovery phone number directly from your profile, Those users, we can do an MFA reset for them, and they will be able to reenroll in MFA, but they will need a device to reenroll with. So if your phone took a swim in the river or in the ocean and you don't have a replacement device yet to receive the new either text message or MFA app code, you're going to have a much harder time to to get reenrolled. I would highly recommend, the biggest thing I see with the apps is, the method to which they name the application in Google auth is different than how it's mentioned in the Microsoft auth. So you'll actually see in each of those applications, it might say Blackbaud plus MFA as the name of the code, and that's just that's how they decide to display that. So that happens quite often. But, definitely, those applications also sometimes have local backups or backups that they do separately. So if you do ever replace the device, lose the device, sometimes when you restore from a backup, it will bring that information back forward. But there's no guarantee, unfortunately, because each of those works work differently and Blackbaud doesn't have much control over how Microsoft Authenticator app or how the Google Authenticator app work. Cool. Thank you again everyone for joining us today. As a reminder, this is the community, link that I wanted you to have. The other, the last two links that are shown under the docs are going to the same place, which is our help docs. And then today's slides were included as part of this. You will receive a recording for this webinar in your email within the next twenty four hours ish. It's usually pretty quick. But, by the next day, you'll receive that. And if you have any questions, you can contact support. My email address is in there at the bottom, but I am perhaps the slowest way for you to get information. But feel free to contact me if you would like. Alright. Thank you, everyone. Hope you have a great day, and we'll see you at the next one.