Articles in this section

  • Follow Up Submission Logic


    By default, the Follow Up Submission Logic setting is set to Sequential. This means that if an applicant is assigned multiple follow up forms, they are accessible based on due dates. Once a follow up form is submitted and marked complete (by an administrator), the follow up with the next earliest due date becomes accessible.

    In the screenshot below:

    • The Grant Agreement follow up had the earliest due date and was already submitted and marked complete, so the applicant now has the option to View that submitted form.
    • The Progress Report has the next earliest due date (02/01/2022), so the applicant now has the option to Edit that form.
    • The Final Report has a due date after the Progress Report (05/31/2022), so the applicant cannot access that form yet. Once their Progress Report is submitted and marked complete, they'll have the option to Edit the Final Report form. 



    Allow Sequential Follow Up Preview

    If you set the Follow Up Submission Logic setting to Sequential, contact Support ( if you'd like to enable the Allow Sequential Follow Up Preview setting. If this setting is enabled, an applicant can preview and save their work on follow up forms with later due dates before submitting follow ups with earlier due dates. The applicant is still only able to submit the forms in sequential order based on due dates. 

    In the screenshot below: 

    • The Final Report has a due date after the Progress Report, and the Progress Report has not yet been submitted and marked complete (it still shows the option to Edit, and its status is Assigned rather than Complete). 
    • The applicant has the option to Preview the Final Report and will see the option to save their responses on the form, but will not see the option to submit the form yet. 




    You have the option to change the Follow Up Submission Logic setting to Open. This means that if an applicant is assigned multiple follow up forms, they are all accessible at once. The applicant does not need to submit them in a specific order. 

    In the screenshot below: 

    • Each follow up form has a different due date, and none have been submitted and marked complete yet.
    • The applicant has the option to Edit each form and will see the option to submit each form as well.



    Configure the Follow Up Submission Logic Feature

    By default, this setting is set to Sequential. Follow these steps to change the setting to Open, or back to Sequential if needed: 

    1. Click the Gear icon.Follow_Up_Submission_Logic_4.png 
    2. Click the Pencil icon next to the Follow Up Submission Logic setting.Follow_Up_Submission_Logic_5.png 
    3. Select Open or Sequential, then click OK.Follow_Up_Submission_Logic_6.png


  • Show Follow Ups with Decision Status

    Show Follow Ups with Decision Status

    By default, when you assign a follow up form to an applicant it's immediately visible on their dashboard. 


    You have the option to turn on the Show Follow Ups with Decision Status setting. When turned on, the system will only show an applicant their assigned follow ups once the decision status ("Approved") is visible for their request. The timing of the decision status and assigned follow ups becoming visible is controlled by the Show Decision Status setting.

    If you set a delay with Show Decision Status for the purpose of communicating with applicants before they can log in and see that their request is approved, this additional feature prevents a situation where they might log in and see assigned follow ups before you've communicated with them.

    Example Scenario

    Let's say you've set a delay of 30 days for the Show Decision Status setting, and you've turned on the Show Follow Ups with Decision Status setting. You just finished approving requests in your site and assigned follow ups for each approved request.

    If an applicant logs in before 30 days has passed, their dashboard will show a status of "Undecided" for their request and they will not see their assigned follow ups. 


    If you assign a follow up that has an automatic email configured to send when the form is assigned, the automatic email will still send even if the Show Follow Ups with Decision status setting is turned on. Consider turning off the automatic email for the follow up form if you prefer to manually send award communications to applicants at a specific time. 


    Configure this Feature

    By default, the Show Follow Ups with Decision Status setting is off (meaning assigned follow ups are visible immediately upon assignment). Follow these steps to turn this setting on: 

    1. Click the Gear Icon. followupswdecision_2.png

    2. Click the Pencil Icon next to the Show Follow Ups with Decision Status setting. followupswdecision_3.png

    3. Select True, then click OK.followupswdecision_4.png
  • Select Date and Time Formats

    You have the option to adjust the format of dates and times in your site. This is a sitewide setting, meaning it will affect how dates and times display throughout the site. The chosen settings automatically display for all user roles as well (i.e. applicants, evaluators, etc.).

    Contact Foundant Support ( or your CSM if you'd like to adjust date or time formats in your site. 

    Available Date Formats: 

    • MM/dd/yyyy (default)
      • Example: 11/25/2020
    • dd/MM/yyyy 
      • Example: 25/11/2020
    • yyyy-MM-dd
      • Example: 2020-11-25

    Available Time Formats:

    • hh:mm:ss tt (default)
      • Example: 04:15:45 PM EST
    • HH:mm:ss
      • Example: 16:15:45 EST


  • Set Custom Columns for Evaluators

    Please refer to this article for an overview and step-by-step instructions on custom columns: Create Custom Columns

    To create the default custom columns on evaluators' dashboards, go to the Your Evaluations tab on your own administrator dashboard to add fields. 



    This will set the default custom columns that evaluators (any users with assigned evaluations) will see. 

    If you have an Advanced license or selected this feature as part of a Standard +2 license, individual evaluators will be able to edit the custom columns on their individual dashboards as well.

  • Reset Two-Factor Authentication for a User

    Refer to this article for instructions on setting up a two-factor authentication requirement for users: Two-Factor Authentication.

    Occasionally a user may need to have two-factor authentication reset for their account. For example, if they need to change the authentication app they use. After resetting, the user will need to set up two-factor authentication again the next time they log on. 

    Follow these steps to reset two-factor authentication for a user's account: 

    1. Navigate to the Users search page, by click Search in the upper navigation bar and selecting Users
    2. Perform a search to find the user. 
    3. Click the Pencil Icon next to the user in the list. 
    4. Deselect Enabled in the Two-Factor Authentication section. 
    5. Click Save.
  • Two-Factor Authentication

    If you enable a custom password policy in your GLM/SLM site, you also have the option to require two-factor authentication for users. This requirement is configured by user role. 

    Two-factor authentication is an additional layer of security. It requires a user to enter both their password and a verification code to log on to a site. When enabled in your GLM/SLM site, a user will need to enter their password and a verification code once per day (as long as they're using the same browser). Throughout the rest of the day they will only need to enter their password to log back on.

    This tutorial (for users with any role in your site) explains how to log on using two-factor authentication.



    Follow these steps to require two-factor authentication:

    1. Refer to this article for the other steps in setting a custom password policy: Set User Password Policy
    2. While editing the User Password Policy setting, select the role(s) for which you'd like to require two-factor authentication.
    3. Click OK
    4. When a user with that role logs in, they will see instructions for setting up two-factor authentication.
      • This involves downloading a two-factor authenticator app, which will generate a unique verification code which they are prompted to enter in the site.
    5. When logging in again (for the first time each day), the user will be prompted to enter a verification code. 
      • They will need to open their two-factor authenticator app again, which will provide them with a time-sensitive verification code to enter in the site. 
  • Quick Navigation

    The Quick Navigation feature gives users with an administrator role (including administrators, grants managers, and auditors) the ability to jump to the top or bottom of the page, and to click into the next form in a list. The ability to click into the next form is only available if you have the Paging feature enabled in your site (please contact the Support team with any questions).


    These options display when viewing a form directly from a workload page (i.e. Application Submitted). Quick Navigation is not available at this time in the Your Evaluations tab.

    • Clicking the Top button brings you to the top of the page. 
    • Clicking the Bottom button brings you to the bottom of the page. 
    • Clicking the Next button brings you to the next form in the list. For example, if you accessed the current application form from the Application Submitted workload page, you'll be brought to the next application form in the Application Submittedlist.
      • When you click Next while viewing the last form in the list, you'll be brought back to the first form in the list. 



  • Save Process Filters

    If you apply a process filter when using your site, the system will remember the filter as you navigate your site until you log out. 

    If you would like the system to remember the filter even after you've logged out and logged back in, enable the Store Process Filter feature in your site. To do this, navigate to the Site Settings page and set the "Store Process Filter as a User Setting" feature to "True." 

  • Auto Search on Requests & Decisions Page

    Any search parameters you use on the Requests & Decisions search page are remembered by the system when you visit the page again. 

    The system can also automatically run a search based on those parameters when you visit the page again. This setting is off by default, but you have the option to toggle it on. This setting will only apply to your account, so other internal users in your site can configure this setting differently. 

    Follow these steps to turn on the Auto Search setting: 

    1. Click Search in the upper navigation bar. 
    2. Select Requests & Decisions
    3. Turn the Auto Search toggle on. 
      • The system will now automatically run a search the next time you visit this page, based on the last search parameters you used.
  • Set User Password Policy

    You can choose to set a password policy for users in your GLM/SLM site. The requirements you choose will apply to all users (across all roles) in your site who set or reset their password going forward.  

    You can also configure the maximum failed attempts allowed for users to enter their password when logging on, without enabling a custom password policy. Please refer to step 10 in this tutorial for more details on this setting.

    1. From the dashboard, click the Gear Icon in the upper right corner of the screen. 
    2. Click the Pencil Icon next to the User Password Policy setting.
    3. Click the checkbox to enable your custom policy.
      • If this setting is not enabled, the default password policy is in effect. The default policy is a minimum of 6 characters, which can include letters, numbers, and the following special characters: !@#$%^&*()_  
    4. Choose the minimum password length. 
      • This is the minimum number of characters that a user must have in their password.
    5. Select any character types you'd like to require. 
      • This defines the specific character types that a user must include in their password.  
    6. Determine how many of the character types (selected in the previous step) must be included.
      • In this example, passwords must contain 2 of the 3 selected character types (i.e. a lower case letter and a number, or an upper case letter and a lower case letter). 
    7. Determine the minimum number of characters required from each character type. 
    8. Set the number of days until passwords should expire (first uncheck the "Never" box). Users are prompted to reset their password after that number of days. Alternatively, keep the "Never" box checked if you do not want passwords to expire.
      • The default for this is to never expire, which is the industry recommended best practice. A password expiration should only be used if your organization’s password security policy requires it.

    9. Select any user roles for which you'd like to require two-factor authentication. Please refer to this article for more information on this feature: Two-Factor Authentication 
    10. Select the maximum failed attempts allowed for users to enter their password when logging on. 
      • After reaching this limit, the user will be locked out of their account and prompted to reset their password.
      • This part of the policy will be enforced even if you do not enable your custom policy.
    11. Click OK.

    If a user tries to set a password that does not meet the requirements, the system will display a message listing the password requirements.  

    Below are a few additional resources related to password policies (and other security considerations): 

  • Foundation Center's eGrant Reporting Program (eReport Map)

    Please note: Foundation Center and GuideStar recently joined forces to become Candid (learn more here: Candid). Links and email addresses in the resource below have been updated accordingly.


    What is the eGrant Reporting Program History:  Foundation Center’s eReporting Program enables grantmakers, to quickly and easily share grants data with the field; making it searchable across several platforms and research projects.  Foundant clients who participate in the program will be provided with a premium version of Foundation Center’s newest mapping platform Foundation Maps that reflects your own foundation's grantmaking activity in a highly interactive tool, accessible directly from your Foundant Grant Lifecycle Manager (GLM) Platform (Here’s a link to an example map).  

    These complimentary maps benefit both internal and external stakeholders and can be used by your staff, included in presentations to your board, or posted on your intranet or public web site.   We currently have over 100 clients who are eReporting to Foundation Center via their Foundant eGrant Report.  Click here to find more information about the program on the Foundation Center’s eReport Website:

    Why Should I Participate?

    • Share info widely in an efficient manner and without any duplication efforts
    • Use the data to pro-actively think about what your grant data is saying about you as a grantmaker.
    • The sector as a whole needs better quality and more timely info than what is publicly being shared on 990s. Grant makers need to be both consumers and participants in the “Virtuous Circle of Data”.  Everyone will benefit from this “Virtuous Circle” as more and more organizations contribute to the eReporting program.
    • eReporting gives your Foundation more control over how your grants are represented to others and, more broadly, to the field.

    What will be done with my data?

    Your data will be centralized at the Foundation Center and help to fuel tools such as:

    • Research studies on giving trends
    • Licensed data sets available for both your organization and the sector
    • Special projects like custom web portals and interactive mapping tools
    • Online tools such as Foundation Directory Online which allows grantmakers to be more informed about their grantees, or Foundation Stats which is a tool that provides a snapshot of givers’ stats:

    How do I eReport via my Foundant Site?  It’s easy!  Just email that you’d like us to create your eGrant Report for you and we’ll be in touch within a few days after it’s built for you to review and finalize.  Once you’re happy with it simply Run Report from your Saved Reports page, export to “CSV” output and email to Foundation Center at  Your eReport Map should be built and ready within a couple weeks of your first eReporting submission. 

    Foundant is very happy to be participating and collaborating with Foundation Center as we’re big fans of the eGrant Reporting tool set and everything they are doing to focus on growing the eGrant Reporting Program.  It’s great to be in a place with our software where we can offer up technology and solutions to these types of community programs to benefit the sector.

  • Follow Up Automatic Email - Notification Days

    You have the ability to configure automatic emails that will go out to grantees who have not submitted follow up forms.  By default, these reminder emails will go out 14 days before a follow up is due.  

    You can also build automatic email templates that will be sent if a grantee does not submit their assigned follow-up by the specified due date. By default, this Follow-up Past Due Notification is set to go out to any grantee that has not submitted a follow up, one day after the due date. 

    Please note that neither one of these notifications will go out to grantees that have already submitted the applicable follow ups. 

    The number of days for both features can be edited from the Settings page by selecting the gear icon at the top of any page.

    • This is a site-wide change and will affect all follow up forms notifications of this type in the system.
  • Warn Applicants of Existing Requests

    Turning on this feature will cause a warning message to appear if an applicant attempts to apply to a Process for which they already have created a request. 

    • The message will provide a link to the existing request, as well as the status and date of the request. 


    This feature will also turn the Apply button of a Process grey after a request has been created, but this will not keep an Applicant from creating a new Request. 

    If a request has been deleted or abandoned it will not activate this warning message.

    This is a site-wide feature and will affect all Processes that are visible to your Applicants. To turn this feature on, access the Settings page by selecting the gear icon at the top of any page.

  • Request Status Updates and Visibility

    Show Decision Status

    When a request has been submitted and is under consideration, the applicant will see the decision status of Undecided on their dashboard. 

    Once a request has been approved or denied, the applicable decision status will appear on the applicant’s dashboard after the preset delay time period has passed after the decision date. 

    • For example: If the decision status is set to a 15 day delay, an award approved on May 15 will appear as Undecided until May 30, at which time the decision status will update to Approved.
    • If the award is denied, the status of Denied will appear and the request will move to the Historic Requests tab after the delay time period has passed.
    • The delay can be set to 0 days, meaning the decision status will be visible on the decision date. 

    By default, the delay is set to 365 days. Follow these steps to change the delay: 

    1. Click the Gear Icon
    2. Click the Pencil Icon next to the Show Decision Status setting. 
    3. Edit the number of days and click OK.

    You also have the option to show the amount awarded and installment information to applicants on their dashboard for any approved requests. When enabled, the applicant will see a View Details link next to the approved request (once the delay period has passed from the decision date), which leads them to the installment and payment information. 


    Follow these steps to turn this setting on or off: 

    1. Click the Gear Icon.
    2. Click the Pencil Icon next to the Enables Details link on Applicant Dashboard setting.

    3. Select True or False, then click OK.


  • Applicants' Ability to Edit Organization Information

    During registration in your GLM site, an applicant enters both their own contact information and their organization's information. By default, once applicants initially enter their organization's information, only a site administrator can edit that information. 

    You have the option to allow applicants to edit their organization's information after registration. This can be limited to certain fields. For example, you could only allow edit access for the organization's address or website information. Some administrators choose to not allow applicants to edit fields such as the tax ID number, as they'd like to first have a conversation about why that information is changing. 


    Configure Applicants' Ability to Edit Organization Information

    Contact Support ( to configure this setting, and let them know which field(s) you'd like to allow applicants to edit. The available fields are shown in the image below.Applicant_Ability_to_Edit_Organization_Information_1.png 

    When one or more fields are accessible for applicants to edit, they will see a Pencil icon next to their organization's information, allowing them to make changes.Applicant_Ability_to_Edit_Organization_Information_2.png 

    Notification of Changes

    When one or more fields are made accessible for applicants to edit, you have the option to configure an automatic email to be sent whenever an applicant edits their organization's information. 

    When configured, this automatic email will send to the selected administrators and the primary contact for the organization whose information was changed. The email will automatically include the original and updated organization information. 

    Changes to an organization's information are also recorded in the Organization Change Log, located on the Organization Summary page.
    1. After creating an email template with the desired language, select the Organization Changed email notification event type.Applicant_Ability_to_Edit_Organization_Information_3.png

    2. Navigate to the Update User page for an administrator who should be set up to receive this email.Applicant_Ability_to_Edit_Organization_Information_4.png 
    3. Click Manage Notifications.Applicant_Ability_to_Edit_Organization_Information_5.png 
    4. Click the Organization Edited tab.Applicant_Ability_to_Edit_Organization_Information_6.png 
    5. Check the box for the email template you created.Applicant_Ability_to_Edit_Organization_Information_7.png 
    6. Click Save.Applicant_Ability_to_Edit_Organization_Information_8.png
  • Applicants Viewing Requests Submitted Within their Organization

    By default applicants can only see the applications that they submitted or requests that have been re-assigned to them. If you would like applicants to see requests submitted by other users at their organization we can turn on the “View Organization History” attribute.

    There are 2 options when configuring this attribute:

    1. All users can view their organization history.

    2. The administrator can select user-by-user who can view their organization history.

    When this feature is enabled applicants that have access to their organization's application history will be able to view:

    • LOIs and applications that have been created by all applicants in the organization
    • Organization contact information
    • The contact information of all other contacts in the organization.

    In order to view the organization history applicants must click on the View Organization History link in their navigation menu.


    This can be edited from the Settings page by selecting the gear icon at the top of any page.

  • Applicant Visibility

    The Applicant Visibility feature allows an administrator to hide a request from the applicant. Turning on this feature will give you the option to hide the entire Process and any Requests entered into the Process from applicants. Or you can choose to hide any specific Requests on an individual basis. 

    Once this functionality is turned on in your site, you will see the Applicant Visibility drop down appear in the Edit Process Summary section if the Visibility is set to Internal.

    From the Applicant Visibility drop down you can select the following options; 

    • Blank - means this is not in use and the process will default to the Internal visibility setting. Meaning requests will be visible to applicants after reaching the decision stage. 
    • Show - will show request to the applicant as soon as they have been created. 
    • Hide - will always hide the request from the applicant, including in the organization history if visible. This will also the hide the amount awarded of a Request if applicable in the total Amount Awarded to the Applicant or Organization.  

    Changing this setting will affect all grants that are in that process, even those that have already been created. 

    Within the Advanced Options section of the Request Summary, you can also override the Process Applicant Visibility for that request. Here you can change the Applicant Visibility to:

    • Default to Process Visibility - which will match the Applicant Visibility setting of the Process
    • Show
    • Hide

    This can be turned on from the Settings page by selecting the gear icon at the top of any page.

  • Collaborator Feature

    The collaborator feature allows applicants to work together on a single request. With this feature, applicants can also add a new user to their organization in your site (GLM only) without contacting an administrator. 

    This feature is included with the Basic license and above. Please reach out to the Support team at to enable this feature in your site. When enabled, the option to invite collaborators will appear for all of your applicants.  


    Use Cases

    The collaborator feature helps address several common scenarios, including: 

    • Multiple applicants from an organization need to work together on a request. 
    • An applicant needs someone else to upload a document, fill out certain questions, or sign off on their request (e.g. a fiscal sponsor, executive director).
    • An applicant needs an efficient way for someone else to view and (in some cases) submit their request.
    • An organization works with a grant writer. 
    • An organization has a new staff member who would like to submit a request.


    Applicant-Facing Tutorials

    Below are tutorials on this feature that you can share with your applicants:  


    How It Works

    Below are the basics on how this feature works for your reference. Please refer to the applicant-facing tutorials linked above for detailed steps for the applicant and collaborator. 

    1. One applicant must go through registration as usual. Once they open the first form in the process (either an LOI or application), they'll see the option to invite collaborators to the request in the top right corner of the page. That option will appear on any follow up forms assigned within the request as well.
    2. After the applicant clicks Collaborate, they'll see a pop-up that prompts them to enter the email address of the person they're inviting to collaborate, type a message, and select the permission level (view, edit, or submit) for the collaborator.
    3. Within the collaborator pop-up, the applicant can also manage existing collaborators. They can resend an invitation, change permission levels, or remove a collaborator from their request. 


    The permission level set for a collaborator applies to the entire request, not just a single form within the request (e.g. application or follow up). 

    • View: The collaborator can view each form in the request that the applicant has access to.
    • EditThe collaborator can view and edit each form in the request that the applicant has access to.
    • Submit: The collaborator can view, edit, and submit each form in the request that the applicant has access to.
  • Enable Short Links for Processes

    Turning on the Enable Short Links for Processes feature allows administrators to share a direct short link to the initial form in a process. When this setting is enabled, follow the steps below to copy the short link for a process: 

    From the Edit Process Summary dropdown in the process, click the link icon next to the name of the process. 

    Make sure the toggle switch is green, indicating the link is active. Click the copy icon to copy the link to your clipboard. This can now be pasted into an email or other communication with applicants.

    • After clicking the short link, if the applicant is already logged on they'll be brought to the first form in the process. 
      • If the applicant is not logged on, they'll be brought to the Logon Page. There they can log on if they've already created an account, or click Create New Account if they're a new applicant.  
      • After logging on or creating their account, they'll then be brought to the first form in the process. 
    • For a process with Restricted visibility, the applicant will not need to enter an Access Code if they use this short link.


    The short link will lead to an “Inactive Link” message in the following instances: 

    • Process is turned off
    • Not within the process start and end date range
    • The process is set to Internal visibility
    • Link has been deactivated in the process by an administrator
  • Shared Documents

    Shared Documents is a tool administrators can use to upload and house documents in the system. These documents can then be shared with users who have the Board Member, Staff Evaluator and/or Grant Manager role.

    Types of files commonly housed in Shared Documents:

    • Print packets for evaluators that don't complete an evaluation form
    • Evaluator tutorials
    • Meeting Agenda & Minutes 
    • Files and images that are linked on other pages within the site

    To access Shared Documents, select the Shared Documents option located under Tools in the navigation menu.

  • Google Translate

    You can turn on the Google Translate feature to let users translate the site into their own language. This is a site-wide setting and will be visible for all users who log into your site. This can be turned on from the Settings page by selecting the gear icon at the top of any page.

    Once this is turned on a Google Translate option will appear near the top of the page. From here you can select a language and the entire page will be translated accordingly.

    • Please note that this is a Google software, and it may not recognize or correctly translate all the terminology within your site.  

    You can revert the language back by selecting English from the Select Language drop-down, or by selecting the close button at the top of the page.

    This feature is currently not compatible with the Microsoft edge internet browser.  

  • Public Apply Page

    With the Public Apply Page feature, administrators can give prospective applicants access to a read only view of the Apply page. This allows prospective applicants to review grant opportunities prior to creating an account in your system.  

    • By default, this feature is turned off.  This can be turned on from the Settings page by selecting the gear icon at the top of any page.
    • After the feature is turned on, administrators can get the link to the Public Apply Page from the Process Manager page. Public_Apply_Page_2.png

    • When the Get Public Apply Link  button is clicked, a pop-up window containing the link to the Public Apply Page appears. Public_Apply_Page_2.png

      • This link can be copied and pasted into an email template or added as a hyperlink on your website.
    • When an applicant clicks the link they will be taken to a VIEW ONLY version of the Apply page. They can click the Preview button for any processes that are turned on and have the public visibility setting. 
      • Applicants that have been provided an access code, may enter the access code to preview the restricted process or processes that correlate to the specific access code.
    • Applicants do not have the ability to apply from this page. 
      • They will need to go to the logon page by clicking the Log On/Create an Account to Apply button in the top right-hand corner of the screen where they can either sign in, if they already have an account, or click the Create New Account button to complete the registration process.
  • Fax to File

    This tool allows users who do no have access to a scanner to use a fax machine in order to get physical documents into a digital format. 

    1. To start, click the Fax to File link on the top menu of the screen.
    2. Then click the Request a Fax # button and you will be presented with a toll-free fax number
    3. You have this number for 20 minutes.
    4. Fax your document to the number provided.
    5. Send a separate fax for each document and do not include a cover sheet.
    6. All faxed documents will be automatically converted to .pdf format.
    7. You have 20 minutes to fax your documents before the number expires.
    8. After you have faxed each separate document click the Finished Faxing button to see your list of files.
    9. Download your converted documents to your computer and save them.
    10. Upload the documents to the appropriate questions on the online form.


  • Duplicate Organization/Tax ID Warning Message in Registration

    The Duplicate Tax ID Warning Message is a measure you can take to help prevent organizations from registering in your site more than once. 

    When registering, if an applicant enters a tax ID number (EIN) that is already registered in the system, the duplicate tax ID warning message can appear prompting the applicant to reach out to the site administrator before continuing. 

    Sample Warning Messages  

    1. Attention Applicant! The Tax ID number you have entered is already registered in the system. Please do not create a duplicate account. Please contact the Foundation at to receive your log on credentials.


    Please note that the Tax ID warning message is not a hard-stop. The applicant can close the message and continue registering.

    By default this message is turned off. To have the Duplicate Tax ID Message added to your registration process please contact

  • Organization Custom Fields


    Custom fields can be added to the Organization Registration page. This page is part of the registration process when a new applicant creates an account.

    The data collected in these fields is visible in an organization's Organization Summary. 


    Contact your CSM to add or edit custom fields on your Organization Registration page.

    Custom Fields

    All question types except File Upload, Text and Upload, and Nested Lists are available on the Organization Registration page. 

    Adding custom fields to this page allows you to collect additional information about each organization upfront. 

    Best practice is to collect more static information at registration, as you will not have a record of the original response if the information is changed. More dynamic information that tends to change from year to year should be collected within a request (i.e. on the Application form).

    Custom fields on the Organization Registration page can be pulled into reports and merge templates. 

    After registration, an applicant can only view the information they entered in any custom fields if you've enabled the setting for Organization Edit Fields.

  • User Custom Fields


    Custom fields can be added to the User Registration page. This page is part of the registration process when a new applicant creates an account. 

    Contact Support ( to add or edit custom fields on the User Registration page.

    Custom Fields

    All question types except File Upload, Text and Upload, and Nested Lists are available on the User Registration page.

    For GLM sites, note that custom fields cannot be added to the Executive Officer section of the User Registration page.

    A best practice is to collect more static information at registration, as you will not have a record of the original response if the information is changed. More dynamic information that tends to change from year to year should be collected within a request (i.e. on the application form).

    Custom fields on the User Registration page can be pulled into reports and merge templates. 

  • What Changes Can be Made to Registration Pages?

    There are many items that can be modified throughout the registration process. Here is a list of the items we can and cannot change. Keep in mind that changes to field labels should be kept to a minimum as these fields are connected to the reporting tool. 

    Items that can be modified:

    • Question Labels can be modified.
    • Questions can be made required.
    • Questions can be hidden.
    • Validation expressions can be added so that only certain formats of answers will be accepted.
    • Page headers and instructions can be modified.
    • Custom fields can be added to the Organization Registration page (GLM sites) and the User Registration page.
    • The executive officer section can be hidden (GLM sites).
    • A duplicate organization message can be added to the Tax ID field alerting applicants that the Tax ID is already in the system (GLM sites).


    Items that cannot be modified:

    • Custom fields cannot be added to the executive officer section of the User Registration page (GLM sites).
    • We cannot make changes to the registration confirmation page.
    • The following fields must remain required: 
      • Organization Name (GLM sites)
      • Applicant First Name
      • Applicant Last Name
      • Email/Login


    If you would like changes made to your registration pages, please contact Foundant Support at If you would like to add any custom fields, please reach out to your CSM.

  • Updating My Foundant Site (Site Skin) to Match My Website

    Has your website changed and your site skin doesn't match?
    We would be happy to update your site skin for you.

    Please contact us at with your updated images/website.

    Below is a list of the image/color requirements:

    • The header banner for your Logon Page can be 50px to 300px in height and the width must be 1002px.
    • The header banner once logged in to your site can be 50px in height and the width must be 150px or less.
    • The header banner image should be in png format (NOT PDF, .zip, .pdf, .doc, or .eps format).
    • Navigation list background color for top navigation bar and section above the top navigation bar.
    • Navigation list headers color.
    • Navigation list text color and background hover color.
    • Table header text color and background color.
    • Footer color.
  • Customize the Logon Page Message

    The Logon page is the first page all users (administrators, board members, applicants, etc.) see when they click the link to access your GLM or SLM site. 

    The message on this page is customizable. Below is an example Logon page message, which you are welcome to use as a template.Customize_the_Logon_Page_Message_1.png

    Example Logon Page Message Text

    Welcome to [insert your foundation's name] online [grant or scholarship] portal.

    New Users: Please click "Create New Account" to complete the registration process and create your logon credentials.

    Existing Users: Please enter your credentials and log in. If you forgot your password, please use the "Forgot your Password?" link to the left to reset your password.

    Not Sure? If you think that you or someone at your organization has already registered in the system, do not create a new account. Please contact our [Grant or Scholarship] Administrator, [insert name], at [insert email address] to receive your username.


    Customize the Logon Page Message

    Follow the steps below to edit the message. 

    1. Click the Gear icon in the upper-right corner of your site to access your Site Settings page.Customize_the_Logon_Page_Message_2.png 
    2. Click the Pencil icon next to the Logon Page Message setting.Customize_the_Logon_Page_Message_3.png 
    3. Customize the message as desired, then click OK.Customize_the_Logon_Page_Message_4.png 
    4. If you'd like to view the changes, log out of your site, as this will take you to the Logon page. 
  • Editing Site Settings

    As an administrator, you have the ability to edit certain back end settings within your site. This can be accessed by selecting the Edit Site Settings gear icon from the top of the page.

    On the Settings page, you will see your License Type, followed by all of the editable settings within your Site. You may use the quick search feature at the top of the page to quickly find a particular setting.

    The edit pencil icon can be used to edit the setting, while the reset icon will set this setting back to its default. Note that changes may be made by all Administrators within your site.

    At the bottom of the page, the Settings Change Log will show you the history of all changes that have been made by Foundant or an Administrator within your site.

    If you have any further questions on a setting please contact