Name: Mastering Programs: Best Practices for Applicant and Grantee Success
Uploaded: 2025-02-15T19:12:09.819Z
Duration: 56 min 4 s
Description: Mastering Programs: Best Practices for Applicant and Grantee Success

Transcript for "Mastering Programs: Best Practices for Applicant and Grantee Success": Good more well, good morning, good afternoon, good evening, wherever you're joining us from. Thanks for joining us. We're gonna take a few minutes here right at the top. Let some of, these numbers climb up and then level off, and then we'll go ahead and get started. Hope everybody's doing well out there tonight or, again, tomorrow morning from my time. Alright. Numbers seem like they might be stabilizing a bit there, so I think we can go ahead and get started. I don't know if anybody else is seeing this. It's looking like our images are waffling about a little bit on the left hand side. We'll ignore that for right now as we go ahead and get started. Welcome to the second iteration of our first in a series of monthly office hours concerning the new applicant and grantee, portal. You guys spoke. We heard you loud and clear that you need, needed some more enablement, needed some more resources to help with the transition. To lay a little groundwork in case you're unaware, everyone who uses BBGM should have access to our new applicant portal. If you're not sure if you have it or not or who was enabled at your organization, you can always reach out to support, and they can tell you who we enabled at your at your organization, and that person can, provide access to any other users that need it across the board. The legacy portal, what you may know as iGAM, is up and available until the August 2025. At that time, everyone will need to be operating, under the new applicant and grantee portal, and we know change is, never easy. There's always challenges with it, but we think the payout of of what the new portal brings is gonna be so beneficial, and it's gonna allow us to iterate, at a faster pace going forward and keeping it keep it growing and keep making it better. So we think the juice is well worth the squeeze. And joining me today to help present, I should introduce myself. I'm Ryan Turner. I'm a customer success manager here at Blackbaud. I will be helping host this session and doing some q and a. Is this session being recorded? I saw that pop up right there. It will be recorded as was the one we put on yesterday. We would ask a few, things, and then I'll get back to the intros. We'd ask a few things, just some housekeeping. Please, if you've got questions, make sure you're putting those into the q and a section. It's the way we track them most easily and readily and make sure we're getting responses out to people. Second, when you throw in a question, try to put in a little context that really helps us out because it lets us know what you're referencing. If you just say, like, hey. Can I see that thing again? We're not sure what you're referring to. So if you, specify it a little bit, that will help us out. Like I said, these are recorded. If you were unable to make it, you will receive the recording via email. Generally takes less than a day, to do those. But back to introductions, I introduced myself, but I'd also like to introduce Penny. Penny, if you wanna jump off mute and say hello. Hello, everyone. My name is Penny. I'm a customer success manager at Blackboard Pacific. So for all our, Asia Pacific customers, hello. I hope some of you guys are joining us this morning. I will be popping on a couple of these sessions moving forward. So I hope you guys get a lot out of today's session. And of course, if you have any questions, feel free to email me. I will put my email in the chat at some point during today's session. But, yeah. Hello, everyone. I hope you enjoy. Very brave of you, Penny. Thank you. And then and then I'd like to introduce the person who's going to be delivering the bulk of the technical, review today. That's Nick Mills, a fantastic representative from our professional services group here at Blackbaud, US based. Nick? Thanks, Ryan. See here. Yeah. So I'll just introduce myself. I'm a senior principal business consultant within our professional services department. I focus exclusively on grant making, a lot of implementation. So So I've been working with, a lot of clients very closely on sort of migrating to this new portal and getting everything set up. I am located in Minneapolis. And for anyone who doesn't know where that is, that's kind of right in the middle of The United States bordering Canada. I I believe it's summertime in the Pacific Region, and, I think it'd be fun to tell you that it is currently negative 24 degrees outside, in Celsius. It's negative 11 Fahrenheit, so it's it's a little chilly here. So I hope everyone is enjoying their warm weather wherever you are. So we can go ahead and get started. So we're just focusing if I could, Nick, real quick. I wanna, thank you for that, and unbelievable that it's that cold. And I always thought of Minnesota as the chef's hat in the map of The United States that's bordered by the Mississippi River. Anyways, the only other thing that I wanted to add about the q and a, Note that we're talking today about programs. This is a series of four, so we're gonna have another one in January that talks to, setting up new forms from existing forms. We'll have another one on the dynamic form builder in February. March, we'll have a tips and tricks. So one of the things we request is, to try to keep your questions sort of on the topic we're presenting, as we as we go through this. So I just wanted to throw that out there, Nick, but I'm gonna toss it right back to you to go ahead and get started with the bulk. Great. Thanks. So like I should have said before, this is specifically mastering programs. We're gonna be talking about the setup of programs, all the different options, and how that's configured, and some best practices, that will, you know, help with applicant and grantee success. So let me jump ahead a little bit here. What is a program? Programs are a group of applicant slash grantee forms that work together to create a specific funding process, and the settings inside that program relate to how the, the funding process will be managed at that applicant or grantee level. So what exactly does that mean, and how does that relate to what you're used to? It's often, a good idea to consider a program to be very similar to a request type. When you're in your classification table, you set up the giving program type status list. That is where you define the different request types that your various grant programs may have. In general, we would suggest that there's a a parallel between each request type and the program. That is not always the case. It's not a % the case that your program will match, the request type. But in in general, that's kind of how we think of that. So you'd think that your request type, you have a very specific workflow that that goes through. You get your application. You may have a second stage application. You may have requirements that are due. So you think about that entire process from intake until you're making funding decisions and some of the reporting that may come after that. That is all kind of combined and consolidated into a single program. So that program is really, a a grouping of forms that helps move the applicant through that workflow. So in general, like I said, we recommend sort of a one to one relationship between your program and your request type. That is not necessarily going to be applicable to every single program, but that's a good way to think about it that, you know, your your program is essentially your request type and the the the forms and the stages that that goes through from start to finish. There are six main components of a program. So when you're in, the program setup, you're gonna have six categories of options. And so we're gonna walk through all of these in a little bit of detail, but we've got some specific details, some settings, cycles that determine when an application can be submitted, the specific forms that are available, where in your workflow those come in, and then specific communications as well. So the first part is setting up the details, and this is really, sort of my colleague Jason called this the welcome mat yesterday where you're sort of you're greeting your applicants. This is the first thing they're going to see when they get the link to access the program, and all of this information is visible to your applicants. So you've got things like your program name, the time zone of that specific program. There are details about when the program may be open and accepting applications. There's an opportunity to describe the program and also add in some guidelines, And then you can also add in a specific program logo or program background to help kind of brand, the program to your specific needs. So this is what you see with that very first, you know, I've clicked on the link to access the program. Here's the very first thing I see after I've logged in. So you can see we've got things like mastering programs as the title of the program. If you click on that view guidelines link, that will open up a separate sort of pop up window where you can list out all the different guidelines for that program. We are accepting applications until 03/12/2025 at 11:59PM, and then we have a nice description of that program. Now some of these can be turned off. You don't have to have all of this, but there are a lot of different options. You can also see the Blackbaud logo and the Blackbaud background, just to kind of help brand and and make this a little bit more of a welcoming, welcome mat. When we move into the settings, this is where we really get into some of the the meat and potatoes of how everything works. So we'll talk about some of the recipients and who the audience for the program is, some organization options, eligibility for recurring applications and being able to apply more than once, the ability to add collaboration and collaborators, copying applications from previous submissions, and then program emails and reminders. So first up in the settings is for the recipient. Now there are two options. You can either set up the program to be, specific to funding an organization or an individual. I would say the vast majority of grant making organizations that, use grant making, strictly grant to nonprofits, five zero one c threes or other nonprofit entities where they're granting to the organization, not to a specific individual. That being said, there are some that do grant directly to individuals, perhaps as a scholarship. And so there are some different options in terms of who the intended recipient of those funding dollars are. When you select an individual applicant, that requires an an additional individual applicant field and potentially some configuration. So if that has not been something you've used before but you are interested in using it, that is certainly available to you, but there may be some additional configuration that's needed, when you're setting up a form for an individual applicant. When you're selecting an organization, there are gonna be some more options that display that we'll talk about here in just a moment. So those settings for organizations options. So moving forward, I'm gonna talk most about, those who are accepting applications on behalf of organizations. So the very first thing is, when you launch the program and you start a new application is you are asked to select, an organization. And this organization search consists of a number of different databases that are all sort of, consolidated into what we call NPO Connect. And that NPO Connect database is not specific, to your grant making database. So when you're searching organizations, you're searching for that nonprofit, that five zero one c three, That is a a a large database that consists of a number of different databases like the IRS Business Master File and and a number of other international databases that, are sort of pre vetted organizations. These have gone through a vetting process, in addition to some that have not. But it's, the very first thing is you have to choose an organization. Now what happens if your organization that, you're applying on behalf of is not in that database? This very first option allows applicants to add organizations to that NPO Connect database. So if I'm searching for something and I do not find the one that I'm looking for, I have the opportunity to add that information into the system, which will then come through into grant making. Now, again, I just wanna reiterate that that database of adding database or adding organizations is not your grant making database. You still have complete control when you're considering those applications as to what organization record you use, what contacts you use, or if you create new ones or not. This is purely looking at that NPO Connect database to see if that organization already exists. If it does, fantastic. If not, checking this first box gives the applicant the option to add information into that database. There is also an address restriction. So based on location, and, again, this is in the NPL Connect database. So if that organization record exists, you search for it. You want to limit your specific applicants to the, organizations that they can apply on behalf of. You can choose your country and then, a state, province, territory, something depending on the country. It doesn't get any more granular than that. So in The United States, for example, you can choose The United States and a specific state. In the screenshot that I have here, United States, New Jersey is selected. That means that the address on file in the NPO Connect database has to be in New Jersey or it will not find it when you're searching. So you can specifically limit the, the location of the organization that is applying. So if you have a very small region or a small smaller area that you, tend to focus on, you could potentially add in some restrictions, based on address. And, again, that's based on the data that's already in that NPO connected database. So if it happens to be something, where you grant nationally and you have some restrictions on there that could pose problems, so you wanna be careful with how you're using that. Next, eligibility of recurring applications. There are currently four options that are displayed on the screen. Only three of those currently work. That last one, limit one application to the current cycle. If there was an approved and awarded application, that is not currently supported, so we just say kinda don't use that one. The other three, determine how often somebody could apply on behalf of an organization. If you're set to allow multiple applications, then there's no restriction. I could apply today. I could apply again tomorrow, again the next day. If I limit it to one application per program, that is one application for that organization in that entire program regardless of how long that program is open. So if I only want one organization to be able to apply one time the entire time that that program is open, that is, what you would choose. You can also limit to one application per cycle. So a cycle is sort of, it's not just a wide open time well, it can be wide open, but if you want to dictate specific times during the year where you're accepting applications, you can set that up so that, you can only apply once per cycle. Let's say in a given year, you have three different grant cycles, perhaps two or three months at a time, then you take a break and add, then have another cycle that comes up. Limiting to one application per cycle allows just that organization to apply during that cycle one time. And remember that this restriction is based on the organization that's selected in that NPO Connect search when you're starting to fill out that application. It is not based on the individual person who is logged in. So one application per program is one application for that organization. One application per cycle is one application in the cycle for that organization. There is the opportunity to add collaborators to your applications. So when you first start an application or after it's been submitted, you can add additional people to help manage those applicants. In the screenshot here, Jason is the applicant, and he added me. When you're adding additional people, you can choose whether or not they can manage additional applicants, and you also have the opportunity to determine whether or not, they are able or they will get any of the email notifications that are automatic within the system. So if you, have multiple people that are going to collaborate on an application to fill it out and submit, You can add them all. They can all see the application, and you can kind of collaboratively work on that. There's also the ability to, copy from previous submissions. So this is within a specific program. If I have submitted an application in that program and I come back and do another application, I'm going to get a pop up here that says, hey. You've previously submitted some applications. Do you wanna use these as the basis for your new application? If you click copy, it's going to take your, the answers and responses from the previous application and populate those in the new to help facilitate, filling out that secondary application. Program emails and reminders. There are, a number of different emails that are in the system. And if you have multiple programs, perhaps you have different logos, different, entities that you are working with. You can choose to use different logos for each of those different programs. You can determine here what that sender display name will be. So if you want it to look like it's coming from somebody other than, you know, your organization name, you can do that. And you can also set up a draft application reminder. So, for example, anybody who started an application but has not submitted it yet, in this case, seven days before that cycle ends, they will get an email that says, hey. Just so you know, this cycle is closing. Go ahead and fill out and submit your your application. Now there's only one form due by email in the communications. So you can use the document template manager or communications emails. There are a couple emails where it's a little bit duplicative, where organizations in the past have documents and email templates set up within grant making. So there's there's a little bit of overlap. Some emails, are automatic in this new system, but they can be turned off if you prefer to, use the document template manager emails as you have in the past. So within settings, there are also, a handful of options that are not currently live. The invitation functionality, displaying payment status, team deadlines, grant manager reminders. And if you have the program set for individual applicants as opposed to organizations, there's a mask applicant information option. None of those are currently live. They're not functioning. They're sort of placeholders for potential future implementation, but they do not work currently. So we would just say ignore these for right now. Next on the groups of settings are these cycles, and this is when an applicant can enter the workflow. So you really have two options. You can mark your cycle as being perpetually open so that, you know, if you never close down your cycle, you accept applications year round, and you never don't want to accept applications, you can leave that open all the time. You can also have set periods of time. So if you have those two or three grant cycles a year where you want to accept applications during a specific time period but then restrict anyone from being able to submit applications, between those periods, you can set those individual periods. Now cycles are when an application can be submitted. So it's that initial application when it starts. You start entering that workflow. You begin with the, application, and it needs to be submitted within that period. That does not apply to requirements or other forms that may be published out after the fact. That's just that initial submission of that application. Looking at adding a new cycle, you can give different cycles a different name, and this is really just an internal name. No applicant will ever see this. That's just what you can call it so that you can help manage the different cycles you have. There will be a checkbox if you wanna leave it open all the time. You have to have at least one cycle for your program. But if you're going to leave it open all the time, you simply just check the box that says it's always open, and that's all you have to do. If you do have specific dates, you can enter the dates in here as to when you will start accepting and when you will, no longer accept applications. And the time zones for these times are based on the time zones that you choose in the settings in that very first screen when setting up the program. For budgets and processing, this is a placeholder. There's no current functionality with budgets. So it it's not tied to the budget module. It's not tied to any sort of drawdown. It's just a placeholder for right now, but you do have to choose a budget. What's nice is that when you click that select cycle budgets button, there's just one option. We just give everybody a billion dollars, and you choose that, and you save it. You have to have a budget, so you have to add that in. You have to add that billion dollars, but there's absolutely no functionality currently. There may be in the future, but for right now, it's just choose that billion dollars and move on. A few notes with cycles. Dates cannot overlap. So you cannot say, you know, I'm gonna go until January 30, and then it's going to stop or that my next cycle is gonna start January 29. They can't overlap, so they have to be concrete, start finish, start finish, start finish. Reminder that this only impacts the ability to enter a workflow with the default form. So when you're setting up, your forms, which we'll talk about in just a moment, that is sort of where the application process starts. So you start that. It it impacts the ability to start that workflow, and then you must submit within that as well. Again, that does not apply to requirements or other forms that may come after an application has been submitted. And then just a reminder, you have to choose that default cycle budget. You can't create new budgets. You just have to use the $11,000,000,000 budget that's provided. Forms. This is how the applicant starts their their, application journey. So you have, an optional eligibility form. In the legacy grantee portal, every single application, you could enable an eligibility form where you would say, you know, here are your questions that determine whether or not somebody is eligible for your program. And then based on whether they answered correctly or not, they were either allowed through to the application or they were not. In the new applicant and grantee portal, eligibility forms are a separate form altogether. So if you you know, I've I've worked with organizations in the past that have had maybe 25 different applications, but they all use the same questions on their eligibility form. So instead of having 25 different eligibility quizzes to maintain, you just have one eligibility form. You can certainly have multiple eligibility forms, but if you have just one that you wanna use and apply to every application, you can certainly do that. When you're setting up that initial program, you can choose your eligibility form, and that's also where you dictate that this is the correct answer, this is the incorrect answer. After that, it moves on to the default form, which is a request form. So that typically that's stage one application. There are a number of different form types. We're not gonna dig in too much to those right now, but there is an LOI form type. Just note that you cannot set that as the default form. So you typically would want, a request form, sort of that default form to be that initial stage one application. You can certainly utilize that LOI stage or that LOI form for later stages, but not for that default form stage. And in the general workflow, you're gonna hear a lot about workflows in relation to this new applicant portal and programs. This is where you determine all of the forms that might be part of that applicant journey. So looking at this little graphic, you've got the request. You might have an other applicant form. There might be some additional information you wanna collect, but that would also be a request. So that could be a stage two. Then you've got your grant agreements, additional documentation, some progress reports, maybe a final report later on. All of the forms that are potentially going to be available and used for that program need to be added into the workflow. So if you have an eligibility quiz, that's gonna come first. That's the first thing the applicant sees when they select their organization and they move on to the application. Then you're going to have your actual application. After that, you could have 50 different requirements available. One thing that we've heard, in the past is that when you went to publish out a requirement, there was, you know, essentially a list of all of your active requirements that were available. Now within a specific program, you can decide only these five requirements apply to this program. So when somebody fills out that initial request, that initial application that's turned into a request, when you go to publish out those requirements, you just get a drop down of only the ones that are applicable to that program. One other note, there's a nomination type form, and those are not part of the workflow setup. That's one of the the form types that currently is not working, similar to the invitation functionality that's not currently functional. So workflow and determining when forms need to be completed. There are some options for adding some due dates within the workflow. So when you go to add a new form to your workflow, you can set some particular due dates. The three options are no due date, relative due date, and custom due date. The no due date is just going to use the standard Blackbaud grant making requirement record due dates. There's not any particular date that that specific form is due. So for grant agreements, progress reports, additional documentation, if you have final reports, financial report requirements, things like that that you're collecting after the fact, you can just use the standard due date on that requirement record. A relative due date is great for additional request forms and other applicant forms. So you you add the form in and you say, this is going to be due thirty days after the application is submitted, or this is due three months after the application is submitted. That's all gonna be based on that that original submission. And then you can also have a custom due date where you set a specific date. So if you have additional request forms, other applicant forms in that workflow where you're collecting additional information, you can say all of this has to be submitted by December 30 regardless of when that original application was submitted. Then there are communications and that's really, the automatic emails that are sent out through the system whenever there are particular actions. So for example, there is an email that goes out confirming that a submission was made, Very similar to the submission confirmation message that is sent out in the legacy grantee portal. Same kind of thing. There are emails that can be modified, and and applied to different programs. So there are default emails that are available. If you want to create a program specific version, you can make a copy of that and then modify them. And there are also a handful of emails that you can deactivate. So if there are things, there's, an additional form has been added email, for example. That is sent out by default when you publish a requirement out to someone. If you prefer to use the emails within the document template manager, so you you've received your application, you've created your request, you've added a requirement record, and you've published it out, but you don't want an automatic notification as soon as that is published, you can deactivate that email and use the the emails in grant making that you're used to using. So there are there's a little bit of an overlap with a couple of those emails, but you can deactivate a number of those emails if you prefer to use the ones that you've used historically in grant making. So like I said, this, there's a little bit of an overlap in that the communications, the emails out of this new applicant in grantee portal do not replace the document template manager. The application form added and due form due emails can be deactivated if you prefer that those do not automatically go out and you'd rather, push out those emails when you're ready for them. You can also add a cc and bcc option to all of the emails or too many of the emails, not not every single one. But for application form submitted, for example, there are a number of organizations who aren't looking at grant making on a daily basis. They may have a lower volume or they may have specific periods of time during the year where they are anticipating an application coming in. This way, you add a BCC, you add your email address, you're going to get an instant notification as soon as somebody submits that application. You do need to make a copy of that in order to utilize, those that BCC option. So there are a lot of just sort of standardized regular emails that are part of the system. In order to make changes to those, you need to make a copy and then apply that to the program. But there are, a number of different options for those communications. And it's our general recommendation that you really should test the full process from creating an account to filling out an application, to publishing requirements, to pushing out a request for revision, publishing out a second stage application, publishing out multiple requirements. Go through that entire process, testing everything that an applicant might do, and then you'll see what emails come through and how you may want to modify them, in order to really conform to your program. And that is the end of our slides. I can hop over to the actual database, and we can take a look at some of these options. Nick, can you go ahead and hear me? Yes. Outstanding. I love that delivery. I would know one of the questions I think I've seen a couple of times, and we're answering these as we go through, asking, can we get help with, doing this? So I've offered you up, Nick, and the services team in general. If you're watching this and you're like, alright. This, you know, seems like maybe more than I wanna take on right now. Our services team is here to help. You can always reach out to your customer success manager, be that me or someone else, and and let us know that you're looking for that assistance, and we can work to create a project, a paid engagement, to be very clear, that would help, you do whatever you want, either recreate a couple of forms and set up your programs in the new system or taking advantage of some of the new functionality within the tool, to do so. And there will get some other q and a live, but, Nick, I want to pass it back to you and give you a chance to break from talking for just a minute, and and feel free to take it back over. Yeah. Yeah. So, like Ryan said, we're we're more than happy to help if there is sort of that hands on assistance needed. There have been a lot of resources posted in the chat, and I'm sure there will be, you know, elsewhere to to find those resources. But, at a high level, you want to get your portal set up, and we haven't really talked about that. But that's another option. That's some of the the starting point. And then you wanna set up your forms. The program is really the last piece that you're gonna configure because you have to kind of define that that initial application form. So the program is really the last thing that you should set up. You can go through, get all of your applications and everything else set up before that program is created. But it's that program that is the the link to access this application as opposed to individual applications having their own specific link like in the legacy portal. So right now, we're giving program links, and that's a collection of forms, applications, eligibility, requirements, all of those in a neat little package called a program. Is there anything that anyone would like to see in more detail? I can go through some of these steps a little bit, in more detail, but we have the mastering programs here. I'll make this a little bit larger. So these are all the different areas that we just went through. So the details, you can decide how things are going to look, program guidelines, your logos. Within the settings, this is where you choose individual applicants or organizations, whether or not you can add an organization. And this this is something that I definitely think you might wanna consider enabling, especially if you are potentially going to be granting to organizations who may not be in that NPO Connect database. So just adding this option gives them, the applicant, the opportunity to add an additional organization, should they not be able to find that in the search. Organization locations where you can define the geographic area of those organizations that are allowed to apply. The recurring applications, remember we have multiple applications, one per program, one per cycle, and that this last option is not functional. Collaboration, the ability to add, or to copy from a previous submission, And then a lot of these, further options are not currently available, like the payment status, invitations, program emails. There are form due reminders. So when you set up those specific due dates that we talked about when you are adding additional forms into your workflow. You can send those reminder emails, you know, five days before it's due, five days after the form was due so that you have a little bit of a reminder that, oops, you maybe missed the deadline. You're not gonna submit this. When we move into cycles, you can set up all sorts of different cycles. When we're in the cycles, we've got that always open box that will just perpetually allow applicants to, submit their applications. Forms. So this is where you would set up your eligibility quiz. Once you have that eligibility form created, you select that form, and then that's going to display all the questions that are on your form. And you say, this is the correct answer for this question. This is the correct answer for this question. One thing I do wanna mention about eligibility forms, in the legacy grantee portal, you could have multiple correct answers. So if you had a question that maybe had five answers and three of them allowed you onto the application and two did not, that was something you could do in the legacy portal. In this new portal with the eligibility form, you can only have one correct answer per question. So as you're thinking about migrating your forms over and starting to put these things together, you may need to consider rewording some of your eligibility questions just because we can only have one correct answer per question. The default form, that's that initial application form, so the first stage application, that request application, that has to be defined when you create the program. This can be changed up until you have accepted an application. So once there is an application that's been submitted, that is no longer modifiable. So you really wanna make sure you have that correct when you're setting up the program, and that's why we also suggest setting up the program as sort of that last step before you you publish things out. Nick, we did have one question I thought I might bring to you and some additional information I wanna put out there. If you look in the chat, I've been dropping in, some links there. A lot of you were, like, sort of, but how do I get started, really? There's a couple of things that I would suggest. The first is to go to our customer success enablement page, which I have listed there, in the chat. I can redrop that if, that would be helpful. I've also linked to a couple Blackboard University courses that are to let you know they're free in front of the learn more firewall through the August, of next year. So you can have that. We will be introducing instructor led training, sometime early in the new year is is my current understanding of timing for that. So there are resources there, and I would always point you to the customer success enablement page, to see a lot of those that are available. But one of the questions I wanted to ask you, can you can we see how you would share out the program link to applicants? Absolutely. I just so happen to have my list of programs available here. So once you have programs, they need to be published. Publishing essentially makes it accessible outside of this window. So once that applicate or that program is published, you can click the three dots and copy the link, and that is the link that takes you to this page. So that's gonna take you to that landing page where you have the program description, the cycle dates, guidelines if you want it, and that's where you start that new application. So this is essentially the link that you would give to that program similar to how you used to publish out the links for individual applications in the legacy portal. I love it. Thank you so much. I do have, some other questions on here. People asking sort of, how do how do we test? I think you covered the talked to this a little bit, but sort of how do we test? Because we don't have sandbox environments. We don't have test environments, and looking to sort of understand how do you go through and do a test run on this to to vet that everything's functional and how you like it. Yeah. So this new applicant portal and the legacy grantee portal are completely independent. There is no overlap whatsoever. So you can continue to run your existing programs with the legacy portal as you're setting up the new portal. You can test the new portal, the new programs, the new applications. You could even use them both live concurrently if you wanted. The mechanism for importing those applications into grant making and turning them into requests and contacts, that's a little bit different. They're kind of in the same location now, but they're slightly different processes. So you can run those concurrently and independently. So while you're currently using the existing legacy portal, accepting applications, doing everything the way you've always done it Always done it. You can also, start testing, go through the test applications, submit everything. You can do all of that in the new portal without impacting anything with the legacy portal. And just if you choose to delete it, or just leave it there as byproduct, I'd probably delete it. I'm looking for some other questions. There's been a lot coming in, but I see our team's been, pretty outstanding in in nailing them. Here's one. Let me know if this makes sense to you, Nick. During testing, all the emails that are active for my program during testing, all the emails are active for my program, but the only email that gets automatically sent is the application submitted one. I'm curious why that is. Even if she approves the request and set up the payment, no other ones get sent automatically. That sounds like maybe that's on the legacy portal or maybe you're testing the new portal. It sounds like it's something new portal set. Yeah. It sounds like it might be the new portal. The there are a handful of emails that are applicable. There are also a whole host of emails that don't really apply to grant making. So there are some that mention, like, nominations or grant managers. Those don't apply to grant making, but the the standard ones like an additional application form has been added or the application form submitted, those will go out automatically. So as soon as you submit an application, that email will be automatically sent. If you publish out a requirement to that applicant, that email will be automatically sent unless you specifically deactivate them. Right. That's cool. And if if that's not the case, that's not what you're seeing, I would encourage you to add in a support case, and we'll have somebody take a look at that for you. And by the way, Colleen did jump on the the chat and said, yes. New portal. I I got another one here. Will our historical data in the legacy system need to be migrated to the new system? Will we need to do this ourselves? And, Michael, there's sort of two answers there, if you will. Your BBG this this doesn't impact your core blackboard grant making system. You will always retain the history from the legacy IGAM portal and the new portal altogether. It will all commingle beautifully in your system, so there's no issue there for you. Might take the opportunity to hear, here to note for your applicants, they will lose access to the history in the historical portal because we are literally shutting down at the August. Now most customers or most customers, excuse me, most applicants either already, like, download that data and store it locally or, they don't care about having it, but they can until that August 30, thirty first timeline, whatever the August is. They can until that day, go in and download their history. They can save their history from those legacy portals. If you're talking about need to be migrated to the new system. If you're talking about sort of bringing your existing forms into the new system, that is what we're all talking about here. You're gonna have to create and set up these programs and set up new forms as part of this effort to migrate over to the new portal. Unfortunately, there's no way to seamlessly push those over. If you go on the customer success enablement page, I will try to link that again here in the chat momentarily. You'll see we have a guideline that helps you do that. And also, the January, the January topic for this monthly series is exactly on that, generating new forms in the new portal from existing forms in the legacy portal. Yeah. The other thing I will add is that when you considered applications in the legacy portal, there's automatically an HTML copy of that application and exactly what was submitted that's attached to that request. So you have all of that data. You have those files that were originally submitted. So that's never gonna be lost. We're not touching organizations, requests, requirements, none of that. Everything, once it's in grant making, that will not be touched at all. It's just how we're getting that data into the system is changing. Another question here that might be relevant, Nick. If using both legacy and new portals, will requirements set in the legacy portal continue to be trackable after the full shift to the new portal happens? And I think I could answer this pretty well, but I would wouldn't mind giving you a better crack at it if you want to. Sure. So there that is something that we're working on right now. So if you have an application that was submitted in the legacy portal, you cannot currently push out a requirement in the new portal. So those requirements are sort of tied to that original application submission. There are some organizations, quite a few in The United States, that, they have have an application that's been submitted that's been turned into a request, and they might have two or three years worth of requirements that have already been published. We're working on a way to sort of migrate that or to enable the ability to push out requirements, in the new portal from legacy data. One of the big sort of sticking points is being able to do that in batch. And so that's what is really taking a little bit of time to to get right is being able to publish out all these new requirements and everything that you might need to push out, but doing it in in a batch manner so that you don't have to go individual form by individual form, which could take a very long time. So that is something that will be coming soon. Currently, there's no way to do that. The only way to publish out requirements in the new portal is to have accepted an application in the new portal, but we are working on a method to be able to do that so that kind of link two together. And we hope to have more information, on what that's gonna look like early in next year. Think think think q one of maybe late q one of next year. Have, that process constructed for you in the way that's easiest for you guys to operate, but couldn't answer to better myself. Omar asked, I don't see a way to delete a program. I've tested one by filling out an application, and now the default form is locked as you mentioned. What's recommended in this situation, or does that almost by default stay there? I have not seen an opportunity to delete. I I have seen the ability to archive, programs, and I think it really depends on if you have published applications, like that default form that you select. If that is still a published and active application, you may not be able to archive that program. Makes sense. You can always rename them, you know, put a z at the very front so that it goes to the bottom of the list. I I haven't seen a whole lot of, you know, archiving, deleting. Some of that is a little bit funky right now. Alright. I definitely get that. And maybe, I I would always I'm not sure how many people on here are familiar with our ideas portal on the community where, like, if that's something that, that you'd really like to see, submit that to the ideas portal. I strongly recommend it. A lot of people are like, oh, it goes nowhere. It really does go somewhere that's reviewed consistently by our product team to look for ideas impacting the any larger subset of our customers. Maybe time for one or two more, Nick, if you're if you're game. If I have one program but provide different types of grants, unrestricted, project, capital, and have different grant agreements for each type, will I have the option to choose which requirement to send out depending on what type of grant is approved? Maybe a unique situation there, but you run across a lot, so maybe you got it. Yep. So in that situation, you remember that a program is a collection of forms. So if your unrestricted grant, for example, had five potential requirement forms that you could publish out, you would wanna add all five of those to the program. Then only those five would be available to publish based on the original application. If you have unrestricted grants, project grants, capital grants, and they all have different requirement forms, I would suggest a different program for each one of those. Then you can define which particular requirement forms would be available for that application. It's it's, you know, very much like I mentioned earlier on, a program is generally applicable to a request type. That's not always the case. But if you have different sets of requirements based on the type of grant, you can you can use different programs to sort of dictate which requirements will be available to publish out. Good deal. I hope that answers, that question for you. Looking to see if there's any another good one here, that could be wide widely available. I do see a number of questions coming in about the NPO, connect, and we're gonna take we're we're taking a lot of these questions, to be able to answer them as thoroughly and concretely as possible. Getting a little echo there. So I guess what I'm saying is have a little patience. We will, be responding to those. I'm not seeing a ton of additional questions here. Anyone else? Penny, I know you're not on stage, but anything else you're catching, that's catching your eye that you'd like to have asked, you can jump on stage if you'd like. Or if not, Nick, anything else you would add with our remaining few minutes here? No. I would just suggest going to, a lot of the resources that have been posted, especially that customer success page, the customer enablement page that has a lot of different information on there. And I think reading through that, going to the the trainings that are available, that's really gonna give you a a good sort of overview and a better understanding of the entire process. Very good. Alright. With that, I think we're probably all set here. So I wanna thank everybody for, their time. Like I said, you will get a copy of this recording, generally within about a day that you can launch and rewatch whenever you'd like. We will take any unanswered questions back and identify answers for those. We'll use that for a couple of purposes. In fact, while I've while I'm thinking about it, let me share the FAQ document that we have in the knowledge base on the new grantee portal. This may answer some of your questions, and we keep adding to this knowledge base article. And the questions we're gathering from these sort of webinars will be used to continue to flash that out. So take a look at that as well. With that, I really appreciate everybody taking the time today to join. Nick, I wanna thank you for, presenting. Penny, thank you for joining us from Down Under. Everybody have a great rest of your day. Really appreciate it.