We have a real need for this. Larger orgs like universities sometimes have separate foundations administered by the same staff as the main org, with grants going to both.

I completely sympathize with this original comment - this is posing a challenge for us as well. We have an applicant from a nursing and rehab facility with multiple subsidiaries. Much like a hospital system, each facility has their own EIN number so we definitely want multiple organizations in the system. The “applicant” from every branch, however, is the Executive Director. He obviously has only one email address – so the system will not let us enter him as an applicant/contact on both organizations. I understand that I could work with him to use someone else as the main contact for one, but that is just manipulating the system in a way that doesn't make sense for us and makes record keeping less accurate.

Similarly, we have applicants that work for hospital systems with multiple branches – all with different EINs. Their email addresses are all hospital.org for instance, regardless of which hospital they are working at. This poses a problem if they transfer from one branch to another because the organization they are applying for will change but their email address will remain the same. The only way around this seems to be going in and reassigning every application they have ever submitted.

This is why I really don't think that requests should be linked to applicants instead of organizations. We aren't funding individuals. I think if there was a way to make the organization the applicant and just add contacts to the record, it would solve these issues. Basically, the organization would have applicant credentials and one person could be identified as the main contact - but others would be able to access the application as needed.

Thanks!

It would be great to see grantees across organisations able to access multiple requests. We have recently introduced collaborative projects, where several of our grantees previously working separately have applied for a grant on a collaborative project, and are trying to figure out how to best manage this in Foundant. Ideally we'd like users to have access to multiple requests, in that we could assign follow-up forms from a request attached to organisation A to a user in organisation B. While creating multiple emails is an option, we don't necessarily want Org B user to have access to information of other grants held by Org A.

This is a specific example of what we are looking for: We had a user from Org B that we originally assigned an email address under Org A so they could have access to the request in question. However, because Org A was uncomfortable with them being able to view grant materials from other grants under Org A, we reassigned the user to their organisation and found that the request went with them, so they were still able to view the LOI/Proposal and the form they had been assigned, but I was no longer able to assign them any additional forms under the grant as I was only able to assign forms for users under Org A. An ideal arrangement would be if there was a way for Org B user to remain under his proper organisation, but still be able to be assigned forms under the grant tied to Org A. This type of collaboration is something we'd like to continue with and would love if Foundant came up with a way to make this process easier.

Both, see requests and submit forms.

We have a similar situation, where a few folks are involved in more than one small, volunteer driven nonprofit and are the grant writer for both organizations. Even worse, these folks are generally some of our least tech savvy so the idea of creating a separate email address and separate log in is especially cumbersome for them to figure out.

We have the issue explained in this idea, but the collaboration on forms that you are describing, Sammie, could also help us with another issue. Currently we assign contracts to the ED/CEO to sign, but we receive tons of questions from the applicant to whom the request belongs about why they can't view the contract before it is signed (to check to ensure everything is correct before the ED/CEO signs).

Hi Sammie, yes this person will need to see requests and submit forms.

Thank you!
Cathy

Sammie, I'm thrilled to see this is under consideration! We have a similar situation, in that we have applicants who manage grants for multiple organizations (and by manage, I mean apply for, sign contracts for, do pay requests for, etc.) and we're having to walk them through using an alternate email address for each... it's a messy workaround. We also have school districts who are the fiscal agent for all of their schools, but right now they can't access or act on any of those schools' Requests, because they'd have to create a different User account with a different email address in order to be a Contact on each school's account.

Don't know if you still need this info. I can have the same issue working with consultants who work between two or more small organizations. My client success manager pointed out this idea, and I've shared it locally with consultants and volunteers who float between two or more grantees.

The consultant should set up a separate gmail address for grant applications/reporting that they will be involved in. For example, Jane.grants@gmail.com.

Then when registering with a Foundant database Jane can use the address Jane.grants+Goodwill@gmail.com and Jane.grants+communityhealthcare@gmail.com

Gmail will direct all the emails to the jane.grants@gmail.com address, yet also show the extended email address in the address header so that she can differentiate the various emails coming in.

That provides the unique email address needed but gets rid of the problem of having to set up separate email accounts. I'm not sure if other databases will recognize an email address with the + sign in them, but someone could try it.

Gmail recognizes the address fine, so when an email gets to the domain, @gmail, it knows how to deal with the + extension. As I was told, this trick was developed so Google testers could run unique email addresses in testing without having to set up thousands of accounts.

Some grant writers assist more than just one organization but currently have to have a unique email for each org. Allow more than one org to be associated with a user logon / email account.