Applicant Tasks

Applicant Tasks let your team send targeted requests for documents or information to members directly within Glide. When a task is assigned to applicant, they see it directly in their portal and can respond from any device.

Use Applicant Tasks to:

• Request supporting documents (proof of address, government ID, proof of income, insurance)

• Collect short-form responses (source of funds, secondary contact information, clarifying questions)

• Track the status of each outstanding item in one place, across all applicants on a membership

How It Works

There are two parts to the feature:

1. Templates — created once under Configure → Applicant Tasks and reused across applications

2. Task assignments — added to a specific application from the Applicant Tasks tab in the application view.

When a task is assigned, the member sees it under Additional Information Requests in their onboarding portal with a clear status (Missing or Completed). Staff can monitor progress, send reminders, and manually update statuses from the dashboard.

Setting Up Applicant Task Templates

Before assigning tasks to individual applications, create reusable templates so your team doesn't have to re-enter the same details every time.

To create a template:

1. Go to Configure → Applicant Tasks

2. Click Add Applicant Task

3. Select an Application Type — either Deposit Account or Loans

4. Select a Task Type — either Document upload or Form (see Task Types below)

5. Enter a Title of Task — this is the headline the member sees

6. Enter a Description of Request — additional context shown to the member

7. Fill in any task-type-specific fields (see below)

8. Click Add Task

Templates are shared across all applications of the matching type (Loans or Deposit Account). Editing or deleting a template does not affect tasks already attached to an application — each task is a snapshot taken at the time it was added.

To edit or delete an existing template, find it in the table and use the kebab row menu.

Permissions: Creating, editing, and deleting templates requires "Configure" permission. Without it, the page is read-only.

Task Types

Document Upload

Use this when you need the member to provide a file.

When creating the template, you'll fill in two additional fields:

• Document Title — the headline shown to the member inside the upload drawer (e.g., "Pay Stub")

• Specific Instructions — detailed guidance about what to upload (e.g., file format, date range, what information must be visible)

Member experience: The member sees an Upload button and an Accepted documents link that opens a drawer with your Document Title and Specific Instructions. They can upload one or multiple files.

Accepted file types: PDF, JPG/JPEG, PNG. Other file types are rejected at upload.

Once the member uploads any file, the task automatically moves to Received. They can still attach additional files afterward using Upload additional documents.

Form

Use this when you need short written answers from the member rather than a file.

When creating the template, add one or more questions under the Questions section. Click + Add Question to add additional fields. Each question renders to the member as a single-line text input.

Member experience: The member sees an Enter details button that opens a drawer with your questions. They fill in their answers and click Submit. Once submitted, the task moves to Received.

Note: Form questions are free-text only. There are no dropdowns, date pickers, required/optional flags, or conditional logic supported. Use the description and question labels to set clear expectations.

Assigning Tasks to an Application

Once you have templates, you can assign them to specific applications — or create one-off custom tasks on the fly.

To assign a task:

1. Open the application from your queue

2. Click the Applicant Tasks tab

3. Click + Add Task

4. Select a template from the Add Task dropdown, or choose Custom to create a one-time task

5. Fill in any required assignment fields (see DAO and DLA sections below)

6. Click Add Task

The task is created with a status of Requested and immediately visible to the assigned member in their portal.

Task Statuses

You can change the status at any time by clicking the status badge on a task row and selecting a new value. To re-open a completed task, click into the task detail and use Send Again (resets to Requested).

Viewing Submissions

Click any task row to open the submission details:

• Document upload tasks: Shows a table of uploaded files with names and upload dates. Each file links to the document.

• Form tasks: Shows the member's submitted answers.

Deposit Account Opening (DAO)

Assigning to a Role

When you click + Add Task on a deposit application, the slide-over includes an Assign To dropdown. This lists every person currently on the membership, starting with the primary applicant.

The dropdown shows people by name (e.g., "Jane Smith"). The underlying role — Primary, Joint Owner, Beneficiary, Authorized Signer, Trustee, etc. — determines who appears, but you select the individual.

To request the same task from multiple roles (e.g., proof of ID from both the primary and a joint owner), add the task once per person. Each assignment becomes its own task row with its own status.

What Staff See

The Applicant Tasks table for deposit applications includes an Assigned To column showing which member each task belongs to. All tasks across all roles on a membership are visible in one table when you're viewing the primary applicant's application.

What Members See

Each member only sees tasks assigned to them. A joint owner, for example, logs into their own portal and sees only their outstanding tasks — not tasks assigned to the primary applicant.

Digital Loan Applications (DLA)

When Tasks Become Available

The Add Task button is not available until the loan application has been approved or counter-offered. Before that point, the Applicant Tasks tab shows:

Tasks will be available once the application has been approved or counter-offered.

LOS Stipulation ID

When creating loan task templates, you can include an LOS Stipulation ID — a reference code used to link the task to a specific requirement in your loan origination system.

For FIs integrated with supported LOS systems, applicant tasks are automatically added to applications if the matching stipulation is added within the LOS and documents uploaded by the member are automatically pushed to the matching loan record in the LOS.

System-Managed Loan Tasks

The following tasks are created automatically by Glide for certain loan states:

• Create a membership — shown to loan applicants who don't yet have a membership

• Vehicle information — shown on vehicle loans when vehicle details are missing

• Finalize my loan — shown once all other tasks are complete; the member uses this to complete the loan flow

Email Reminders

From the applicant task tab, you can send a manual email reminder to the assigned member for any task.

To send a reminder:

1. Find the task row in the Applicant Tasks tab

2. Click the ⋯ overflow menu

3. Select Send Email Reminder

The reminder is sent to the assignee's email on file and logged in the Activity Trail. A success message will confirm: Reminder sent for [Task Title] to [Assignee Name].

Common errors and what they mean:

Activity Trail

Every action taken on an Applicant Task is logged in the application's Activity Trail:

• Task added

• Task status updated

• Task deleted

• Email reminder sent

• Document uploaded by member

• Form submitted by member

This gives your team a full audit history of each request without any additional tracking.

Tips

• Build your template library first. Templates save time and ensure consistent instructions across your team.

• Use Specific Instructions thoroughly. Clear guidance reduces back-and-forth — tell the member exactly what format you need, what dates should be visible, and what qualifies as an acceptable document.

• Use Waived, not Delete, when a task is no longer needed. Waived keeps the task in your staff view for audit purposes; Delete removes it entirely.

• For the same request across multiple DAO roles, add the task once per assignee rather than creating separate templates.