This Glossary is intended to support understanding of terms used in Grant Lifecycle Manager (GLM) or Scholarship Lifecycle Manager (SLM). In some cases, definitions for key terms are accompanied by examples. Note that examples are not comprehensive; not all examples will be relevant, applicable, or appropriate to all organizations.
- Dashboard - When a user logs into the system, they land on this page. The specifics of the dashboard vary based on the user's role.
- For an administrator, the dashboard displays all open requests in the system, divided into workload pages based on request status.
- Email Template - When sending an email from a GLM/SLM site, a saved email template can be selected. Email templates can also be configured to send automatically at certain events within a process or universe.
- Form - A form is built within a process or universe stage. It contains questions to be completed for each request at that stage.
- Example: The application form is completed by applicants at the application stage, and the approval form is completed by an administrator at the decisions stage.
- Installment - When approving a request, the system prompts the administrator to record installments for the request. These are the planned payments for the grant or scholarship award. The total of the installments is displayed as the amount awarded for the request.
- Logon Page - All users logging into a GLM/SLM site do so through the Grant Interface logon page. The message on this page can be customized as desired.
- LOI - The Letter of Intent (LOI) stage in a process can be used to screen applicants so that an informed decision can be made early on about those not likely to be selected for funding or to steer applicants to a different funding opportunity that is a better fit.
- Merge Template - A template that can be used to generate merge documents from a GLM/SLM site. Merge fields are copied and pasted into the template to tell the system what data to pull from the site into the template when generating documents.
- Example: If award letters are sent to each grantee/scholarship recipient, a merge template of that letter could be created and used to generate customized award letters displaying the amount of each award and any additional details.
- Organization - In a GLM site, each applicant is connected to an organization. At registration, each applicant provides information about their organization, establishing a record for that organization in the site. Administrators can also add applicants to an existing organization. The Organization Summary page for an organization shows all requests submitted in the site by applicants connected with that organization.
- Process - The set of stages that a request goes through during its lifecycle. Administrators build and customize each process before opening it to applicants.
- Typically, each grant or scholarship cycle is built as a separate process.
- Process Manager - On this page, actions are available to add and manage processes or universes. This includes turning processes or universes on or off, making edits, and archiving processes or universes that are no longer active.
- Process Stage - A step within a process that a request goes through during its lifecycle. Each stage contains at least one form as well as configuration options.
- Example: The application stage of a process contains the application form and the option to configure a hard deadline and automatic emails.
- Project Name - By default, each form within a process includes the Project Name field. This is used by the system as an identifier for each request. The label and instructions of this field can be edited, but it cannot be deleted.
- Question Group - On a form, each question is located within a question group. The form can contain a single question group, or multiple groups can be added to organize questions on the form. A user filling out the form can expand and collapse each question group, which can be helpful on longer forms.
- Reporting Tool - This tool allows all of the data contained in a GLM/SLM site to be analyzed. After building a data set, reports can be run and saved. Filters, groups, charts, formulas, and other items can be added to each report.
- Request - When an applicant starts the first form in a process or universe, a request is created. The request houses all forms and information related to that request for grant or scholarship funding.
- Request Status - The status of a request reflects where it is located on its lifecycle in a GLM/SLM site. Active requests, meaning those with any status other than abandoned, denied, or closed, are available directly on the administrator dashboard.
- Example: The application complete status indicates that the applicant has submitted their application for the request and an administrator has marked the application complete.
- Request Summary - This page can be reached by clicking a request's project name. The Request Summary page displays all forms related to the request, information on the applicant and organization, and allows the administrator to upload documents and take actions on the request.
- Rich Text Editor - In locations such as a process description and an email template, the rich text editor is available to allow further customization of the content in that area.
- Shared Question - A question shared from one form to another within the same process or universe. Any edits to the question's response automatically update wherever the question is shared. By default, questions shared onto subsequent forms in a process or universe are in a read-only format as a quick reference for applicants.
- Example: A question about project goals might be shared from a grant application to a progress report follow up form.
- Site Settings - These settings allow the customization of various available features. Click the gear icon in the upper-right corner to access the Site Settings page.
- Submission Status - While each request has an overall status, the forms contained within the request each have a submission status. Submission statuses are helpful when running reports that require filtering based on the status of each individual form, such as an overdue follow up form report.
- Example: A request with the status of application submitted could contain an LOI form with the submission status of complete and an application form with the status of submitted.
- User - Any individual who logs into a GLM/SLM site is defined as a user. Each user is assigned a specific role. Applicants completing registration are automatically assigned the applicant role. Several internal roles are also available for staff members and evaluators.
- Workload Page - The administrator dashboard contains workload pages associated with the different request statuses. Requests within a particular status can be managed from within the associated workload page.
- Example: The Application Complete workload page contains all requests currently in the application complete status.