Below are commonly used terms and definitions related to your GLM/SLM site.
- 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 your GLM/SLM site, you have the option to select any of the templates you've saved. 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 you to record the installment(s) 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 your GLM/SLM do so through the Logon Page. You can customize the message on this page in your site settings.
- Merge Template - A template that can be used to generate merge documents from your site. Merge fields are copied and pasted into the template to tell the system what data to pull from your site into the template when generating documents.
- Example: If you send award letters to each grantee/scholarship recipient, you could create a merge template of that letter to generate customized award letters with the amount of each award and other 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 your site. As an administrator, you can also add applicants to an existing organization. The Organization Summary page for an organization shows all requests submitted in your site by applicants connected with that organization.
- Process - The set of stages (e.g. application, evaluations, approval, etc.) that a request goes through during its lifecycle. You, as the administrator, can build and customize each process before opening it to applicants. Typically each grant or scholarship cycle will be built as a separate process in your site.
- Process Manager - On this page, you can take actions on your processes or universes. This includes actions such as adding or archiving processes/universes, accessing a specific process/universe to make edits, and turning processes/universes on or off.
- Process Stage - A stage (e.g. application, evaluations, approval, etc.) within a process that a request goes through during its lifecycle. Each stage contains at least one form as well as configuration options.
- Project Name - By default, the forms within a process contain the Project Name field. This is used by the system as an identifier for each request. You can change the label and instructions of this field, 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 you can add multiple groups 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 you to analyze all of the data contained in your GLM/SLM site. After building a data set (telling the system which data you want to examine), you can run reports. On each report, you can add filters, groups, charts, etc.
- 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 funding.
- Request Status - The status of a request reflects where it's located on its lifecycle in your GLM/SLM site. Active requests (requests with any status other than abandoned, denied, or closed) are available directly on your 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 the project name of a request. The Request Summary displays all forms related to the request, information on the applicant and organization (if applicable), 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.
- Example: You can make text bold, change the text color, or insert an image using the rich text editor.
- 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: You might share a question about project goals from a grant application to a progress report follow up form.
- Site Settings - These settings allow you to control and customize different features available in your site. The Site Settings page can be accessed by clicking the gear icon in the upper-right corner of your site.
- 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 (e.g. 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 your site is defined as a user. Each user is assigned a specific role - either applicant, or one of the internal roles (administrator, grants manager, board member, etc.).
- 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.