Project Applications allow organizations to require volunteers to apply and be approved before signing up for opportunities within a project. This helps ensure volunteers meet specific requirements, complete necessary paperwork, and are properly vetted before participating.

When creating or editing a project when there are active project applications, you will be able to add a project application to any project. 
 

Overview

Project Applications provide a structured way to collect additional information, enforce requirements, and control when volunteers can access opportunities within a project.

• Volunteers must complete a project-specific application before accessing needs (shifts/opportunities)
• Any required project credentials must also be completed and approved before needs are accessible
• Volunteers cannot view or sign up for needs until all requirements are satisfied
• Admin approval is required before access is granted

This functionality adds an additional layer of screening and preparation beyond standard volunteer registration.

Project Application Form

Each project can include a fully customizable application form that volunteers must complete before participating.

Admins can configure forms with:

• Custom fields and application-specific questions
• Instructional text and help content
• Section headers and separators for better organization

This allows each project to collect only the information relevant to its specific needs.

👉 For more details, see: Project Application Configuration
 

Project Applicant Review

Once a project application has been submitted by a volunteer, a project admin or organizer admin on the project can review the various applicants and their associated responses via the projects themselves.

👉 For more details, see: Project Application Review
 

Project-Level Credentials

Project credentials apply to all opportunities (needs) within a project and must be completed before participation.

These may include:

• Background checks
• Training acknowledgments
• Certifications or document uploads

Depending on configuration, credentials may also require admin approval. 
 

👉 Learn more: Credential Administration
 

Advanced Credential Logic

In addition to project-level credentials, projects can support more advanced configurations such as:

• Assignment-level credentials (specific to individual needs)
• Prerequisite credential chains (project credentials must be completed before another becomes available on the project need)

This enables workflows like:

• Requiring an interview credential before accessing certain roles that could require a background check. 
   

Volunteer Experience

To participate in a project, volunteers will:

1. Register or log in
2. Navigate to the project
3. Complete all required steps:
   • Project Application
   • Project-level credentials
4. Wait for approval
5. Gain access to view and sign up for needs

Until these steps are completed, opportunities within the project will remain unavailable.

For Volunteers (Public Experience)

Logged Out Users

• Volunteers will see the message:

• They must log in or create an account via general registration before proceeding.
   

Logged In Users

Once logged in, volunteers will see:

1. Project Application (Required)
2. Project-Level Credentials Individually (if configured)

From here:

• Volunteers must complete the Project Application
• Complete any required credentials
• Wait for approval

Only after completing all steps will available needs appear for signup. 
 

Best Practices

Project Applications are especially useful for:

• Roles involving higher responsibility
• Youth programs or vulnerable populations
• Opportunities requiring onboarding or screening levels

To ensure a smooth experience:

• Keep applications clear, concise, and relevant
• Only require information that is necessary
• Use credentials to manage:
  • Compliance requirements
  • Training verification
  • Document collection